I run NCrunch 2.24 on Visual Studio 2015 with NUnit 3.4.1 on two different machines. On both maschines all tests starts but not all tests finishes.
In the NCrunch Tests window this tests shows the state 'Running (First time run') but never finishes.
If I change some code in this tests (i.e. the function name) the test runs immediately, but after the next build the same tests have the same problems.
Build/Test Issues
Some tests stay on status 'Running (First time run)'
Started by isb-ik on 5,332 views
Remco NCrunch Developer
#9051
26 Jul 2016 23:40 UTC
Hi, thanks for sharing this issue.
Is there a pattern as to which tests are hanging? Is it possible to examine the test behaviour by running them with the debugger (under NCrunch)? My gut feel is that these tests may have some state or sequence related assumptions causing them to hang (see http://www.ncrunch.net/documentation/considerations-and-constraints_test-atomicity).
NCrunch does have timeout enforcement to stop tests from hanging indefinitely, but unfortunately it isn't perfect. If the tests are hanging on low level service calls, it's possible for them to hang forever if NCrunch isn't able to abort their execution thread.
Is there a pattern as to which tests are hanging? Is it possible to examine the test behaviour by running them with the debugger (under NCrunch)? My gut feel is that these tests may have some state or sequence related assumptions causing them to hang (see http://www.ncrunch.net/documentation/considerations-and-constraints_test-atomicity).
NCrunch does have timeout enforcement to stop tests from hanging indefinitely, but unfortunately it isn't perfect. If the tests are hanging on low level service calls, it's possible for them to hang forever if NCrunch isn't able to abort their execution thread.
It seems to be a problem with the NUnit Version. First I have tried NUnit 3.2.1 but the problem was the same. Then I changed back to NUnit 2.6.3 and then all works fine.
Remco NCrunch Developer
#9053
27 Jul 2016 13:27 UTC
isb-ik wrote:It seems to be a problem with the NUnit Version. First I have tried NUnit 3.2.1 but the problem was the same. Then I changed back to NUnit 2.6.3 and then all works fine.
NCrunch uses a completely different adapter for NUnit v2, so this suggests it's something NUnit v3/NCrunch related ...
Are you able to reproduce anything consistent that you can share with me?
Post a reply
Log in to reply.