Command line should provide an option for run timeout

[vinaychandra]

The current --timeout parameter when invoking command line sets the per-test timeout. Can we also have an option for the full timeout for the test run similar to RunConfiguration.Test SessionTimeout from vstest?

[ChrisMaddock]

@vinaychandra

Can I ask what the motivation for this is?

I would have thought the main purpose of timeout is to kill particularly tests which may be flaky/unreliable. That doesn't really work the same way across an entire test run. What did you want to do with this functionality?

[mikkelbu]

I'll try to provide some motivation.

At my work we have prior had problems on certain old CI setups which have a max timeout for each step in the pipeline. Sometimes the tests took a lot longer than expected - or a lot of tests where added when we merged in new functionality - making the test-step fail with a timeout and no information from nunit, since the process was just killed. Of cause we could just set the timeout to something very large, but a few times we have also run into tests that did not terminate :(.

Hence, it would be nice if the console could be stopped more controlled, so that it would be possible to get a (partial) result and perhaps also some indication of the last/current test executing.

[CharliePoole]

Pretty easy to create a run-level timeout. Partial output is harder. Tentatively adding this to 4.0 milestone, but "we'll see."