Re: establishing logical test order?
"Charlie Poole" <[email protected]>
| Newsgroups | gmane.comp.windows.dotnet.nunit.user |
|---|---|
| Message-ID | <001a01c8d5fd$833a7e30$6401a8c0@ferrari> |
Hi Tony, > Since you are already DI-aware and are not using it for the > project which prompted you to post here about ordering > dependent tests then presumably you deem DI not appropriate > for this case, so we may as well end the discussion here > since it's turning into a DI-101 topic instead of an nunit one. I think if you look back, you'll see that David is not using "dependency" in the usual sense, which makes DI moot anyway. If I understand him correctly, he is writing about dependencies in the interpretation of test results, which lead one to want to find the "key" failure that explains many other failures. It's true that such interpretation would be unnecessary if we removed 100% of dependencies, but that's not generally practical, or even desirable. For example, the tests of NUnit itself use a utility method that allows constructing a test case in isolation. I recently broke it, causing a few dozen tests to fail. It took me a few minutes to realize the cause. David is asking for that key failure to be given more prominent display. Charlie ------------------------------------------------------------------------- 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