Perhaps... but unit tests should *all* run all the time. When you break something, and indeed more than one test fail, go after the lower-level ones first, and the other might go away as well. Sorting the unit tests is not worth it IMHO. We used to do that, list explicitly the test methods to call, and the test classes, to kind of do what you want, but kept on 'loosing' tests. An automatic way to find test is much better. But that's just me!
Cheers, --DD -----Original Message----- From: Tom Lipkis [mailto:[EMAIL PROTECTED]] Sent: Tuesday, October 15, 2002 12:58 PM To: [EMAIL PROTECTED] Subject: Re: Sorting filesets > Note 2: don't write tests that depend on the order of execution, write > your tests to be independent. 8-) Right. They are. I hope I've adequately explained my reasons for this. Thanks, Tom -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
