TestDriven.NET vs. NUNIT GUI w/ class level Ignore attribute.

Skip to first unread message


Nov 1, 2007, 12:21:20 PM11/1/07
to TestDriven.NET Users
I have applied the NUNIT Ignore attribute to a number of classes in my
test project. When I run these test assemblies in the NUNIT GUI, the
tests in those classes are ignored (as expected). When I run these
test assemblies in my main developer machine using TestDriven .NET
that was built a while ago, the tests in those classes are also
ignored. So far so good.

The problem I am having is that when I execute the tests on a newly
built machine using TestDriven .NET, it appears to ignore the Ignore
attribute and attempt to run all of the tests in the class.

Any ideas?


Brad Wilson

Nov 1, 2007, 12:28:40 PM11/1/07
to TestDri...@googlegroups.com
Sometimes (very rarely) the ad-hoc framework runner actually ends up running things that should've been handled elsewhere. You can tell the ad-hoc runner is the one that's running in two ways: 1. the methods in error reports are prepended with "M:". 2. the frameworks normally strip out the bits of the stack trace that come from the framework itself (during an assert), but the ad-hoc runner does not.

If you see either one of these "symptoms", then the tests are being run by the wrong runner.
Reply all
Reply to author
0 new messages