Also alllow TemplateBased naming (for arguments etc.) placeholders in test description about nunit HOT 3 OPEN

The reason for the recommendation to not change the testname is that the Visual Studio test explorer is driven by the testname. However, the default is {m}{a}, so not sure why that should not work for you.

The problem: Now ShouldBeTrue_WhenIsLastFoundAtSameDayAsLimit is just duplicated, I cannot differentiate the tests and see them in NUnit.

I can't see what you're pointing at. I am possibly drowning in the image there. The first image looks like it still has template parameters, but the test code doesn't. I am confused. Can you point it out?

You are correct that the template parameters are for the testname, and not for the description. I am not sure if you want this to work in VS or in NCrunch.

from nunit.

I am possibly drowning in the image there. [...] I am confused. Can you point it out?

Oh I am sorry seems I indeed uploaded the wrong first image I am sorry, I've corrected it in the post.

So the actual problem seems to be that NCrunch always shows the description.

Also to see how NCrunch structures tests the code structure in my example is:

[TestOf(typeof(NotFoundWithinDuration))]
internal class NotFoundWithinDurationTest
{
    // ...
    public class ShouldDelete : NotFoundWithinDurationTest
    {
      // ...

      // ....
      public void
            ShouldBeTrue_WhenLastFoundTimeIsInThePast(int numberOfDaysLastFound, int notFoundLimitInDays)
        {
           // ....
        }
   }

So that is why there is a plus in there etc, it uses the class names for it. That said, this does not matter, actually. NCrunch just always replaces the test name with the NUnit description if it has one. That is the root cause, leading to my tries here...

NCrunch v4.11.0.2 (in my case) with Visual Studio 2022 (17.8.4)

from nunit.

Have you raised an issue with NCrunch about this? It seems to me that the best place to fix this is in NCrunch, so that it doesnt use the description but the testname. In this case you should ignore the recommendation, given that you get a view in TestExplorer or NCrunch that you're happy with.

You could also look into moving the test data into a testcasesource, and then build up the description yourself with the correct parameters.

from nunit.