test_ok1/pytest.py

# PYTHON_ARGCOMPLETE_OK
"""
pytest: unit and functional testing with Python.
"""
__all__ = ['main']

if __name__ == '__main__': # if run as a script or by 'python -m pytest'
    # we trigger the below "else" condition by the following import
    import pytest
    raise SystemExit(pytest.main())

# else we are imported

from _pytest.config import (
    main, UsageError, _preloadplugins, cmdline,
    hookspec, hookimpl
)
from _pytest import __version__

_preloadplugins() # to populate pytest.* namespace so help(pytest) works
moving from optparse to argparse. Major difficulty is that argparse does not have Option objects -> added class Argument Needed explicit call of MyOptionParser.format_epilog as argparse does not have that. The parse_arg epilog argument wraps the text, which is not the same (could be handled with a special formatter). - parser.parse() now returns single argument (with positional args in .file_or_dir) - "file_or_dir" made a class variable Config._file_or_dir and used in help and tests - added code for argcomplete (because of which this all started!) addoption: - if option type is a string ('int' or 'string', this converted to int resp. str - if option type is 'count' this is changed to the type of choices[0] testing: - added tests for Argument - test_mark.test_keyword_extra split as ['-k', '-mykeyword'] generates argparse error test split in two and one marked as fail - testing hints, multiline and more strickt (for if someone moves format_epilog to epilog argument of parse_args without Formatter) - test for destination derived from long option with internal dash - renamed second test_parseopt.test_parse() to test_parse2 as it was not tested at all (the first was tested.) --HG-- branch : argparse 2013-07-25 21:33:43 +08:00			`# PYTHON_ARGCOMPLETE_OK`
flat is better than nested (cont'd): - pytest.py is new module, making "python -m pytest" work always - _pytest/*.py now contains core.py, hookspec and the plugins, no sub packages 2010-11-13 18:10:45 +08:00			`"""`
avoid double-instantiation of PluginManager in case of the "python pytest.py" or -m pytest invocation 2012-09-25 17:58:41 +08:00			`pytest: unit and functional testing with Python.`
flat is better than nested (cont'd): - pytest.py is new module, making "python -m pytest" work always - _pytest/*.py now contains core.py, hookspec and the plugins, no sub packages 2010-11-13 18:10:45 +08:00			`"""`
			`__all__ = ['main']`

			`if __name__ == '__main__': # if run as a script or by 'python -m pytest'`
avoid double-instantiation of PluginManager in case of the "python pytest.py" or -m pytest invocation 2012-09-25 17:58:41 +08:00			`# we trigger the below "else" condition by the following import`
			`import pytest`
			`raise SystemExit(pytest.main())`
some more separation of core pluginmanager from pytest specific functionality. Idea is to have the PluginManager be re-useable from other projects at some point. 2013-09-30 19:14:14 +08:00
			`# else we are imported`

adapt pytest to pluggy's decoratorclass branch --HG-- branch : pluggy1 2015-04-29 22:40:52 +08:00			`from _pytest.config import (`
			`main, UsageError, _preloadplugins, cmdline,`
adapt to pluggy naming, rename pytest.hookspec_opts to pytest.hookspec,s ame with hookimpl_opts --HG-- branch : pluggy1 2015-05-06 16:08:08 +08:00			`hookspec, hookimpl`
adapt pytest to pluggy's decoratorclass branch --HG-- branch : pluggy1 2015-04-29 22:40:52 +08:00			`)`
some more separation of core pluginmanager from pytest specific functionality. Idea is to have the PluginManager be re-useable from other projects at some point. 2013-09-30 19:14:14 +08:00			`from _pytest import __version__`

			`_preloadplugins() # to populate pytest.* namespace so help(pytest) works`