Is there life without Resharper - 2?
After checking that it is possible to do navigation in the studio and without a resharper , I decided to investigate the following important scenario for me: namely, unit testing in the studio (using the nunit test framework ).
Resharper quite well supports the ability to run tests (implemented using nunit) directly from the studio. A brief description of the features can be found here .
')
several screenshots (resharper):
test run (debugging):
test viewer:
test session window
You also need to add a screen with possible resharper options (one parallel is worth it!):
After this “wealth” I began to explore the built-in (or alternative) solutions.
First of all, a purely studio does not support tests from nunit, but you can debug tests using NUnit itself in this perverted way:
Where
"Start external program": C: \ Program Files (x86) \ NUnit 2.6.2 \ bin \ nunit.exe
"Command line arguments:" mock-assembly.dll /fixture:NUnit.Tests.TestAssembly.MockTestFixture
"Working directory": D: \ My \ MyProjects \ MySharper \ NUnit-2.6.2-src \ NUnit-2.6.2 \ bin \ Debug \ tests
And if now run the test project through the command Debug | Start new instance, then NUnit will rise with the desired test class and you can run tests, and breakpoints will work.
It is clear that this method is very "slow." In order to take advantage of the built-in features, the authors of NUnit have implemented an adapter that can be installed from the gallery .
But, unfortunately, I still could not run the tests from the NUnit source codes (Visual Studio 2013, Reshaper 8) due to the error:
Googling, found two open "ticket":
bugs.launchpad.net/nunit-vs-adapter/+bug/1203587
youtrack.jetbrains.com/issue/RSRP-380922
The capabilities of the built-in “Test Explorer” window are more than covered by a resharper, it can be, except for the “Group by | Duration or Group by | Traits ”(I don’t know how beautifully to translate, Google translated it like this:“ Group of traits ” ), which allows you to group tests according to various other properties (work time, attributes of the tests themselves).
grouping example:
I tried to run tests in different conditions: sometimes it worked, but by eye, much slower than resharper.
Also found the status of the test directly above the test itself:
A blue icon means that the test has not yet been launched.
It is also interesting that for some reason the studio does not allow the test to be run directly from the code editor, but it allows the test to be run from the method called by the test:
It looks like a bug.
Total , in principle, as it is, it is possible to work in the studio with nunit tests (especially when the adapter is repaired). In addition (regardless of resharper), there are a couple of interesting things that expand the programmer.
Thank,
Igor
Resharper quite well supports the ability to run tests (implemented using nunit) directly from the studio. A brief description of the features can be found here .
')
several screenshots (resharper):
test run (debugging):
test viewer:
test session window
You also need to add a screen with possible resharper options (one parallel is worth it!):
After this “wealth” I began to explore the built-in (or alternative) solutions.
First of all, a purely studio does not support tests from nunit, but you can debug tests using NUnit itself in this perverted way:
Where
"Start external program": C: \ Program Files (x86) \ NUnit 2.6.2 \ bin \ nunit.exe
"Command line arguments:" mock-assembly.dll /fixture:NUnit.Tests.TestAssembly.MockTestFixture
"Working directory": D: \ My \ MyProjects \ MySharper \ NUnit-2.6.2-src \ NUnit-2.6.2 \ bin \ Debug \ tests
And if now run the test project through the command Debug | Start new instance, then NUnit will rise with the desired test class and you can run tests, and breakpoints will work.
It is clear that this method is very "slow." In order to take advantage of the built-in features, the authors of NUnit have implemented an adapter that can be installed from the gallery .
But, unfortunately, I still could not run the tests from the NUnit source codes (Visual Studio 2013, Reshaper 8) due to the error:
------ Run test started ------ Could not find test executor with URI 'executor://nunittestexecutor/'. Make sure that the test executor is installed and supports .net runtime version 4.0.30319.18213. ========== Run test finished: 0 run (0:00:43.9573953) ========== Googling, found two open "ticket":
bugs.launchpad.net/nunit-vs-adapter/+bug/1203587
youtrack.jetbrains.com/issue/RSRP-380922
The capabilities of the built-in “Test Explorer” window are more than covered by a resharper, it can be, except for the “Group by | Duration or Group by | Traits ”(I don’t know how beautifully to translate, Google translated it like this:“ Group of traits ” ), which allows you to group tests according to various other properties (work time, attributes of the tests themselves).
grouping example:
I tried to run tests in different conditions: sometimes it worked, but by eye, much slower than resharper.
Also found the status of the test directly above the test itself:
A blue icon means that the test has not yet been launched.
It is also interesting that for some reason the studio does not allow the test to be run directly from the code editor, but it allows the test to be run from the method called by the test:
It looks like a bug.
Total , in principle, as it is, it is possible to work in the studio with nunit tests (especially when the adapter is repaired). In addition (regardless of resharper), there are a couple of interesting things that expand the programmer.
Thank,
Igor
Source: https://habr.com/ru/post/189200/
All Articles