CharliePoole

That's how it's designed to work. `[Order]` orders tests within a parent test (suite or fixture). Since each namespace is a suite, the ordering only takes place within that namespace....

I didn't say it was an impossible idea, but only that that's not how it works. Back when NUnit was first designed, it might have been done differently. Maybe we...

@OsirisTerje `SetUpFixture` was created in NUnit V2, so it's original design had nothing to do with parallelism, which we introduced in NUnit3. The original work on parallelism only dealt with...

The notion of "cooperative cancellation" in NUnit refers to cooperation between the runner and the framework itself. The framework stops running any new tests and waits for outstanding tests to...

@JackUkleja Thanks to @Tragedian 's post, I'm looking at this again after a long gap. When I asked you how the user would signal cancellation, what I meant was the...

@oznetmaster The question wasn't "how do you write a program supporting cancel" but "how does the OP currently cancel execution, leading to the described behavior."

Exactly! And only the person who is experiencing the problem can tell us the answer. What you're describing is a solution to one problem, which may eventually turn out to...

I'd definitely like to see us add cooperative cancellation at some point. The framework has an app method that supports "normal" and "forced" stop. We could add the cooperative stop...

Whether this would help you with the R# runner depends on how they are using NUnit, something we are not privy to.

For console runner support to trigger cancel this way, a new issue against that project would be helpful. We'd probably want to allow some time for a normal stop to...