-
-
Notifications
You must be signed in to change notification settings - Fork 46
-
After installation the C# unit test run is very slow. If I change the test code and re-run the test, it takes about 50 seconds until it's completed. The majority of time is taken by the build. When I disabled the extension, the total time for the same test after same change, takes 20 seconds only and the build is really fast. Is there a way how to speed it up?
Beta Was this translation helpful? Give feedback.
All reactions
Replies: 4 comments 5 replies
-
Can you provide details on your test framework and if you have set RunMsCodeCoverage Yes.
Beta Was this translation helpful? Give feedback.
All reactions
-
I use the XUnit. RunMsCodeCoverage is set "No"
Beta Was this translation helpful? Give feedback.
All reactions
-
Is this XUnit with Testing Platform ? Do you get the same slowness with RunMsCodeCoverage Yes ?
Beta Was this translation helpful? Give feedback.
All reactions
-
Looks much faster with RunMsCodeCoverage = Yes, but there is no coverage reported.
Beta Was this translation helpful? Give feedback.
All reactions
-
The RunMsCodeCoverage setting should not affect the build.
When you say much faster are you referring to the time that FCC displays coverage ? That is dependent upon RunMsCodeCoverage. When Yes coverage is collected as your tests run when No FCC will wait untill the tests run complete before running the tests again.
Beta Was this translation helpful? Give feedback.
All reactions
-
If there is no coverage reported can you show the FCC Output Window Pane logs.
Beta Was this translation helpful? Give feedback.
All reactions
-
The time I wrote, it FCC Output was completely empty. But today all started to work, the coverage is nicely visible. Just after running test the VS becomes not responding for a minute. Hard to say whether that's caused by the FCC. Anyway thanks for the suggestion to set RunMsCodeCoverage to Yes. I will try to work with that and than again to deactivate to see, if the performance and the responsiveness of the VS could be somehow affected by the FCC.
Beta Was this translation helpful? Give feedback.
All reactions
-
When you are saying vs becomes not responding do you mean that it will not accept your key strokes ?
See this issue - perhaps setting the options mentioned will help
#470
Is this a large project ? Is the problem reproducable in other projects ?
Beta Was this translation helpful? Give feedback.
All reactions
-
You can also check the test explorer output window pane.
Beta Was this translation helpful? Give feedback.