almalinux/pungi
14
1
Fork 0
Code Issues Pull Requests Releases Activity

Simplify running tests

Browse Source 
There is no need to run the tests both by setup.py and nose: it just
runs the same tests twice. Also, generating coverage data is useless and
it will not be visible anywhere anyway. This allows us to get rid of one
build requires.

Also we should first run unittests and only then build the data for
dummy compose: if the tests fail, we get the info earlier.
This commit is contained in:
Lubomír Sedlář 2016-11-16 09:45:02 +01:00
parent 2a2ed408b8
commit 39a95b7f87
1 changed files with 2 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
pungi.spec
View File

@ -11,7 +11,7 @@ Source0: https://pagure.io/releases/%{name}/%{name}-%{version}.tar.bz2
Patch0: 0001-pungi-Fix-tests-on-non-x86_64-arches.patch
Patch1: 0002-pungi-Fix-incorrectly-skipped-tests.patch
BuildRequires: python-nose, python-nose-cov, python-mock
BuildRequires: python-nose, python-mock
BuildRequires: python-devel, python-setuptools, python2-productmd
BuildRequires: python-lockfile, kobo, kobo-rpmlib, python-kickstart, createrepo_c
BuildRequires: python-lxml, libselinux-python, yum-utils, lorax
@ -77,9 +77,8 @@ gzip _build/man/pungi.1
%{__install} -m 0644 doc/_build/man/pungi.1.gz %{buildroot}%{_mandir}/man1
%check
nosetests --exe
./tests/data/specs/build.sh
%{__python} setup.py test
nosetests --exe --with-cov --cov-report html --cov-config tox.ini
cd tests && ./test_compose.sh
%files