chevron-thin-right chevron-thin-left brand cancel-circle search youtube-icon google-plus-icon linkedin-icon facebook-icon twitter-icon toolbox download check linkedin phone twitter-old google-plus facebook profile-male chat calendar profile-male
0 votes
With the test runner enabled, when I edit a test method name the VS code editor responds very slowly and characters typed appear after a long delay. It appears that for each character that is typed the test runner is performing some heavy operation (probably to determine if the method is a valid test method). Also, uncommenting a block of code containing 20 test methods can cause VS to get stuck or stutter for upwards of 15 seconds.

It is easy to demonstrate that the TypeMock test runner is at fault (and not .some other add-in like ReSharper) by performing the following:

1. Try to edit a test method name. VS lags considerably.
2. Add the [DontRun] attribute to the test method and try to edit the method name. VS runs as smooth as butter.

It turns out that with a Core i7-2600 and 16 GB of RAM it's quicker to add [DontRun] before editing the name and remove it after than waiting for the lag (especially if you have to correct typos). But doing that can become really old, really fast.
asked by allon.guralnek (10.6k points)

2 Answers

0 votes
Hi Allon,

We've recreated both cases using your instructions.
Both cases do happen under some conditions, we will look into it.
Thank you for informing us.


Regards,
Alex,
Typemock Support.
answered by alex (18k points)
0 votes
I have found that renaming things that are used by several test methods (in my case using ReSharper) makes visual studio freeze for around 20 seconds. But what really broke my unit testing flow was the original lag when editing a method's name. For me it occurred 100% of the time (and not under "some conditions" like you said) and reached the point of being too disruptive so I had to disable the test runner. That's very unfortunate because it was quite useful, but when you get to the point that it hurts productivity more than it improves it, that's when you have to stop. I hope this gets fixed soon so that I can resume the use of the test runner.
answered by allon.guralnek (10.6k points)
...