On Wednesday 26 March 2008 12:34:04 pm Alec Thomas wrote: > On 27/03/2008, Tim Hatch <[EMAIL PROTECTED]> wrote: > > For just the basic functional tests, leaving the regression tests > > still in one big file? Or categorizing regression tests as well? > > I'd imagine that mostly the same logic would apply, except where it clearly > doesn't make any sense (eg. if the regression test crosses multiple > packages). > > The advantages are: > > 1. It's obvious where the tests for a particular module are. Want Wiki > tests? Look in trac/wiki/tests/. And so on. > 2. It's an implicit Trac "standard".
Ok, please review the new! improved! sandbox/testing branch. PYTHONPATH=.:../genshi-trunk:../twill-0.9 ./..../tests/functional.py will run the functional tests for the module in question. running trac/test.py will run all the tests (unit and functional). Full, redundant demo: for f in ./trac/test.py `find -name functional.py`; do PYTHONPATH=.:../genshi-trunk:../twill-0.9 $f -v || break; done Comments? Eli ------------------. "If it ain't broke now, Eli Carter \ it will be soon." -- crypto-gram [EMAIL PROTECTED] `------------------------------------------------- --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en -~----------~----~----~----~------~----~------~--~---
