I haven't really explored the integrated testing support in devpi-server so can't comment on that specifically but I can add some general observations:
I always bundle my tests inside my Python packages so that they are published to PyPI (and as such they would also be included in wheels if I was publishing those) however I seem to be in the tiny minority in the larger Python community on this point :-)
Also, running tests against an installed sdist seems like added value to me, because lots of people get setup.py files wrong on the first few iterations, and this would point out bugs in their installation procedures. On the other hand you could be opening a can of worms, so maybe make this an optional thing? :-)
- Peter Odding
PS. I'm loving devpi-server 2.x, the new web interface is also very nice, so thanks a lot to you and Florian for your effort on devpi-*
On 29 September 2014 12:41, holger krekel hol...@merlinux.eu wrote:
Currently you can't use "devpi test" with wheel files because they don't contain the tests unless you put all tests inside the software archive. To get the tests we could require that there is an "sdist" archive file containing the "tox.ini" file and the tests. Thus "devpi test X" would potentially download two files, a platform specific one and the sdist to configure and perform testing.
Apart from running the tests against the sdist we probably also want to run the tests against the installed sdist. Not sure i grasp all implications yet (also UI wise) but does anyone of you have preliminary thoughts on the issue?
-- You received this message because you are subscribed to the Google Groups "devpi-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to devpi-dev+...@googlegroups.com. To post to this group, send email to devp...@googlegroups.com. Visit this group at http://groups.google.com/group/devpi-dev. For more options, visit https://groups.google.com/d/optout.