On Jun 15, 2011, at 02:39 AM, Zygmunt Krynicki wrote: >I agree in the value but I don't want to assume that it is a default practice >or requirement. I package/hack on the webapp (django) side of tests and after >being spoiled with the goodness of python-testtools and python-testscenarios >I ventured to create equivalents (compatible wrappers really) for >django. This means that my packages build depend on 5 additional packages >just for testing. I really hope we could take an 80/20 approach here. IOW, do by default that which *most* packages will benefit from, which IMHO is installing the tests by default. Those packages which have additional dependencies, huge test data, or complicated tests can always add overrides to separate things into a -tests package. Or, make the common things trivial and the difficult things possible. :) -Barry
Attachment:
signature.asc
Description: PGP signature