kubernetes-client/python
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Use py.test instead of nosetests for better problem reporting (#282)

Browse Source 
nosetests output is not very useful for diagnosing issues when
running in travis. Let us switch to py.test
This commit is contained in:
Davanum Srinivas 2017-07-06 21:27:30 -04:00 committed by Mehdy Bohlool
parent bd4b72ebb0
commit 7fd6d559b8
2 changed files with 5 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
test-requirements.txt
View File

@ -1,5 +1,6 @@
coverage>=4.0.3
nose>=1.3.7
pytest
pluggy>=0.3.1
py>=1.4.31
randomize>=0.13

8
tox.ini
View File

@ -9,7 +9,7 @@ deps = -r{toxinidir}/test-requirements.txt
-r{toxinidir}/requirements.txt
commands =
python -V
nosetests -e e2e -v
py.test -vvv -s --ignore=kubernetes/e2e_test
[testenv:docs]
commands =
@ -22,17 +22,17 @@ commands =
[testenv:py27-functional]
commands =
python -V
{toxinidir}/scripts/kube-init.sh nosetests -v []
{toxinidir}/scripts/kube-init.sh py.test -vvv -s []
[testenv:py35-functional]
commands =
python -V
{toxinidir}/scripts/kube-init.sh nosetests -v []
{toxinidir}/scripts/kube-init.sh py.test -vvv -s []
[testenv:py36-functional]
commands =
python -V
{toxinidir}/scripts/kube-init.sh nosetests -v []
{toxinidir}/scripts/kube-init.sh py.test -vvv -s []
[testenv:coverage]
commands =