From 403c144d086ec7c21c61cb24b0eadd1cfbd7fe88 Mon Sep 17 00:00:00 2001 From: Damien Lespiau Date: Tue, 22 Sep 2015 17:11:45 +0100 Subject: [PATCH] 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 Acked-by: Stephen Finucane (v2) --- tox.ini | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/tox.ini b/tox.ini index d7eb5b0b..19606e51 100644 --- a/tox.ini +++ b/tox.ini @@ -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 -- 2.47.3