On Fri, Feb 3, 2017 at 11:05 PM, Kamil Paral <kpa...@redhat.com> wrote:
> I spent a bit of time fixing minor issues in our test suite and makefiles > and would like to do the following further changes across all our taskotron > projects: > > 1. run the test suite while inside virtualenv with simple `pytest` command > 2. run the test suite outside of virtualenv with `make test` or `doit > test` and recommend this approach in readme > 3. use a separate virtualenv when running under `make test`, without > --system-site-packages if possible, and ensure up-to-date deps are always > installed, to eliminate any differences that can occur on different setups > The only problem I see here, is that some of the packages that you'd need to install into the test-virtualenv need some C-compilation when installing from PyPi, and that (if used without the --system-site-packages) would mean having to install not only gcc but also plenty of -dev packages. Not a _huge_ ussue but an issue nevertheless. > 4. configure pytest to print out coverage by default, so that it shows up > for both `pytest` and `make test` > > Any concerns or different suggestions? > _______________________________________________ > qa-devel mailing list -- qa-devel@lists.fedoraproject.org > To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org >
_______________________________________________ qa-devel mailing list -- qa-devel@lists.fedoraproject.org To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org
