[Template] Support for TUnit as testframework

[samtrion]

With existing support for various testing frameworks, it would be great if the current offering could be extended with TUnit.

TUnit is a rising star that challenges existing test frameworks such as xUnit and NUnit. Especially in terms of simplified syntax and performance, it clearly stands out from the existing test frameworks without sacrificing familiar features.

[linkdotnet]

Hey @samtrion

Besides that we don’t offer templates for TUnit - is there anything missing or not working?
It should work without any problem (didn’t try it until now).

[samtrion]

@linkdotnet Support as a template was meant when this issue was created.

Switching to TUnit can be done in 3 simple steps after creation. Therefore, there is not much to consider.

1. mark all tests as [Test].
2. remove reference to Microsoft.NET.Test.Sdk from the .csproj file
3. adjust OutputType to <OutputType>Exe</OutputType> in the project file

After that it works without problems.

[samtrion]

It should also be noted that there is an ambiguous reference between Bunit.TestContext and TUnit.Core.TestContext.

[linkdotnet]

We can add the template. And probably we will do this only for v2 of Bunit.

The whole TestContext name conflict will be a thing of the past as we rename it to BunitContext.

[linkdotnet]

We have to check how nice TUnit plays together with our templates, given that we use Microsoft.NET.Sdk.Razor. So there are multiple (custom) source code generators at work.

[samtrion]

We have to check how nice TUnit plays together with our templates, given that we use Microsoft.NET.Sdk.Razor. So there are multiple (custom) source code generators at work.

I was just able to run a few tests with both the latest stable and the current 2 preview version. No noticeable problems so far

[linkdotnet]

Did you use the "classic" C# tests or tests written in razor files?

[samtrion]

So far only classic tests

[linkdotnet]

Short test from my side:

warning CS8892: Method 'TestingPlatformEntryPoint.Main(string[])' will not be used as an entry point because a synchronous entry point 'AutoGeneratedProgram.Main(string[])' was found.

Seems there is some work to do.

[samtrion]

Short test from my side:

warning CS8892: Method 'TestingPlatformEntryPoint.Main(string[])' will not be used as an entry point because a synchronous entry point 'AutoGeneratedProgram.Main(string[])' was found.

Seems there is some work to do.

Shouldn't be a big problem

[linkdotnet]

Spicey! Thanks for the link

[linkdotnet]

One step further - have to try a bit more when I have more time.
Current state of affairs: It does compile, but doesn't discover any test.

[samtrion]

One step further - have to try a bit more when I have more time. Current state of affairs: It does compile, but doesn't discover any test.

As mentioned here, or in my previous message

Switching to TUnit can be done in 3 simple steps after creation. Therefore, there is not much to consider.

1. mark all tests as [Test].
2. remove reference to Microsoft.NET.Test.Sdk from the .csproj file
3. adjust OutputType to <OutputType>Exe</OutputType> in the project file

After that it works without problems.

And you have to adjust your IDE ...

• Visual Studio
• JetBrains Rider
• VS Code

[linkdotnet]

No that does work indeed. The problem seems the generated C# file from the razor code.
So something like:

@using Bunit
@using TUnit.Core;

@inherits Bunit.BunitContext

@code
{
    [Test]
    public void CounterStartsAtZero()
    {
        var cut = Render(@<Counter />);

        cut.Find("p").MarkupMatches(@<p>Current count: 0</p>);
    }
}

Will not have any discoverable test.

[linkdotnet]

PS: I am only using the CLI ATM

[linkdotnet]

The main issue with razor files is that they will be taken care of by the compiler, and C# files are generated.

As of now, a source code generator can not see or use the output of another generator. Somewhere on the roslyn repo there is an issue addressing exactly that. So, therefore, if people want to use TUnit, they might be locked in "csharp" only.

From the point of view of the template, that wouldn't be a big issue. And we have to document that somewhere in our docs.

[linkdotnet]

Using Microsoft.NET.Sdk.Razor will lead to such an output:

dotnet run

████████╗██╗   ██╗███╗   ██╗██╗████████╗
╚══██╔══╝██║   ██║████╗  ██║██║╚══██╔══╝
   ██║   ██║   ██║██╔██╗ ██║██║   ██║   
   ██║   ██║   ██║██║╚██╗██║██║   ██║   
   ██║   ╚██████╔╝██║ ╚████║██║   ██║   
   ╚═╝    ╚═════╝ ╚═╝  ╚═══╝╚═╝   ╚═╝   
   
   TUnit v0.6.154.0 | 64-bit | Darwin 24.2.0 Darwin Kernel Version 24.2.0: Fri Dec  6 18:56:34 PST 2024; root:xnu-11215.61.5~2/RELEASE_ARM64_T6020 | osx-arm64 | .NET 8.0.10 | Microsoft Testing Platform v1.4.3
   

Test run summary: Zero tests ran - bin/Debug/net8.0/test.dll (net8.0|arm64)
  total: 0
  failed: 0
  succeeded: 0
  skipped: 0
  duration: 59ms

While plain old cs files with Microsoft.NET.Sdk

████████╗██╗   ██╗███╗   ██╗██╗████████╗
╚══██╔══╝██║   ██║████╗  ██║██║╚══██╔══╝
   ██║   ██║   ██║██╔██╗ ██║██║   ██║   
   ██║   ██║   ██║██║╚██╗██║██║   ██║   
   ██║   ╚██████╔╝██║ ╚████║██║   ██║   
   ╚═╝    ╚═════╝ ╚═╝  ╚═══╝╚═╝   ╚═╝   
   
   TUnit v0.6.154.0 | 64-bit | Darwin 24.2.0 Darwin Kernel Version 24.2.0: Fri Dec  6 18:56:34 PST 2024; root:xnu-11215.61.5~2/RELEASE_ARM64_T6020 | osx-arm64 | .NET 8.0.10 | Microsoft Testing Platform v1.4.3
   
failed CounterStartsAtZero (186ms)
  Bunit.ElementNotFoundException: No elements were found that matches the selector 'p'

Basically a test is run

[linkdotnet]

I do have a version that might do the trick (C# only). @egil let's discuss this on Friday latest.