Using os-testr to get better report

As a wrapper of testr, os-testr can provide subunit-trace for output
which is useful for debug.

Change-Id: I99f3a01ea85cbbf2b9a970b75bff19c63f7e44eb
This commit is contained in:
Fei Long Wang 2017-02-02 19:52:30 +13:00 committed by Feilong Wang
parent d23b83503c
commit d3f69d93c0
2 changed files with 3 additions and 2 deletions

View File

@ -23,6 +23,7 @@ testrepository>=0.0.18 # Apache-2.0/BSD
testtools>=1.4.0 # MIT
oslo.db>=4.15.0 # Apache-2.0
testresources>=0.2.4 # Apache-2.0/BSD
os-testr>=0.8.0 # Apache-2.0
# Documentation
sphinx!=1.3b1,<1.4,>=1.2.1 # BSD

View File

@ -14,7 +14,7 @@ deps = -r{toxinidir}/requirements.txt
-r{toxinidir}/test-requirements.txt
commands =
find . -type f -name "*.pyc" -delete
python setup.py testr --slowest --testr-args='--concurrency 1 {posargs}'
ostestr --concurrency 1 {posargs}
whitelist_externals = find
[testenv:pypy]
@ -25,7 +25,7 @@ setenv = {[testenv]setenv}
setenv = {[testenv]setenv}
ZAQAR_TEST_INTEGRATION=1
OS_TEST_PATH=./zaqar/tests/functional
commands = python setup.py testr --slowest --testr-args='--concurrency 1 {posargs}'
commands = ostestr --concurrency 1 {posargs}
[testenv:pep8]
commands = flake8