The Visual Studio Test Explorer user interface have been nearly the same since 2012, with only a few minor updates. One thing that have annoyed a few people are how the test names are displayed. The Test Explorer have got a bit of critique on this, but it is not that hardcoded. It can be tweaked! With NUnit3 and the NUnit3TestAdapter version 3.8 you can configure this naming yourself, which makes for some interesting possibilities.
Problem
The default naming scheme is that the test name is equal to the test method. You can then group them based on project, outcome, duration, namespace and even class. The class grouping is pretty nice, and is close to what we want to see, but you can’t combine this with the others. With only a few tests this is ok, but when the number of tests goes up over the 100’s and even 1000’s it starts to became harder to locate what you want.
The practice of using both the class and the method name combined to express your intent is also pretty common, but the grouping mechanism in Test Explorer makes it hard to get the full benefit of this practice.
Let us take a simple example just for illustration:
Here we follow sort of the Given-When-Then pattern, but it could be anything, it just is one example where the class name can be seen as part of the wanted test name.
It could also so simple that multiple test methods in different classes have the same name. They would come out as equal, but displayed separately, in the Test Explorer but you would not know where they belonged (unless you used the Class grouping). So you loose context.
It will come out like this:
Just imagine 500 tests like this – it is not easy to separate them.
Solution
Now, NUnit3 has a concept of Test Names, which can be configured, either individually, or globally. It is done by adding a Test Name Template Pattern to the test.
Added to a single test it looks like this:
The default pattern is just “{m}{a}” which means Methodname+Arguments. When we add the “{c}.” we get the class name in front. And as seen the Test Explorer now displays the tests with this combination.
This is the basic principle, but we can’t go and change all the tests to enter this pattern. The next step is therefore to add a runsettings file and enable that.
If you already haven’t, go and download the item template for the runsettings files. That done, you can add one out of 3 possible templates for the runsettings. For this purpose, just choose and add the simplest one, which is the Parallell template. In the end of the file you find the NUnit settings. Add the same name template to the DefaultTestNamePattern:
Now, enable choose and enable this runsettings file from the Test/Test Settings/Select Test Settings File, and then it will be selectable.
and voila! You have proper test naming for all your tests!
Having a runsettings file present is a good thing anyway, because that is also used to control code coverage and a lot of other settings. Using it to set the test name pattern just solves one more issue, and makes your developer life a little bit easier!
Traps
Now every rose has it’s thorn, and in this case even if there is really no big disadvantages, there are just a couple of things you would expect to work, but which unfortunately doesn’t.
- Test Name patterns are ignored by the Live Unit Testing. This is a known bug in LUT, and you can find one report and the Microsoft answer to it here. If you enable LUT you will both the new name and the old name together, a bit confusing, although only the LUT names will be run.
- We have also noted that the display names are currently not being used in the VSTest task, neither in version 1.0 nor 2.0.
