This is a side effect of how TestDriven.Net executes its tests. Rather
than crawl the target assembly looking for tests, both the discovery
and execution of tests is delegated to the plugin test runners.
TestDriven.Net passes a test path to the test runner, rather that a
complete list of tests to be executed.
When a subfolder is targeted, TestDriven.Net looks at the first class
in each of the contained source files. If all of the classes are in
the same namespace, the test runner will attempt to execute all tests
in the target namespace. If the classes are in mixed namespaces, it
will attempt to execute the first class in each source as a separate
test run (which can be very slow).
To make this work, try to ensure that all of your test classes for a
given folder are in the same namespace. Also, try putting the test
class first in the source file followed by any utility classes you're
using.
I know this setup isn't ideal, but changing it as this stage would be
very tricky.
Regards,
Jamie.
--
http://www.testdriven.net
http://twitter.com/jcansdale
http://weblogs.asp.net/nunitaddin
> --
> You received this message because you are subscribed to the Google Groups
> "TestDriven.NET Users" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/testdrivenusers/-/u3-SUApXi-0J.
> To post to this group, send email to testdri...@googlegroups.com.
> To unsubscribe from this group, send email to
> testdrivenuse...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/testdrivenusers?hl=en.
>