Re: establishing logical test order?
"Charlie Poole" <[email protected]>
| Newsgroups | gmane.comp.windows.dotnet.nunit.user |
|---|---|
| Message-ID | <00b801c8d58c$e460dc70$6401a8c0@ferrari> |
What about giving tests a "criticality" level, settable by an attribute. They could then be queried on that basis. Charlie _____ From: [email protected] [mailto:[email protected]] On Behalf Of David Jeske Sent: Monday, June 23, 2008 9:50 AM To: [email protected] Subject: [Nunit-users] establishing logical test order? How do you all go about establishing a logical test order? So far, I'm using naming conventions in my TestFixture classes and Test methods. They all start with "A##_", where ## is the level number of the tests. A00_BasicLowLevelStuff T00_SimplestConcept T01_MoreComplicated T02_StillMoreComplicated T03_MostComplicated A01_NextLevelStuff A02_HighLevelStuff A03_MyApplication Is this similar to what others do? Note that this isn't about execution order of the tests. It's merely about organizing the failures so I start looking at the earliest failure. I've read that JUnit intentionally randomizes the execution order, to help you assure that the tests are not dependent on the output of other tests. That seems like a neat feature, and one NUnit might consider in the future. ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Nunit-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nunit-users