Using the code coverage of the VS on my project, it tells me that I'm not having a 100% code coverage because there is one instruction that apparently is never hit.
But if I put a breakpoint in that instruction and perform a test debug, the breakpoint is hit. What can be wrong?
I have a very simple test and the UI does not indicate whether it failed or passed. Basically the UI does not update. I get this error after the test completes:
Machine Specifications Visual Studio Test Adapter - Error while executing specifications in assembly ... - The process cannot access the file 'C:\Users\...\AppData\Local\Temp\d05645cd-e5c0-4c20-8033-f55de314011f\d05645cd-e5c0-4c20-8033-f55de314011f\assembly\dl3\789104d5\6adc2d7e_4ff5cf01' because it is being used by another process.
Why is it looking for that path and how can I fix the issue?
So I looked more into this and seems like if I change the Thread.CurrentPrincipal then the runner does not update the UI. Right now I am saving the original principal and changing it back because the runner needs it.
I hope that helps.
this tool is awesome!
could you make an update so that it fully works with latest version of MSpec and VS2013? I have an issue, that it doesn't display the MSpec Subject.
Also, support for MSpec [Tags] would be great as VS traits.
Not sure if this is the place for asking a question about a bug ...
Today I was running my tests and one of the tests was silently failing (test runner was not reporting it as either passed/failed).
When I ran the tests using the mspec it error's saying that I have more than one because clause in my type hierarhcy (a valid error).
But MSpec adapter did not display the error and was failing silently.
You can simulate this using the code @ https://gist.github.com/Chandu/9807661