nunit-core team mailing list archive

[Charlie Poole <charlie@xxxxxxxxx>]

Well, the console is intended for batch execution, so it naturally just
runs the tests and then exits. This is what most people use in batch jobs,
especially on servers where there may not be an interactive window
available to the scheduled job.

There are intrinsic differences between the two, since the gui is used
for human interaction and maintains the tests loaded for multiple runs.

For that reason, the console has options missing in the Gui and vice
versa.

See the docs for a complete list of options.

Charlie

On Tue, Sep 7, 2010 at 3:23 PM, Rechenelf <629585@xxxxxxxxxxxxxxxxxx> wrote:
> In our project files we have installed always the use of the gui for
> debugging and looking at it. So the easiest way is to use it too for
> profiling. And I must add, I did not know that the console has the
> feature. I had have never a look on it.
>
> Is it very much work to do so?
>
> We also had have a problem with the differences between gui and console
> so we have decided to use gui every time. We are using the call from
> different batch files and they don't know what they are calling.
>
> But it is possible to have the same parameters in console and gui?
>
> --
> /close
> https://bugs.launchpad.net/bugs/629585
> You received this bug notification because you are a member of NUnit
> Developers, which is subscribed to NUnit V2.
>

-- 
/close
https://bugs.launchpad.net/bugs/629585
You received this bug notification because you are a member of NUnit
Developers, which is subscribed to NUnit V2.

Status in NUnit V2 Test Framework: New

Bug description:
As a parameter of the runner program, /close would be a fine option.
If all tests are green or yellow, the runner closes at once if it has finished all tests. This is quite good if you are not interestes in errors but in the performance using a profiler.
We are using the NUnit-test also for profiling when they are working well.