diff options
| author | Damien Lespiau <damien.lespiau@intel.com> | 2015-09-22 17:11:45 +0100 |
|---|---|---|
| committer | Stephen Finucane <stephen.finucane@intel.com> | 2015-11-05 03:56:28 +0000 |
| commit | 403c144d086ec7c21c61cb24b0eadd1cfbd7fe88 (patch) | |
| tree | fba347ec984b92157208b23c6cda85a8525ee36d /tox.ini | |
| parent | e12cc2028d1a54611da0f4dbf92f7393f67cc72a (diff) | |
| download | patchwork-403c144d086ec7c21c61cb24b0eadd1cfbd7fe88.tar patchwork-403c144d086ec7c21c61cb24b0eadd1cfbd7fe88.tar.gz | |
tests: Use --noinput when running tests
We don't want prompts when running tests, especially when they are run
through tox and most likely on a CI server.
When cancelling a test mid-way, the test db is not destroyed ans
subsequent runs will fail trying to create it and asking the user what
to do. --noinput will use the default answer, that is to destroy the
test db and start anew.
v2: Rebase on top of upstream
v3: Rebase, yet again.
Signed-off-by: Damien Lespiau <damien.lespiau@intel.com>
Acked-by: Stephen Finucane <stephen.finucane@intel.com> (v2)
Diffstat (limited to 'tox.ini')
| -rw-r--r-- | tox.ini | 4 |
1 files changed, 2 insertions, 2 deletions
@@ -14,7 +14,7 @@ deps = setenv = DJANGO_SETTINGS_MODULE = patchwork.settings.dev commands = - {toxinidir}/manage.py test '{posargs:patchwork}' + {toxinidir}/manage.py test --noinput '{posargs:patchwork}' passenv = http_proxy HTTP_PROXY https_proxy HTTPS_PROXY no_proxy NO_PROXY PW_TEST_DB_USER PW_TEST_DB_PASS @@ -45,5 +45,5 @@ setenv = commands = coverage erase coverage run --omit=*tox*,patchwork/tests/*.py,manage.py --branch \ - {toxinidir}/manage.py test patchwork + {toxinidir}/manage.py --noinput test patchwork coverage report -m |