| Reporter |
Matthew Smit (programmdude.1)
|
|---|---|
| Created | Dec 6, 2017 1:25:10 PM |
| Updated | Apr 13, 2018 1:22:23 PM |
| Subsystem | Unit Testing |
| Assignee | Eugene Strizhok (Eugene.Strizhok) |
| Priority | Show-stopper |
| State | Open |
| Type | Performance Problem |
| Fix version | 2018.2 |
| Affected versions | 2017.3 |
| Fixed In Version ReSharper | Undefined |
| VsVersion | All Versions |
When using the resharper unit test system, there is a large delay between telling resharper to run the unit tests, and the test runner starting.
This is not a new issue, it's been like this for at least 6 months. I am using XUnit, although I have tried nunit with the same results. I am currently running Visual Studio 2017 with resharper 2017.3 EAP 8 on Windows 10 x64. The task runner application is CPU bound both waiting for the tests to start, and running the tests.
It takes around 30 seconds between telling resharper to run the unit tests, and the test runner executing any tests. It makes no difference if I run all the tests or if I run just one test. The actual tests are fairly fast to run, around 1 per second per core.
There are 14948 tests in my unit test project, which is likely the reason for it taking a long time to start up.
Note, I am not talking about the time to run the tests, that is dependant on what is in the tests. I am talking about the time between the UI action and the test runner running a test.