Re: how does "stop" work in Nunit GUI?

It seems like it would always be better to run tests in a separate
process. Of course in order for any of this to work, there would need
to be a "test runner" which communicated back the results of tests to
the main nunit gui over IPC.  However, once that is done, it seems
like this would be the best way to always run tests because:

1) the test process could always be "closed" or "force quit" without
affecting nunit gui
2) the test results would remain in nunit gui after the test process was closed
3) it would be simpler to debug or profile a separate testprocess

Once this 'out of process test runner' works, is there a reason to run
tests in the nunit gui process?


On Wed, Jul 9, 2008 at 10:19 AM, Charlie Poole
<[email protected]> wrote:
> We plan some improvements for "Stop" but it can never be
> perfect since threads don't actually have to stop! NUnit
> is actually cancelling your thread, which is pretty
> heavy handed and yet - as you have seen - it still may
> not stop.
>
> The /real/ solution for this, IMO, is to run tests that
> are difficult to stop in a separate process, which can
> be killed if necessary. This too is an enhancement we
> hope to add to the next release.

-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08