Compatibility
What TestDetta needs, and what it has been tested with. Anything outside these tables is not necessarily unsupported, but it has not been tested end to end.
Requirements
| Item | Requirement |
|---|---|
| .NET SDK | The .NET 10 SDK runs TestDetta itself. Your tests keep the SDK and runner your repository already uses. |
| Git history | The full history of your branch and its target branch, so the merge base can be found. Shallow clones cannot work. |
| Operating system | Windows x64 and Linux x64 (our CI runs the whole test suite on both for every pull request) and macOS arm64 (the evaluation). Other architectures have not been tested. |
| Legacy project files | Non-SDK .csproj files with packages.config restore and build with the full MSBuild: Visual Studio or its Build Tools on Windows (found through vswhere), Mono's msbuild on macOS and Linux, or the executable that TESTDETTA_MSBUILD names. Their tests run from the compiled assembly through VSTest, the engine of vstest.console.exe. Tested on macOS with Mono. |
Test frameworks and runners
Both runners of dotnet test work. The runner is read from global.json, as dotnet test reads it. These combinations are tested end to end, recording included, also with each framework's own parallelization turned on:
| Framework | VSTest | Microsoft.Testing.Platform |
|---|---|---|
| xUnit v2 | Tested | – |
| xUnit v3 | – | Tested (required for xUnit v3 on the .NET 10 SDK) |
| NUnit | Tested | Tested; add Microsoft.Testing.Extensions.TrxReport so failed tests are known while recording |
| MSTest | Tested | Tested |
| TUnit | – | Tested |
Test projects in the evaluation corpus target .NET 8 to .NET 10. .NET Framework test projects are not part of it.
Target frameworks
The code under test can target any framework: TestDetta reads its source and rewrites its compiled assemblies while recording, whatever they target. What sets a limit is the test project, because recording runs inside its test host.
| Target | Status |
|---|---|
| Code under test: .NET Framework 3.5 and later, .NET Standard 1.0 and later, .NET Core, .NET 5 and later | Supported; a .NET Framework 3.5 library under .NET Framework 4.8 tests is tested |
| Test projects on .NET 8 and later | Tested, the whole evaluation corpus |
| Test projects on .NET 6 and 7 | .NET 6 tested with xUnit v2, NUnit 3 and MSTest 3, on Microsoft.NET.Test.Sdk 17.13 (the last version for them) |
| Test projects on .NET Framework 4.6.2 to 4.8.1 | Tested on Windows with xUnit v2 (4.6.2 and 4.8) and MSTest 1 and 3 (4.8), legacy (non-SDK) solutions included, and the same under Mono on macOS. NUnit 2's adapter is not supported yet. |
| Test projects on .NET Framework 3.5 to 4.6.1 | Not supported: current test platforms need .NET Framework 4.6.2 |
For a test project that targets several frameworks, td record runs its tests for one framework: the one -f names, or else the first in TargetFrameworks that runs on the machine (.NET Framework only on Windows). Without -f, it also reads the generated code and build inputs of the project's other frameworks, which that build produces too, so a change is compared with each framework's own build. What a change selects then depends on the frameworks your tests run for; see Limitations.
Languages
| Language | How changes are handled |
|---|---|
| C#, Visual Basic | Analysed down to members: syntax trees, coverage maps and name tracing. Visual Basic names are matched ignoring case, and the project's root namespace is applied, as the compiler does. |
| F# | Analysed like C#, down to members. Modules count as classes and their let functions as members, as the compiler builds them; indentation counts as code. An inline function is compiled into its callers, so they are found by name. Signature files (.fsi) are not analysed: a change to one runs everything that depends on its project. |
CI systems
Every CI needs the same three things: the full history, the target branch fetched, and a place to keep coverage maps between the default branch and pull requests.
| CI | Setup | Where maps are kept | Summary |
|---|---|---|---|
| GitHub Actions | The action, two steps | The Actions cache, one entry per commit | Job summary, written for you |
| GitLab CI | The td tool, td record and td test | A shared folder or object storage, through --maps-dir | --summary-file writes Markdown for any CI that shows it |
| Jenkins | |||
| Azure DevOps | |||
| Bitbucket Pipelines |