On Sat, Dec 12, 2009 at 6:39 PM, [email protected] <[email protected]> wrote: > > On Dec 12, 2009, at 12:34 PM, Tarek Ziadé wrote: > >> On Sat, Dec 12, 2009 at 6:29 PM, [email protected] >> <[email protected]> wrote: >>> >>> On Dec 12, 2009, at 11:26 AM, Tarek Ziadé wrote: >>> >>>> There are hundreds of way to break things :) >>>> >>>> IOW everytime a change is made, there's a potential risk. Functional >>>> tests may help >>> >>> Tarek, >>> >>> What are you using for a test suite pre-release now? >> >> I run the test command using python then python3 : >> >> $ python setup.py test >> $ python3 setup.py test >> >> the latter triggers the 2to3 script and launch the tests in build/ >> >>> >>> I started on the multi-package installer we talked about but we >>> never got back together to get it into the release testing. >> >> >> That would be a good timing to continue then ;) > > I'm thinking you're right... > > Do we have a buildout that fails to put into the loop?
any buildout that contains a mrdeveloper egg should trigger that particular problem. For regression testing I think using the plone 4 development .cfg could be a good idea because its quite big and complex _______________________________________________ Distutils-SIG maillist - [email protected] http://mail.python.org/mailman/listinfo/distutils-sig
