I am using NCrunch with MSpec on Visual Studio 2010, using C#, and .net 4.
From the NCrunch Tests view, when I double-click on a test, or I right-click and select Go to selected test, it doesn't do anything.
I was using 1.39 until today, I upgraded to 1.40b to see if it fixed it (I've read about fixes in that area) and it didn't.
I will say that when I first started using NCrunch, it didn't work and then it started working for a little while, but has since stopped.
Also, the NUnit tests work fine, it goes to the test, but the MSpec doesn't.
Anything else I can provide? Great product, by the way.
Jeff
Remco NCrunch Developer
#2337
03 Jul 2012 09:02 UTC
Hi Jeff,
Thanks for posting!
Do you experience this problem with all tests? Does it also happen for other test frameworks on your system?
Also, does it appear to be specific to any one solution, or all solutions you use NCrunch on?
Thanks for posting!
Do you experience this problem with all tests? Does it also happen for other test frameworks on your system?
Also, does it appear to be specific to any one solution, or all solutions you use NCrunch on?
I'm guessing that this only applies to tests that are "inconclusive" in mspec, at least that is the case for me.
So given a spec like this....
It should_do_something;
NCrunch won't navigate to that test from the tests window or what not, but if it's a successful or failed test that has an actual implementation, then it works fine.
So given a spec like this....
It should_do_something;
NCrunch won't navigate to that test from the tests window or what not, but if it's a successful or failed test that has an actual implementation, then it works fine.
Remco NCrunch Developer
#2515
25 Jul 2012 23:58 UTC
This is caused by a technical limitation of tests without a body, as these tests have no representation in the PDB file and therefore NCrunch isn't able to 'find' them in the source code.
I'm afraid there aren't any quick fixes to this. It will need to be addressed as a long term problem. Thanks for reporting it!
I'm afraid there aren't any quick fixes to this. It will need to be addressed as a long term problem. Thanks for reporting it!
Post a reply
Log in to reply.