Mikkel Nylander Bundgaard

I think this could be related to #3949

I agree with Joseph's last paragraph in https://github.com/nunit/nunit/issues/3316#issuecomment-511144457 and I think that one issue is fine to begin with. If the work is larger than expected then we can create...

@yetibrain How are you running the tests and which version of NUnit are you using? I've never seen "TIMEOUT OR BROKEN" before and cannot find it in the codebase (the...

1. I think legacy has a negative sound, so in the analyzers we also use "constraint model" vs "classic model" (and I prefer this to legacy). A comment on nunit/nunit.analyzers#9...

Regarding the hang. Perhaps nunit/nunit#2920 will solve this? Att: @MillerJames. Can you try if the "hang" is still there if you compile against the current code from master instead version...

A `SetupFixture` with no namespace should run for the entire assembly https://docs.nunit.org/articles/nunit/writing-tests/attributes/setupfixture.html > A SetUpFixture outside of any namespace provides SetUp and TearDown for the entire assembly. @MMark4 You write...

I just tried to run the code in VS and got the following result ``` ... [02/05/2018 20:15:40 Informational] NUnit3TestExecutor converted 1 of 1 NUnit test cases [02/05/2018 20:15:45 Warning]...

The problem is that we are not (re)setting `now` before we are setting `nextPoll` in 255, hence `nextPoll` will every second iteration not be larger than `now`, since `now` is...

@CharliePoole It also took some print-statements to figure out 😄 .

I can take a look at this, but I've two questions: 1. Do we have any best practises about writing tests that tests time 2. Is the current behaviour of...