Re: [Pyunit-interest] pyunit command
Brought to you by:
purcell
From: Stephen P. <ste...@ya...> - 2000-05-01 01:33:41
|
Hi Michal (and all), I'm very happy that you have taken the time to describe your experiences, and your suggestions make a lot of sense. When projects amass a large number of tests, they absolutely *must* be organised sanely. Such sanity is a subjective standard, and would necessarily vary from project to project. I would therefore be wary of suggesting a 'general' convention for this kind of thing, even if you and I would probably do things the way you describe. The DistUtil case is an important one to consider. From what I can see, the DistUtil people do not impose any particular structure on distributions, except for the presence of an appropriately capable 'setup.py' that can programmatically oversee compilation, installation, testing and so on. A 'setup.py' could work quite easily with the existing framework code, so the question is how to conveniently arrange sets of tests. I would tend to stick with explicitly grouping test cases into suites, and then grouping those suites into further high-level suites. Others may prefer to automagically construct suites based on naming conventions (*.suite() etc). I will get in touch with Greg Stein, who seems to be doing much of the DistUtils work, and see what he thinks. Very best wishes, -Steve _____________________________________________ Steve Purcell, Technical Director, Inkontact Get in touch at http://www.inkontact.com/ |