community.general/tox.ini

[tox]
envlist = py26,py27,py35,py36

[testenv]
deps = -c{toxinidir}/test/runner/requirements/constraints.txt
       -r{toxinidir}/test/runner/requirements/ansible-test.txt
       -r{toxinidir}/test/runner/requirements/sanity.txt
       -r{toxinidir}/test/runner/requirements/units.txt
commands =
    python --version
    # The recommended method of running tests with tox is to execute
    # ansible-test directly and use the --tox and --python options.
    # The commands below are provided as a convenience for those who
    # prefer to run tox directly instead of through ansible-test.
    {toxinidir}/test/runner/ansible-test compile --python default -v
    {toxinidir}/test/runner/ansible-test sanity  --python default -v
    {toxinidir}/test/runner/ansible-test units   --python default -v
passenv =
    # Pass HOME to the test environment to avoid the missing HOME env
    # variable error. See issue: #20424
    HOME

[pytest]
xfail_strict = true

[flake8]
# These are things that the devs don't agree make the code more readable
# E402 module level import not at top of file
ignore = E402
# not all the devs believe in 80 column line length
max-line-length = 160
Add tox and travis-ci support Add tox integration to run unittests in supported python releases. Travis-CI is used for test execution. Additionally, the unittest TestQuotePgIdentifier was updated to support using assert_raises_regexp on python-2.6. Sample travis-ci output available at https://travis-ci.org/ansible/ansible/builds/54189977 2015-03-11 00:38:37 +01:00			`[tox]`
Fix envlist in tox.ini tox doesn't actually expand {brace,expressions} in envlist, so if you ran `tox` without specifying a `-e` parameter, tox would try to run `py26`, `py27`, `py3{5` and `6)`, defaulting to python2.7 for those non-standard environment names. 2017-01-09 10:31:01 +01:00			`envlist = py26,py27,py35,py36`
Reorganizing tox stuff and making py3-specific requirements 2016-03-11 17:25:28 +01:00
Add tox and travis-ci support Add tox integration to run unittests in supported python releases. Travis-CI is used for test execution. Additionally, the unittest TestQuotePgIdentifier was updated to support using assert_raises_regexp on python-2.6. Sample travis-ci output available at https://travis-ci.org/ansible/ansible/builds/54189977 2015-03-11 00:38:37 +01:00			`[testenv]`
Update tox.ini to use ansible-test. 2017-06-30 23:53:32 +02:00			`deps = -c{toxinidir}/test/runner/requirements/constraints.txt`
			`-r{toxinidir}/test/runner/requirements/ansible-test.txt`
			`-r{toxinidir}/test/runner/requirements/sanity.txt`
			`-r{toxinidir}/test/runner/requirements/units.txt`
Testing additions and fixes * Fix import pathing for units.mock * Add some additional requirements * Use compileall to test compatiblity with different python versions 2015-05-08 18:34:19 +02:00			`commands =`
Push python2.4 check into travis 2015-08-01 07:50:05 +02:00			`python --version`
Update tox.ini to use ansible-test. 2017-06-30 23:53:32 +02:00			`# The recommended method of running tests with tox is to execute`
			`# ansible-test directly and use the --tox and --python options.`
			`# The commands below are provided as a convenience for those who`
			`# prefer to run tox directly instead of through ansible-test.`
			`{toxinidir}/test/runner/ansible-test compile --python default -v`
			`{toxinidir}/test/runner/ansible-test sanity --python default -v`
			`{toxinidir}/test/runner/ansible-test units --python default -v`
Pass the HOME environment variable to testenv in tox.ini In order to avoid the "missing HOME variable" issue when running the unit tests, this patch is passing the HOME environment variable to [testenv]. Fixes #20424 2017-01-18 22:48:11 +01:00			`passenv =`
			`# Pass HOME to the test environment to avoid the missing HOME env`
			`# variable error. See issue: #20424`
			`HOME`
Start a pyflakes section to cut down on extra messages that we don't agree are problems 2015-11-11 16:50:19 +01:00
Fail hard when tests pass that are expected to fail `@pytest.mark.xfail()` can be used to decorate tests that don't yet pass. By default, if I wrote a test like this: ``` @pytest.mark.xfail() def test_naughty(): assert 1 == 1 ``` Then Pytest would allow this test to pass without notifying that an expected-fail didn't fail. To make that happen, you have to set xfail_strict=True so that the above test would cause the tests to fail. 2017-12-05 22:36:24 +01:00			`[pytest]`
			`xfail_strict = true`
Start a pyflakes section to cut down on extra messages that we don't agree are problems 2015-11-11 16:50:19 +01:00
			`[flake8]`
			`# These are things that the devs don't agree make the code more readable`
Update tox.ini to match current standards tox.ini is used for flake8 configuration in addition to tox configuration. Update the flake8 configuration to match the latest standards as documented in ansible/proposals#50 2017-02-03 05:49:33 +01:00			`# E402 module level import not at top of file`
update the flake8 config in tox.ini 2017-04-05 17:22:07 +02:00			`ignore = E402`
Start a pyflakes section to cut down on extra messages that we don't agree are problems 2015-11-11 16:50:19 +01:00			`# not all the devs believe in 80 column line length`
			`max-line-length = 160`