Comment 3 for bug 1091138

> ... PNUnit is only intended to
run test methods.

Ok. That makes sense then. I know it was meant for client server tests and I guess it then makes sense that the launcher synchronizes each agent with a test method.

On the other hand, the cumbersome part of PNUnit right now is the .conf files and getting the results back into a report.
Support for TestFixtures and namespaces could lighten the .conf files a bit.

As a side info we we generate the .conf files using reflection on the test assembly. We do it like this since we have .conf files dependent on number of cores on target CPU (to avoid timeouts) and the programmer really shouldn't waste time on keeping the .conf files updated. We use the TimeOut attribute and a few custom attributes to bundle tests together to optimize running time since the Launcher waits for all agents to complete a batch of tests. In our case it would be awesome if the Launcher kept the agents busy, but I can see that this doesn't really match the current design.

In any case thumbs up for an interesting piece of software that is currently closing a gap in the world of automated tests.