openstack/horizon
Code Issues Proposed changes
235c60c8dc
horizon/tox.ini

165 lines
4.5 KiB
INI
Raw Normal View History

Add ProjectTestingInterface to horizon. Horizon is the last project that doesn't have support for the common Project Testing Interface. This gets horizon up to speed with the other bits, but shouldn't break any of the existing interfaces. Change-Id: I464c3b10d9708a0b7b5ffd42c88cd3cf515ef6a7
2012-05-26 14:58:14 -04:00
[tox]
Drop py34 target in tox.ini Change-Id: Ic2c7016344ec3be49e52bcdf0db6da2ccb58f4f7
2017-03-23 20:50:25 +08:00
envlist = pep8,py27dj{18,19,110},py35,releasenotes,npm
Refactor tox & update docs - Updated tox envlist, so just running `tox` from the CLI will now run all voting gate tests - Reduce duplicated definitions and commands - Remove any reliance on run_tests within tox - Removes all doc references to run_tests.sh, and replaces them with their tox equivalent. Where necessary, language around the tox commands has been altered or extended so that it makes sense and is consistent with other parts of the docs. Also adds a new "Test Environment" list to the docs, so that newcomers do not have to piece together CLI commands and their cryptic extensions from tox.ini - Move the inline shell scripting to its own file. Also fixes a bug when passing args, since the logic assumed you were attempting a subset test run (try `tox -e py27 -- --pdb` on master to compare) - Moved translation tooling from run_tests to manage.py, w/ help text and arg restrictions. This is much more flexible so that plugins can use it without having to copy commands, but still defaults to exactly the same parameters/behaviour from run_tests. Docs updated appropriately. - Removed npm/karma strange reliance on either .venv or tox/py27. Now it only uses tox/npm. Change-Id: I883f885bd424955d39ddcfde5ba396a88cfc041e Implements: blueprint enhance-tox Closes-Bug: 1638672
2016-10-06 14:27:22 +01:00
minversion = 2.3.2
Updates tox.ini to use new features Reasons: - tox update v1.6 Changes: - tox 1.6 allows us to skip the sdist step, which is slow. - It also allows us to override the install line. In this case, it's important as it allows us to stop getting pre-release software we weren't asking for. Original patch by Monty Taylor, talked about here: http://lists.openstack.org/pipermail/openstack-dev/2013-September/015495.html Change-Id: I0b2da3369ec303b9997305f602e6c444cafe14b0
2013-12-09 14:17:48 +00:00
skipsdist = True
Add ProjectTestingInterface to horizon. Horizon is the last project that doesn't have support for the common Project Testing Interface. This gets horizon up to speed with the other bits, but shouldn't break any of the existing interfaces. Change-Id: I464c3b10d9708a0b7b5ffd42c88cd3cf515ef6a7
2012-05-26 14:58:14 -04:00
[testenv]
Use upper-constraints in tox test environments Recently OpenStack introduced a mechanism to specify a constrained "working set" of packages that are "guaranteed" to produce a working OpenStack environment. This pinning of packages limits the more broadly-defined requirements.txt which is managed by global-requirements. This patch modifies our tox test environment to use upper-constraints and explictly removes those requirements from the "venv" tox environment that is used by some commands in infra. Change-Id: I84582370e139fc5812bc85ae5341f7f9c8b93ff5 Closes-Bug: 1554791
2016-03-09 11:30:20 +11:00
install_command = pip install -c{env:UPPER_CONSTRAINTS_FILE:https://git.openstack.org/cgit/openstack/requirements/plain/upper-constraints.txt} {opts} {packages}
Enhances tox to not rely on run_tests Several changes: - Dont rely on run_tests.sh and run the commands directly - Move the coverage options to the setup.cfg - Set py27 envs under the same umbrella - Split horizon and openstack_dashboard tests into 2 different envs - Remove usedevelop from most envs as its not needed - Set basepython to 27 on the default env - Allow adding posargs to py34 env - Add npm environment which defaults to npm run test - Add runserver as a new env - Move pep8 to be the first tests so we fail fast - Provide an env to tests against system packages, useful for package builders that DONT want to test against pip install but their local packages installation. - Allow to pass TOX_EXTRA_DEPS to the system_packages tests in case some extra pip packages are needed - Add a manage env to pass commands to manage.py - Add an environment to createmessages - Add an environment to check only if we can create messages - pep8 environment also runs the check for messages - All python commands use {envpython} so no escape from the venv is possible - Uses {toxinidir} for a clear indication of where the files to be executed are - Moves all keywords for pybabel to the setup.cfg - Removes not needed whitelist_external for all envs and uses only git for one specific env Change-Id: Ia1be8f60265d9dab2639a05912b4b7c51f1d4033 Implements: blueprint enhance-tox
2015-12-17 13:23:36 +01:00
setenv =
VIRTUAL_ENV={envdir}
INTEGRATION_TESTS=0
NOSE_WITH_OPENSTACK=1
NOSE_OPENSTACK_SHOW_ELAPSED=1
Refactor tox & update docs - Updated tox envlist, so just running `tox` from the CLI will now run all voting gate tests - Reduce duplicated definitions and commands - Remove any reliance on run_tests within tox - Removes all doc references to run_tests.sh, and replaces them with their tox equivalent. Where necessary, language around the tox commands has been altered or extended so that it makes sense and is consistent with other parts of the docs. Also adds a new "Test Environment" list to the docs, so that newcomers do not have to piece together CLI commands and their cryptic extensions from tox.ini - Move the inline shell scripting to its own file. Also fixes a bug when passing args, since the logic assumed you were attempting a subset test run (try `tox -e py27 -- --pdb` on master to compare) - Moved translation tooling from run_tests to manage.py, w/ help text and arg restrictions. This is much more flexible so that plugins can use it without having to copy commands, but still defaults to exactly the same parameters/behaviour from run_tests. Docs updated appropriately. - Removed npm/karma strange reliance on either .venv or tox/py27. Now it only uses tox/npm. Change-Id: I883f885bd424955d39ddcfde5ba396a88cfc041e Implements: blueprint enhance-tox Closes-Bug: 1638672
2016-10-06 14:27:22 +01:00
whitelist_externals =
bash
Add '*.pyc' clean up for unit_tests After updating code from actual branch we still use old *.pyc files. It can give an unexpected result, for instance, a lot of tests are broken due to unknown reasons. This patch fixes this issue. Change-Id: I3bdbad9748dc3d94d6d8914156604eab7ad877a0
2017-07-07 13:28:41 +03:00
find
Make nosehtmloutput an optional test requirement It is not strictly needed. Change-Id: I37b2623ec834533a7ecae63084e2c2c04ecc1751
2017-08-21 14:50:05 +02:00
deps = .[test]
Enhances tox to not rely on run_tests Several changes: - Dont rely on run_tests.sh and run the commands directly - Move the coverage options to the setup.cfg - Set py27 envs under the same umbrella - Split horizon and openstack_dashboard tests into 2 different envs - Remove usedevelop from most envs as its not needed - Set basepython to 27 on the default env - Allow adding posargs to py34 env - Add npm environment which defaults to npm run test - Add runserver as a new env - Move pep8 to be the first tests so we fail fast - Provide an env to tests against system packages, useful for package builders that DONT want to test against pip install but their local packages installation. - Allow to pass TOX_EXTRA_DEPS to the system_packages tests in case some extra pip packages are needed - Add a manage env to pass commands to manage.py - Add an environment to createmessages - Add an environment to check only if we can create messages - pep8 environment also runs the check for messages - All python commands use {envpython} so no escape from the venv is possible - Uses {toxinidir} for a clear indication of where the files to be executed are - Moves all keywords for pybabel to the setup.cfg - Removes not needed whitelist_external for all envs and uses only git for one specific env Change-Id: Ia1be8f60265d9dab2639a05912b4b7c51f1d4033 Implements: blueprint enhance-tox
2015-12-17 13:23:36 +01:00
-r{toxinidir}/requirements.txt
-r{toxinidir}/test-requirements.txt
commands =
Refactor tox & update docs - Updated tox envlist, so just running `tox` from the CLI will now run all voting gate tests - Reduce duplicated definitions and commands - Remove any reliance on run_tests within tox - Removes all doc references to run_tests.sh, and replaces them with their tox equivalent. Where necessary, language around the tox commands has been altered or extended so that it makes sense and is consistent with other parts of the docs. Also adds a new "Test Environment" list to the docs, so that newcomers do not have to piece together CLI commands and their cryptic extensions from tox.ini - Move the inline shell scripting to its own file. Also fixes a bug when passing args, since the logic assumed you were attempting a subset test run (try `tox -e py27 -- --pdb` on master to compare) - Moved translation tooling from run_tests to manage.py, w/ help text and arg restrictions. This is much more flexible so that plugins can use it without having to copy commands, but still defaults to exactly the same parameters/behaviour from run_tests. Docs updated appropriately. - Removed npm/karma strange reliance on either .venv or tox/py27. Now it only uses tox/npm. Change-Id: I883f885bd424955d39ddcfde5ba396a88cfc041e Implements: blueprint enhance-tox Closes-Bug: 1638672
2016-10-06 14:27:22 +01:00
horizon: {envpython} {toxinidir}/manage.py test --settings=horizon.test.settings {posargs}
manage: {envpython} {toxinidir}/manage.py {posargs}
py27: {[unit_tests]commands}
py35: {[unit_tests]commands}
openstack_dashboard: {envpython} {toxinidir}/manage.py test --settings=openstack_dashboard.test.settings {posargs}
runserver: {envpython} {toxinidir}/manage.py runserver {posargs}
venv: {posargs}
Add ProjectTestingInterface to horizon. Horizon is the last project that doesn't have support for the common Project Testing Interface. This gets horizon up to speed with the other bits, but shouldn't break any of the existing interfaces. Change-Id: I464c3b10d9708a0b7b5ffd42c88cd3cf515ef6a7
2012-05-26 14:58:14 -04:00
Enable Python 3.5 testing and fix tests Fixes to a couple of places to make the python 3.5 tests pass. Change-Id: I3f4b73b24fbe336ac6c80b7aa224a830ab7e36a6
2016-09-06 12:15:50 +10:00
[testenv:py35]
setenv =
Refactor tox & update docs - Updated tox envlist, so just running `tox` from the CLI will now run all voting gate tests - Reduce duplicated definitions and commands - Remove any reliance on run_tests within tox - Removes all doc references to run_tests.sh, and replaces them with their tox equivalent. Where necessary, language around the tox commands has been altered or extended so that it makes sense and is consistent with other parts of the docs. Also adds a new "Test Environment" list to the docs, so that newcomers do not have to piece together CLI commands and their cryptic extensions from tox.ini - Move the inline shell scripting to its own file. Also fixes a bug when passing args, since the logic assumed you were attempting a subset test run (try `tox -e py27 -- --pdb` on master to compare) - Moved translation tooling from run_tests to manage.py, w/ help text and arg restrictions. This is much more flexible so that plugins can use it without having to copy commands, but still defaults to exactly the same parameters/behaviour from run_tests. Docs updated appropriately. - Removed npm/karma strange reliance on either .venv or tox/py27. Now it only uses tox/npm. Change-Id: I883f885bd424955d39ddcfde5ba396a88cfc041e Implements: blueprint enhance-tox Closes-Bug: 1638672
2016-10-06 14:27:22 +01:00
PYTHONUNBUFFERED = 1
Enable Python 3.5 testing and fix tests Fixes to a couple of places to make the python 3.5 tests pass. Change-Id: I3f4b73b24fbe336ac6c80b7aa224a830ab7e36a6
2016-09-06 12:15:50 +10:00
{[testenv]setenv}
Refactor tox & update docs - Updated tox envlist, so just running `tox` from the CLI will now run all voting gate tests - Reduce duplicated definitions and commands - Remove any reliance on run_tests within tox - Removes all doc references to run_tests.sh, and replaces them with their tox equivalent. Where necessary, language around the tox commands has been altered or extended so that it makes sense and is consistent with other parts of the docs. Also adds a new "Test Environment" list to the docs, so that newcomers do not have to piece together CLI commands and their cryptic extensions from tox.ini - Move the inline shell scripting to its own file. Also fixes a bug when passing args, since the logic assumed you were attempting a subset test run (try `tox -e py27 -- --pdb` on master to compare) - Moved translation tooling from run_tests to manage.py, w/ help text and arg restrictions. This is much more flexible so that plugins can use it without having to copy commands, but still defaults to exactly the same parameters/behaviour from run_tests. Docs updated appropriately. - Removed npm/karma strange reliance on either .venv or tox/py27. Now it only uses tox/npm. Change-Id: I883f885bd424955d39ddcfde5ba396a88cfc041e Implements: blueprint enhance-tox Closes-Bug: 1638672
2016-10-06 14:27:22 +01:00
commands = {[unit_tests]commands}
Enable Python 3.5 testing and fix tests Fixes to a couple of places to make the python 3.5 tests pass. Change-Id: I3f4b73b24fbe336ac6c80b7aa224a830ab7e36a6
2016-09-06 12:15:50 +10:00
Fix py27dj18 definition py27dj18 currently uses Django 1.10 (from upper-constraints.txt). The Django version should be specified explicitly. Change-Id: I23a6dda4da52a0758e2f3e3bff26795c161babb8
2017-07-08 21:02:44 +00:00
[testenv:py27dj18]
commands =
pip install -U django>=1.8,<1.9
{[unit_tests]commands}
Refactor tox & update docs - Updated tox envlist, so just running `tox` from the CLI will now run all voting gate tests - Reduce duplicated definitions and commands - Remove any reliance on run_tests within tox - Removes all doc references to run_tests.sh, and replaces them with their tox equivalent. Where necessary, language around the tox commands has been altered or extended so that it makes sense and is consistent with other parts of the docs. Also adds a new "Test Environment" list to the docs, so that newcomers do not have to piece together CLI commands and their cryptic extensions from tox.ini - Move the inline shell scripting to its own file. Also fixes a bug when passing args, since the logic assumed you were attempting a subset test run (try `tox -e py27 -- --pdb` on master to compare) - Moved translation tooling from run_tests to manage.py, w/ help text and arg restrictions. This is much more flexible so that plugins can use it without having to copy commands, but still defaults to exactly the same parameters/behaviour from run_tests. Docs updated appropriately. - Removed npm/karma strange reliance on either .venv or tox/py27. Now it only uses tox/npm. Change-Id: I883f885bd424955d39ddcfde5ba396a88cfc041e Implements: blueprint enhance-tox Closes-Bug: 1638672
2016-10-06 14:27:22 +01:00
[testenv:py27dj19]
Add check for makemessages in tox.ini PEP8 This commit adds a check of extracting message catalogs to tox PEP8 check. It is useful to avoid a bug like bug 1379054. It also fixes a warning "WARNING:root:No local_settings file found." in run_tests.sh --makemessages and --compilemessages by specifying Django settings. Closes-Bug: #1379507 Change-Id: I5541e28a87d48601202bf8180a18eadb5a91770b
2014-10-10 05:16:31 +09:00
commands =
Refactor tox & update docs - Updated tox envlist, so just running `tox` from the CLI will now run all voting gate tests - Reduce duplicated definitions and commands - Remove any reliance on run_tests within tox - Removes all doc references to run_tests.sh, and replaces them with their tox equivalent. Where necessary, language around the tox commands has been altered or extended so that it makes sense and is consistent with other parts of the docs. Also adds a new "Test Environment" list to the docs, so that newcomers do not have to piece together CLI commands and their cryptic extensions from tox.ini - Move the inline shell scripting to its own file. Also fixes a bug when passing args, since the logic assumed you were attempting a subset test run (try `tox -e py27 -- --pdb` on master to compare) - Moved translation tooling from run_tests to manage.py, w/ help text and arg restrictions. This is much more flexible so that plugins can use it without having to copy commands, but still defaults to exactly the same parameters/behaviour from run_tests. Docs updated appropriately. - Removed npm/karma strange reliance on either .venv or tox/py27. Now it only uses tox/npm. Change-Id: I883f885bd424955d39ddcfde5ba396a88cfc041e Implements: blueprint enhance-tox Closes-Bug: 1638672
2016-10-06 14:27:22 +01:00
pip install -U django>=1.9,<1.10
{[unit_tests]commands}
Enhances tox to not rely on run_tests Several changes: - Dont rely on run_tests.sh and run the commands directly - Move the coverage options to the setup.cfg - Set py27 envs under the same umbrella - Split horizon and openstack_dashboard tests into 2 different envs - Remove usedevelop from most envs as its not needed - Set basepython to 27 on the default env - Allow adding posargs to py34 env - Add npm environment which defaults to npm run test - Add runserver as a new env - Move pep8 to be the first tests so we fail fast - Provide an env to tests against system packages, useful for package builders that DONT want to test against pip install but their local packages installation. - Allow to pass TOX_EXTRA_DEPS to the system_packages tests in case some extra pip packages are needed - Add a manage env to pass commands to manage.py - Add an environment to createmessages - Add an environment to check only if we can create messages - pep8 environment also runs the check for messages - All python commands use {envpython} so no escape from the venv is possible - Uses {toxinidir} for a clear indication of where the files to be executed are - Moves all keywords for pybabel to the setup.cfg - Removes not needed whitelist_external for all envs and uses only git for one specific env Change-Id: Ia1be8f60265d9dab2639a05912b4b7c51f1d4033 Implements: blueprint enhance-tox
2015-12-17 13:23:36 +01:00
Refactor tox & update docs - Updated tox envlist, so just running `tox` from the CLI will now run all voting gate tests - Reduce duplicated definitions and commands - Remove any reliance on run_tests within tox - Removes all doc references to run_tests.sh, and replaces them with their tox equivalent. Where necessary, language around the tox commands has been altered or extended so that it makes sense and is consistent with other parts of the docs. Also adds a new "Test Environment" list to the docs, so that newcomers do not have to piece together CLI commands and their cryptic extensions from tox.ini - Move the inline shell scripting to its own file. Also fixes a bug when passing args, since the logic assumed you were attempting a subset test run (try `tox -e py27 -- --pdb` on master to compare) - Moved translation tooling from run_tests to manage.py, w/ help text and arg restrictions. This is much more flexible so that plugins can use it without having to copy commands, but still defaults to exactly the same parameters/behaviour from run_tests. Docs updated appropriately. - Removed npm/karma strange reliance on either .venv or tox/py27. Now it only uses tox/npm. Change-Id: I883f885bd424955d39ddcfde5ba396a88cfc041e Implements: blueprint enhance-tox Closes-Bug: 1638672
2016-10-06 14:27:22 +01:00
[testenv:py27dj110]
Enhances tox to not rely on run_tests Several changes: - Dont rely on run_tests.sh and run the commands directly - Move the coverage options to the setup.cfg - Set py27 envs under the same umbrella - Split horizon and openstack_dashboard tests into 2 different envs - Remove usedevelop from most envs as its not needed - Set basepython to 27 on the default env - Allow adding posargs to py34 env - Add npm environment which defaults to npm run test - Add runserver as a new env - Move pep8 to be the first tests so we fail fast - Provide an env to tests against system packages, useful for package builders that DONT want to test against pip install but their local packages installation. - Allow to pass TOX_EXTRA_DEPS to the system_packages tests in case some extra pip packages are needed - Add a manage env to pass commands to manage.py - Add an environment to createmessages - Add an environment to check only if we can create messages - pep8 environment also runs the check for messages - All python commands use {envpython} so no escape from the venv is possible - Uses {toxinidir} for a clear indication of where the files to be executed are - Moves all keywords for pybabel to the setup.cfg - Removes not needed whitelist_external for all envs and uses only git for one specific env Change-Id: Ia1be8f60265d9dab2639a05912b4b7c51f1d4033 Implements: blueprint enhance-tox
2015-12-17 13:23:36 +01:00
commands =
Refactor tox & update docs - Updated tox envlist, so just running `tox` from the CLI will now run all voting gate tests - Reduce duplicated definitions and commands - Remove any reliance on run_tests within tox - Removes all doc references to run_tests.sh, and replaces them with their tox equivalent. Where necessary, language around the tox commands has been altered or extended so that it makes sense and is consistent with other parts of the docs. Also adds a new "Test Environment" list to the docs, so that newcomers do not have to piece together CLI commands and their cryptic extensions from tox.ini - Move the inline shell scripting to its own file. Also fixes a bug when passing args, since the logic assumed you were attempting a subset test run (try `tox -e py27 -- --pdb` on master to compare) - Moved translation tooling from run_tests to manage.py, w/ help text and arg restrictions. This is much more flexible so that plugins can use it without having to copy commands, but still defaults to exactly the same parameters/behaviour from run_tests. Docs updated appropriately. - Removed npm/karma strange reliance on either .venv or tox/py27. Now it only uses tox/npm. Change-Id: I883f885bd424955d39ddcfde5ba396a88cfc041e Implements: blueprint enhance-tox Closes-Bug: 1638672
2016-10-06 14:27:22 +01:00
pip install -U django>=1.10,<1.11
{[unit_tests]commands}
Add Django 1.11 tox env Change-Id: If26325ec260135064e178fa2254ddf7026bbce67
2017-07-05 11:12:16 +01:00
[testenv:py27dj111]
commands =
pip install -U django>=1.11,<2.0
{[unit_tests]commands}
Refactor tox & update docs - Updated tox envlist, so just running `tox` from the CLI will now run all voting gate tests - Reduce duplicated definitions and commands - Remove any reliance on run_tests within tox - Removes all doc references to run_tests.sh, and replaces them with their tox equivalent. Where necessary, language around the tox commands has been altered or extended so that it makes sense and is consistent with other parts of the docs. Also adds a new "Test Environment" list to the docs, so that newcomers do not have to piece together CLI commands and their cryptic extensions from tox.ini - Move the inline shell scripting to its own file. Also fixes a bug when passing args, since the logic assumed you were attempting a subset test run (try `tox -e py27 -- --pdb` on master to compare) - Moved translation tooling from run_tests to manage.py, w/ help text and arg restrictions. This is much more flexible so that plugins can use it without having to copy commands, but still defaults to exactly the same parameters/behaviour from run_tests. Docs updated appropriately. - Removed npm/karma strange reliance on either .venv or tox/py27. Now it only uses tox/npm. Change-Id: I883f885bd424955d39ddcfde5ba396a88cfc041e Implements: blueprint enhance-tox Closes-Bug: 1638672
2016-10-06 14:27:22 +01:00
[unit_tests]
Add '*.pyc' clean up for unit_tests After updating code from actual branch we still use old *.pyc files. It can give an unexpected result, for instance, a lot of tests are broken due to unknown reasons. This patch fixes this issue. Change-Id: I3bdbad9748dc3d94d6d8914156604eab7ad877a0
2017-07-07 13:28:41 +03:00
commands =
find . -type f -name "*.pyc" -delete
bash {toxinidir}/tools/unit_tests.sh {envpython} {toxinidir} {posargs}
Enhances tox to not rely on run_tests Several changes: - Dont rely on run_tests.sh and run the commands directly - Move the coverage options to the setup.cfg - Set py27 envs under the same umbrella - Split horizon and openstack_dashboard tests into 2 different envs - Remove usedevelop from most envs as its not needed - Set basepython to 27 on the default env - Allow adding posargs to py34 env - Add npm environment which defaults to npm run test - Add runserver as a new env - Move pep8 to be the first tests so we fail fast - Provide an env to tests against system packages, useful for package builders that DONT want to test against pip install but their local packages installation. - Allow to pass TOX_EXTRA_DEPS to the system_packages tests in case some extra pip packages are needed - Add a manage env to pass commands to manage.py - Add an environment to createmessages - Add an environment to check only if we can create messages - pep8 environment also runs the check for messages - All python commands use {envpython} so no escape from the venv is possible - Uses {toxinidir} for a clear indication of where the files to be executed are - Moves all keywords for pybabel to the setup.cfg - Removes not needed whitelist_external for all envs and uses only git for one specific env Change-Id: Ia1be8f60265d9dab2639a05912b4b7c51f1d4033 Implements: blueprint enhance-tox
2015-12-17 13:23:36 +01:00
Refactor tox & update docs - Updated tox envlist, so just running `tox` from the CLI will now run all voting gate tests - Reduce duplicated definitions and commands - Remove any reliance on run_tests within tox - Removes all doc references to run_tests.sh, and replaces them with their tox equivalent. Where necessary, language around the tox commands has been altered or extended so that it makes sense and is consistent with other parts of the docs. Also adds a new "Test Environment" list to the docs, so that newcomers do not have to piece together CLI commands and their cryptic extensions from tox.ini - Move the inline shell scripting to its own file. Also fixes a bug when passing args, since the logic assumed you were attempting a subset test run (try `tox -e py27 -- --pdb` on master to compare) - Moved translation tooling from run_tests to manage.py, w/ help text and arg restrictions. This is much more flexible so that plugins can use it without having to copy commands, but still defaults to exactly the same parameters/behaviour from run_tests. Docs updated appropriately. - Removed npm/karma strange reliance on either .venv or tox/py27. Now it only uses tox/npm. Change-Id: I883f885bd424955d39ddcfde5ba396a88cfc041e Implements: blueprint enhance-tox Closes-Bug: 1638672
2016-10-06 14:27:22 +01:00
[testenv:pep8]
Enhances tox to not rely on run_tests Several changes: - Dont rely on run_tests.sh and run the commands directly - Move the coverage options to the setup.cfg - Set py27 envs under the same umbrella - Split horizon and openstack_dashboard tests into 2 different envs - Remove usedevelop from most envs as its not needed - Set basepython to 27 on the default env - Allow adding posargs to py34 env - Add npm environment which defaults to npm run test - Add runserver as a new env - Move pep8 to be the first tests so we fail fast - Provide an env to tests against system packages, useful for package builders that DONT want to test against pip install but their local packages installation. - Allow to pass TOX_EXTRA_DEPS to the system_packages tests in case some extra pip packages are needed - Add a manage env to pass commands to manage.py - Add an environment to createmessages - Add an environment to check only if we can create messages - pep8 environment also runs the check for messages - All python commands use {envpython} so no escape from the venv is possible - Uses {toxinidir} for a clear indication of where the files to be executed are - Moves all keywords for pybabel to the setup.cfg - Removes not needed whitelist_external for all envs and uses only git for one specific env Change-Id: Ia1be8f60265d9dab2639a05912b4b7c51f1d4033 Implements: blueprint enhance-tox
2015-12-17 13:23:36 +01:00
usedevelop = True
commands =
Make extract_messages quiet in pep8 test The additional extract_messages call in the pep8 tox environment generates a lot of meaningless output, that then makes it difficult to spot actual failures and warnings. This patch makes the Django command respect the verbosity setting and call the setup.py command with a quiet flag if low verbosity is requested, considerably decreasing the amount of useless output. It then sets that verbosity to low in the corresponding tox environment. Change-Id: I2976250a23e800fbb582726299670b57199b58a7
2017-03-15 18:41:19 +01:00
{envpython} {toxinidir}/manage.py extract_messages --verbosity 0 --check-only
Refactor tox & update docs - Updated tox envlist, so just running `tox` from the CLI will now run all voting gate tests - Reduce duplicated definitions and commands - Remove any reliance on run_tests within tox - Removes all doc references to run_tests.sh, and replaces them with their tox equivalent. Where necessary, language around the tox commands has been altered or extended so that it makes sense and is consistent with other parts of the docs. Also adds a new "Test Environment" list to the docs, so that newcomers do not have to piece together CLI commands and their cryptic extensions from tox.ini - Move the inline shell scripting to its own file. Also fixes a bug when passing args, since the logic assumed you were attempting a subset test run (try `tox -e py27 -- --pdb` on master to compare) - Moved translation tooling from run_tests to manage.py, w/ help text and arg restrictions. This is much more flexible so that plugins can use it without having to copy commands, but still defaults to exactly the same parameters/behaviour from run_tests. Docs updated appropriately. - Removed npm/karma strange reliance on either .venv or tox/py27. Now it only uses tox/npm. Change-Id: I883f885bd424955d39ddcfde5ba396a88cfc041e Implements: blueprint enhance-tox Closes-Bug: 1638672
2016-10-06 14:27:22 +01:00
flake8
Add ProjectTestingInterface to horizon. Horizon is the last project that doesn't have support for the common Project Testing Interface. This gets horizon up to speed with the other bits, but shouldn't break any of the existing interfaces. Change-Id: I464c3b10d9708a0b7b5ffd42c88cd3cf515ef6a7
2012-05-26 14:58:14 -04:00
Enhances tox to not rely on run_tests Several changes: - Dont rely on run_tests.sh and run the commands directly - Move the coverage options to the setup.cfg - Set py27 envs under the same umbrella - Split horizon and openstack_dashboard tests into 2 different envs - Remove usedevelop from most envs as its not needed - Set basepython to 27 on the default env - Allow adding posargs to py34 env - Add npm environment which defaults to npm run test - Add runserver as a new env - Move pep8 to be the first tests so we fail fast - Provide an env to tests against system packages, useful for package builders that DONT want to test against pip install but their local packages installation. - Allow to pass TOX_EXTRA_DEPS to the system_packages tests in case some extra pip packages are needed - Add a manage env to pass commands to manage.py - Add an environment to createmessages - Add an environment to check only if we can create messages - pep8 environment also runs the check for messages - All python commands use {envpython} so no escape from the venv is possible - Uses {toxinidir} for a clear indication of where the files to be executed are - Moves all keywords for pybabel to the setup.cfg - Removes not needed whitelist_external for all envs and uses only git for one specific env Change-Id: Ia1be8f60265d9dab2639a05912b4b7c51f1d4033 Implements: blueprint enhance-tox
2015-12-17 13:23:36 +01:00
[testenv:cover]
commands =
coverage erase
coverage run {toxinidir}/manage.py test horizon --settings=horizon.test.settings {posargs}
Fix tox cover to not fail This changes the run of tox with cover, to just ammend cover output data.... the combine option seemed to be breaking the data and then the xml / html options did not work as a result. Change-Id: Ic600b55855cf74c1b6ed138fea5c4b7bb037de82 Closes-bug: #1628661
2016-09-28 14:58:48 -06:00
coverage run -a {toxinidir}/manage.py test openstack_dashboard --settings=openstack_dashboard.test.settings --exclude-dir=openstack_dashboard/test/integration_tests {posargs}
Add Django OpenStack Auth to Horizon Moves Django OpenStack Auth content to Horizon, since they are so tightly coupled. This cleans up the development workflow and should make keystone / auth related contributions easier. Implements: blueprint merge-openstack-auth Change-Id: Ia1cdc47bad1ca6e633073a9f9445b0c7f70d05bc
2017-07-11 14:19:57 +01:00
coverage run -a {toxinidir}/manage.py test openstack_auth --settings=openstack_auth.test.settings {posargs}
Enhances tox to not rely on run_tests Several changes: - Dont rely on run_tests.sh and run the commands directly - Move the coverage options to the setup.cfg - Set py27 envs under the same umbrella - Split horizon and openstack_dashboard tests into 2 different envs - Remove usedevelop from most envs as its not needed - Set basepython to 27 on the default env - Allow adding posargs to py34 env - Add npm environment which defaults to npm run test - Add runserver as a new env - Move pep8 to be the first tests so we fail fast - Provide an env to tests against system packages, useful for package builders that DONT want to test against pip install but their local packages installation. - Allow to pass TOX_EXTRA_DEPS to the system_packages tests in case some extra pip packages are needed - Add a manage env to pass commands to manage.py - Add an environment to createmessages - Add an environment to check only if we can create messages - pep8 environment also runs the check for messages - All python commands use {envpython} so no escape from the venv is possible - Uses {toxinidir} for a clear indication of where the files to be executed are - Moves all keywords for pybabel to the setup.cfg - Removes not needed whitelist_external for all envs and uses only git for one specific env Change-Id: Ia1be8f60265d9dab2639a05912b4b7c51f1d4033 Implements: blueprint enhance-tox
2015-12-17 13:23:36 +01:00
coverage xml
coverage html
Adding django 1.6 support Adding tox config to maintain django 1.5 support. Implements: blueprint django-1point6 Change-Id: Id51b61f8ec8f5a1f83b4d3520dfa4273f07db4cb
2014-02-10 12:47:53 -07:00
Refactor tox & update docs - Updated tox envlist, so just running `tox` from the CLI will now run all voting gate tests - Reduce duplicated definitions and commands - Remove any reliance on run_tests within tox - Removes all doc references to run_tests.sh, and replaces them with their tox equivalent. Where necessary, language around the tox commands has been altered or extended so that it makes sense and is consistent with other parts of the docs. Also adds a new "Test Environment" list to the docs, so that newcomers do not have to piece together CLI commands and their cryptic extensions from tox.ini - Move the inline shell scripting to its own file. Also fixes a bug when passing args, since the logic assumed you were attempting a subset test run (try `tox -e py27 -- --pdb` on master to compare) - Moved translation tooling from run_tests to manage.py, w/ help text and arg restrictions. This is much more flexible so that plugins can use it without having to copy commands, but still defaults to exactly the same parameters/behaviour from run_tests. Docs updated appropriately. - Removed npm/karma strange reliance on either .venv or tox/py27. Now it only uses tox/npm. Change-Id: I883f885bd424955d39ddcfde5ba396a88cfc041e Implements: blueprint enhance-tox Closes-Bug: 1638672
2016-10-06 14:27:22 +01:00
[testenv:selenium]
setenv =
{[testenv]setenv}
WITH_SELENIUM=1
SKIP_UNITTESTS=1
commands = {[unit_tests]commands}
Add py27dj19 tox env This adds a failing Django 1.9 tox env. This will be followed by a non-voting Jenkins job to show the tests failing, and then a follow up patch to make them pass. Change-Id: I0534746360266e4a99e014d69ac19ab2d5b44a83 Partially-Implements: blueprint drop-dj17
2016-01-12 18:43:13 +00:00
Refactor tox & update docs - Updated tox envlist, so just running `tox` from the CLI will now run all voting gate tests - Reduce duplicated definitions and commands - Remove any reliance on run_tests within tox - Removes all doc references to run_tests.sh, and replaces them with their tox equivalent. Where necessary, language around the tox commands has been altered or extended so that it makes sense and is consistent with other parts of the docs. Also adds a new "Test Environment" list to the docs, so that newcomers do not have to piece together CLI commands and their cryptic extensions from tox.ini - Move the inline shell scripting to its own file. Also fixes a bug when passing args, since the logic assumed you were attempting a subset test run (try `tox -e py27 -- --pdb` on master to compare) - Moved translation tooling from run_tests to manage.py, w/ help text and arg restrictions. This is much more flexible so that plugins can use it without having to copy commands, but still defaults to exactly the same parameters/behaviour from run_tests. Docs updated appropriately. - Removed npm/karma strange reliance on either .venv or tox/py27. Now it only uses tox/npm. Change-Id: I883f885bd424955d39ddcfde5ba396a88cfc041e Implements: blueprint enhance-tox Closes-Bug: 1638672
2016-10-06 14:27:22 +01:00
[testenv:selenium-headless]
setenv =
{[testenv]setenv}
SELENIUM_HEADLESS=1
WITH_SELENIUM=1
SKIP_UNITTESTS=1
commands = {[unit_tests]commands}
[testenv:selenium-phantomjs]
setenv =
{[testenv]setenv}
SELENIUM_PHANTOMJS=1
WITH_SELENIUM=1
SKIP_UNITTESTS=1
commands = {[unit_tests]commands}
Add Django 1.10 tox env This will be used for a non-voting test run by infra. Change-Id: Ie773fbb2ff8451bc974b570e2e2e7304b72a9e05 Implements: blueprint dj110
2016-06-29 10:18:36 +01:00
Integration tests - running the tests Initial setup for running the integration tests. A basic test is included to ensure this works, although it will be rewritten to follow the Page Object pattern. Thanks to Daniel Korn for the initial test. https://wiki.openstack.org/wiki/Horizon/Testing/UI Implements blueprint: selenium-integration-testing Change-Id: Id5b62cdeac5295667a3922f7bed1db3c7617f841
2013-01-10 14:13:59 +00:00
[testenv:py27integration]
Enhances tox to not rely on run_tests Several changes: - Dont rely on run_tests.sh and run the commands directly - Move the coverage options to the setup.cfg - Set py27 envs under the same umbrella - Split horizon and openstack_dashboard tests into 2 different envs - Remove usedevelop from most envs as its not needed - Set basepython to 27 on the default env - Allow adding posargs to py34 env - Add npm environment which defaults to npm run test - Add runserver as a new env - Move pep8 to be the first tests so we fail fast - Provide an env to tests against system packages, useful for package builders that DONT want to test against pip install but their local packages installation. - Allow to pass TOX_EXTRA_DEPS to the system_packages tests in case some extra pip packages are needed - Add a manage env to pass commands to manage.py - Add an environment to createmessages - Add an environment to check only if we can create messages - pep8 environment also runs the check for messages - All python commands use {envpython} so no escape from the venv is possible - Uses {toxinidir} for a clear indication of where the files to be executed are - Moves all keywords for pybabel to the setup.cfg - Removes not needed whitelist_external for all envs and uses only git for one specific env Change-Id: Ia1be8f60265d9dab2639a05912b4b7c51f1d4033 Implements: blueprint enhance-tox
2015-12-17 13:23:36 +01:00
# Run integration tests only
Implement video capture for failed tests Example of video recording Idd218e09c0f8df8ec7740173d5f2d856b8baafa1 Change-Id: I350950095f840f63638175b09ed083109aada2da Closes-Bug: #1585092
2016-05-23 17:05:00 +03:00
passenv = AVCONV_INSTALLED
Enhances tox to not rely on run_tests Several changes: - Dont rely on run_tests.sh and run the commands directly - Move the coverage options to the setup.cfg - Set py27 envs under the same umbrella - Split horizon and openstack_dashboard tests into 2 different envs - Remove usedevelop from most envs as its not needed - Set basepython to 27 on the default env - Allow adding posargs to py34 env - Add npm environment which defaults to npm run test - Add runserver as a new env - Move pep8 to be the first tests so we fail fast - Provide an env to tests against system packages, useful for package builders that DONT want to test against pip install but their local packages installation. - Allow to pass TOX_EXTRA_DEPS to the system_packages tests in case some extra pip packages are needed - Add a manage env to pass commands to manage.py - Add an environment to createmessages - Add an environment to check only if we can create messages - pep8 environment also runs the check for messages - All python commands use {envpython} so no escape from the venv is possible - Uses {toxinidir} for a clear indication of where the files to be executed are - Moves all keywords for pybabel to the setup.cfg - Removes not needed whitelist_external for all envs and uses only git for one specific env Change-Id: Ia1be8f60265d9dab2639a05912b4b7c51f1d4033 Implements: blueprint enhance-tox
2015-12-17 13:23:36 +01:00
setenv =
PYTHONHASHSEED=0
INTEGRATION_TESTS=1
SELENIUM_HEADLESS=1
NOSE_WITH_OPENSTACK=1
NOSE_OPENSTACK_SHOW_ELAPSED=1
Integration tests - running the tests Initial setup for running the integration tests. A basic test is included to ensure this works, although it will be rewritten to follow the Page Object pattern. Thanks to Daniel Korn for the initial test. https://wiki.openstack.org/wiki/Horizon/Testing/UI Implements blueprint: selenium-integration-testing Change-Id: Id5b62cdeac5295667a3922f7bed1db3c7617f841
2013-01-10 14:13:59 +00:00
basepython = python2.7
Enhances tox to not rely on run_tests Several changes: - Dont rely on run_tests.sh and run the commands directly - Move the coverage options to the setup.cfg - Set py27 envs under the same umbrella - Split horizon and openstack_dashboard tests into 2 different envs - Remove usedevelop from most envs as its not needed - Set basepython to 27 on the default env - Allow adding posargs to py34 env - Add npm environment which defaults to npm run test - Add runserver as a new env - Move pep8 to be the first tests so we fail fast - Provide an env to tests against system packages, useful for package builders that DONT want to test against pip install but their local packages installation. - Allow to pass TOX_EXTRA_DEPS to the system_packages tests in case some extra pip packages are needed - Add a manage env to pass commands to manage.py - Add an environment to createmessages - Add an environment to check only if we can create messages - pep8 environment also runs the check for messages - All python commands use {envpython} so no escape from the venv is possible - Uses {toxinidir} for a clear indication of where the files to be executed are - Moves all keywords for pybabel to the setup.cfg - Removes not needed whitelist_external for all envs and uses only git for one specific env Change-Id: Ia1be8f60265d9dab2639a05912b4b7c51f1d4033 Implements: blueprint enhance-tox
2015-12-17 13:23:36 +01:00
commands = nosetests openstack_dashboard.test.integration_tests {posargs}
Integration tests - running the tests Initial setup for running the integration tests. A basic test is included to ensure this works, although it will be rewritten to follow the Page Object pattern. Thanks to Daniel Korn for the initial test. https://wiki.openstack.org/wiki/Horizon/Testing/UI Implements blueprint: selenium-integration-testing Change-Id: Id5b62cdeac5295667a3922f7bed1db3c7617f841
2013-01-10 14:13:59 +00:00
Enhances tox to not rely on run_tests Several changes: - Dont rely on run_tests.sh and run the commands directly - Move the coverage options to the setup.cfg - Set py27 envs under the same umbrella - Split horizon and openstack_dashboard tests into 2 different envs - Remove usedevelop from most envs as its not needed - Set basepython to 27 on the default env - Allow adding posargs to py34 env - Add npm environment which defaults to npm run test - Add runserver as a new env - Move pep8 to be the first tests so we fail fast - Provide an env to tests against system packages, useful for package builders that DONT want to test against pip install but their local packages installation. - Allow to pass TOX_EXTRA_DEPS to the system_packages tests in case some extra pip packages are needed - Add a manage env to pass commands to manage.py - Add an environment to createmessages - Add an environment to check only if we can create messages - pep8 environment also runs the check for messages - All python commands use {envpython} so no escape from the venv is possible - Uses {toxinidir} for a clear indication of where the files to be executed are - Moves all keywords for pybabel to the setup.cfg - Removes not needed whitelist_external for all envs and uses only git for one specific env Change-Id: Ia1be8f60265d9dab2639a05912b4b7c51f1d4033 Implements: blueprint enhance-tox
2015-12-17 13:23:36 +01:00
[testenv:npm]
Allow Chrome to start when tox is running npm Chrome in *nix environments requires the HOME and DISPLAY variables to be set for Chrome to start properlyi when running the 'npm' rule. The HOME variable is needed so Chrome can load up the user's preferences. The DISPLAY variable is needed so it know what display to launch Chrome into. Change-Id: I84f4d1d47f065158e8f5bf5691c241061cc16aab Closes-Bug: #1684321
2017-04-20 16:37:49 -07:00
passenv =
HOME
DISPLAY
Enhances tox to not rely on run_tests Several changes: - Dont rely on run_tests.sh and run the commands directly - Move the coverage options to the setup.cfg - Set py27 envs under the same umbrella - Split horizon and openstack_dashboard tests into 2 different envs - Remove usedevelop from most envs as its not needed - Set basepython to 27 on the default env - Allow adding posargs to py34 env - Add npm environment which defaults to npm run test - Add runserver as a new env - Move pep8 to be the first tests so we fail fast - Provide an env to tests against system packages, useful for package builders that DONT want to test against pip install but their local packages installation. - Allow to pass TOX_EXTRA_DEPS to the system_packages tests in case some extra pip packages are needed - Add a manage env to pass commands to manage.py - Add an environment to createmessages - Add an environment to check only if we can create messages - pep8 environment also runs the check for messages - All python commands use {envpython} so no escape from the venv is possible - Uses {toxinidir} for a clear indication of where the files to be executed are - Moves all keywords for pybabel to the setup.cfg - Removes not needed whitelist_external for all envs and uses only git for one specific env Change-Id: Ia1be8f60265d9dab2639a05912b4b7c51f1d4033 Implements: blueprint enhance-tox
2015-12-17 13:23:36 +01:00
commands =
nodeenv -p
npm install
npm run {posargs:test}
Establish baseline JSCS configuration Establishes the ability to have JSCS (JS Code Style) run from the run_tests.sh script. Also provides basis for code style configuration. Co-Authored-By: Brian Tully <brian.tully@hp.com> Change-Id: Ib22da5ae05c353d12507a1809ec79e93379acecf Closes-Bug: 1450626
2015-04-02 10:37:32 -06:00
Enhances tox to not rely on run_tests Several changes: - Dont rely on run_tests.sh and run the commands directly - Move the coverage options to the setup.cfg - Set py27 envs under the same umbrella - Split horizon and openstack_dashboard tests into 2 different envs - Remove usedevelop from most envs as its not needed - Set basepython to 27 on the default env - Allow adding posargs to py34 env - Add npm environment which defaults to npm run test - Add runserver as a new env - Move pep8 to be the first tests so we fail fast - Provide an env to tests against system packages, useful for package builders that DONT want to test against pip install but their local packages installation. - Allow to pass TOX_EXTRA_DEPS to the system_packages tests in case some extra pip packages are needed - Add a manage env to pass commands to manage.py - Add an environment to createmessages - Add an environment to check only if we can create messages - pep8 environment also runs the check for messages - All python commands use {envpython} so no escape from the venv is possible - Uses {toxinidir} for a clear indication of where the files to be executed are - Moves all keywords for pybabel to the setup.cfg - Removes not needed whitelist_external for all envs and uses only git for one specific env Change-Id: Ia1be8f60265d9dab2639a05912b4b7c51f1d4033 Implements: blueprint enhance-tox
2015-12-17 13:23:36 +01:00
[testenv:tests_system_packages]
# Provide an environment for system packagers that dont want anything from pip
# Any extra deps needed for this env can be passed by setting TOX_EXTRA_DEPS
sitepackages = True
Pass environment variables of proxy to tox When a development environment is under a proxy, tox fails even if env variables are set, this patch will fix this problem. Change-Id: I8ae234be37937dea804d80a87bb43755c847b4e3
2017-02-06 15:52:35 -06:00
passenv = TOX_EXTRA_DEPS http_proxy HTTP_PROXY https_proxy HTTPS_PROXY no_proxy NO_PROXY
Enhances tox to not rely on run_tests Several changes: - Dont rely on run_tests.sh and run the commands directly - Move the coverage options to the setup.cfg - Set py27 envs under the same umbrella - Split horizon and openstack_dashboard tests into 2 different envs - Remove usedevelop from most envs as its not needed - Set basepython to 27 on the default env - Allow adding posargs to py34 env - Add npm environment which defaults to npm run test - Add runserver as a new env - Move pep8 to be the first tests so we fail fast - Provide an env to tests against system packages, useful for package builders that DONT want to test against pip install but their local packages installation. - Allow to pass TOX_EXTRA_DEPS to the system_packages tests in case some extra pip packages are needed - Add a manage env to pass commands to manage.py - Add an environment to createmessages - Add an environment to check only if we can create messages - pep8 environment also runs the check for messages - All python commands use {envpython} so no escape from the venv is possible - Uses {toxinidir} for a clear indication of where the files to be executed are - Moves all keywords for pybabel to the setup.cfg - Removes not needed whitelist_external for all envs and uses only git for one specific env Change-Id: Ia1be8f60265d9dab2639a05912b4b7c51f1d4033 Implements: blueprint enhance-tox
2015-12-17 13:23:36 +01:00
# Sets deps to an empty list so nothing is installed from pip
deps =
commands =
pip install -U {env:TOX_EXTRA_DEPS:}
Refactor tox & update docs - Updated tox envlist, so just running `tox` from the CLI will now run all voting gate tests - Reduce duplicated definitions and commands - Remove any reliance on run_tests within tox - Removes all doc references to run_tests.sh, and replaces them with their tox equivalent. Where necessary, language around the tox commands has been altered or extended so that it makes sense and is consistent with other parts of the docs. Also adds a new "Test Environment" list to the docs, so that newcomers do not have to piece together CLI commands and their cryptic extensions from tox.ini - Move the inline shell scripting to its own file. Also fixes a bug when passing args, since the logic assumed you were attempting a subset test run (try `tox -e py27 -- --pdb` on master to compare) - Moved translation tooling from run_tests to manage.py, w/ help text and arg restrictions. This is much more flexible so that plugins can use it without having to copy commands, but still defaults to exactly the same parameters/behaviour from run_tests. Docs updated appropriately. - Removed npm/karma strange reliance on either .venv or tox/py27. Now it only uses tox/npm. Change-Id: I883f885bd424955d39ddcfde5ba396a88cfc041e Implements: blueprint enhance-tox Closes-Bug: 1638672
2016-10-06 14:27:22 +01:00
{[unit_tests]commands}
Enhances tox to not rely on run_tests Several changes: - Dont rely on run_tests.sh and run the commands directly - Move the coverage options to the setup.cfg - Set py27 envs under the same umbrella - Split horizon and openstack_dashboard tests into 2 different envs - Remove usedevelop from most envs as its not needed - Set basepython to 27 on the default env - Allow adding posargs to py34 env - Add npm environment which defaults to npm run test - Add runserver as a new env - Move pep8 to be the first tests so we fail fast - Provide an env to tests against system packages, useful for package builders that DONT want to test against pip install but their local packages installation. - Allow to pass TOX_EXTRA_DEPS to the system_packages tests in case some extra pip packages are needed - Add a manage env to pass commands to manage.py - Add an environment to createmessages - Add an environment to check only if we can create messages - pep8 environment also runs the check for messages - All python commands use {envpython} so no escape from the venv is possible - Uses {toxinidir} for a clear indication of where the files to be executed are - Moves all keywords for pybabel to the setup.cfg - Removes not needed whitelist_external for all envs and uses only git for one specific env Change-Id: Ia1be8f60265d9dab2639a05912b4b7c51f1d4033 Implements: blueprint enhance-tox
2015-12-17 13:23:36 +01:00
Use doc8 check doc8 is a linter for documents and used in openstack-manuals. It is better to enforce document linters for simple checking. The current rules are really simple like: - line length check (80 chars) - new line at the end of file Change-Id: I3810df521068ffc97e25a5fc56b72397bf9783bc
2017-07-08 20:53:45 +00:00
[testenv:docs]
commands =
doc8 doc/source
sphinx-build -W -b html doc/source doc/build/html
[testenv:releasenotes]
commands =
doc8 releasenotes/source releasenotes/notes
sphinx-build -a -E -W -d releasenotes/build/doctrees -b html releasenotes/source releasenotes/build/html
Move to flake8. The project is standardizing on flake8 for static code analysis. Change-Id: I4fd97b56b6c6cb57e8d245281e0da15f838ec840
2013-04-20 23:22:39 -07:00
[flake8]
Remove license headers to openstack_dashboard/enabled/* files We don't need license headers in config files. That's why it's safe to skip this check. Change-Id: I1ec3c0ade4377f2ca001e7c48620d76b96caff48
2017-10-09 11:45:57 +03:00
exclude = .venv,.git,.tox,dist,*lib/python*,*egg,build,panel_template,dash_template,local_settings.py,*/local/*,*/test/test_plugins/*,.ropeproject,node_modules,openstack_dashboard/enabled/*
Fix H405 (multi line docstring) warnings (openstack_dashboard) H405: multi line docstring summary not separated with an empty line Closes-Bug: #1696996 Change-Id: Id895695663b19522d9cdc22f8b012e49680d708b
2017-06-09 10:47:12 +00:00
ignore =
Enable some off-by-default hacking rules This commit enables the following two hacking rules which are disabled by default. * H203 Use assertIs(Not)None to check for None * H904 Delay string interpolations at logging calls Recently we clean them up in our code base and it looks better to detect them automatically. Change-Id: I4fb81b1d8e29c21aecd909a54d3294362fe140a2
2017-05-17 20:44:42 +00:00
# Enable the following hacking rules which are disabled by default
# H203 Use assertIs(Not)None to check for None
# H904 Delay string interpolations at logging calls
enable-extensions=H203,H904
[Heat] Fix default values displaying for "Launch Stack" This patch set fixes default values displaying for JSON parameters to make it possible to use them without any changes. Closes-Bug: #1438138 Change-Id: Ib925dc39320f7cab240eed3ccbcf1fa574bc5507
2015-03-30 13:30:17 +03:00
max-complexity = 20
flake8-import-order: Ensure to place project imports last To ensure project imports are placed after third party import, we need to specify application-import-names. Previously flake8-import-check checks only standard imports or not. Change-Id: I9beb2105f686dc7d9aebfce8e21c5e182698e2fe
2017-08-19 07:15:38 +00:00
# flake8-import-order configurations
Use flake8-import-order plugin In reviews we usually check import grouping but it is boring. By using flake8-import-order plugin, we can avoid this. This flake8 plugin is already used in tempest. It enforces loose checking so it sounds good to use. Note that flake8-import-order version is pinned to avoid unexpected breakage of pep8 job. Change-Id: I8ccd05eb70350a2441cc2a4d1eafc09ee690b83b
2017-07-02 10:50:06 +00:00
import-order-style = pep8
flake8-import-order: Ensure to place project imports last To ensure project imports are placed after third party import, we need to specify application-import-names. Previously flake8-import-check checks only standard imports or not. Change-Id: I9beb2105f686dc7d9aebfce8e21c5e182698e2fe
2017-08-19 07:15:38 +00:00
application-import-names = horizon,openstack_dashboard
Remove #noqa from most common imports and add them to import_exceptions We have a lot of import with #noqa that is there to ignore h302, because it's traditional to import and use a name directly, instead of a whole module. This hides other errors and gives people the impression that it's actually fine to import non-modules, you just have to slap #noqa on those lines. I went through the code and identified about a dozen names that are most commonly imported this way. I remove the #noqa tag from them, and added them to the list in import_exceptions. I also removed a few unused imports that were revealed in the process. Change-Id: I27afb8e2b1d4759ec974ded9464d8f010312ee78
2014-01-03 17:31:49 +01:00
[hacking]
Eliminate mutable default arguments The best practice in Python is not to use mutable object (i.e. list, dictionary, or instances of most classes) as value of default argument (see https://goo.gl/Kwhg0T). A hacking rule to enforce this practice is added as well. The patch was inspired by CR https://review.openstack.org/#/c/198465/ and took most of its code from it as well. That's why original copyrights are kept. Closes-Bug: #1471349 Change-Id: Ia77b1736dbc3d4e28ff2d2c3424e9cfcaefa5077
2015-09-21 13:22:59 +03:00
local-check-factory = horizon.hacking.checks.factory
Use doc8 check doc8 is a linter for documents and used in openstack-manuals. It is better to enforce document linters for simple checking. The current rules are really simple like: - line length check (80 chars) - new line at the end of file Change-Id: I3810df521068ffc97e25a5fc56b72397bf9783bc
2017-07-08 20:53:45 +00:00
[doc8]
# File extensions to check
extensions = .rst, .yaml
# Maximal line length should be 80 but we have some overlong lines.
# Let's not get far more in.
max-line-length = 80
# Disable some doc8 checks:
# D000: Check RST validity
# - cannot handle "none" for code-block directive
ignore = D000
Copy Permalink