Reputation: 2984
ReSharper Unit Test Runner: Support for Deployment Items
I have a follow up question for the question above. I'm using resharper version 4.5 with native mstest support to run mstest unit tests. When I configure resharper's unit test options to use my testrunconfig (in order to utilize my set of deployment items), my test runs end without displaying any results or errors. Has anyone using resharper's mstest runner had the same issue or anything similar?
Upvotes: 14
Views: 6915
Reputation: 13806
I ran into this problem as well. I didn't want to disable code coverage however, because I often use it. The build server also uses it as well. So I wanted a solution that let me use R#'s runner most of the time for convenience, but still allow me to run my tests with Visual Studio's MSTest runner to get code coverage whenever I wanted as well as allow the build server to continue to generate code coverage statistics.
I created an additional test settings file called Resharper.testsettings. It is exactly the same my normal Local.testsettings file except that it has code coverage disabled. Then I told R# to use this specific test run configuration.
If using R# 5.0 for step 8 there is an extra menu depth:
Upvotes: 8
Reputation: 17863
Having similar problem. My MSTest tests run with Visual Studio test runner but not R#'s runner. The exception thrown is directly attributable to R# test run not finding the files that have to be deployed (and are specified in the testrunconfig).
Tried letting it pick the configured file and specified the file. No dice.
Don't know how to "disable code coverage" in the testrunconfig file other than to not specify any (and I don't).
Have asked R#. Now asking the StackOverflow audience.
Upvotes: 1
Reputation: 62876
You do not need resharper to support standalone mstest installation. I explain how to make a standalone mstest installation without the VS in my post here - http://www.shunra.com/shunrablog/index.php/2009/04/running-mstest-without-visual-studio
Upvotes: 1
Reputation: 2984
Turns out that resharper's mstest runner does not work on testrunconfig files that have code coverage enabled. I've worked around the problem by disabling code coverage in my test run config file.
Upvotes: 8