Skip to content

Enhance engine modes documentation with Reflection mode details #3030

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
thomhurst merged 1 commit into from
Sep 6, 2025
Merged

Enhance engine modes documentation with Reflection mode details #3030

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions docs/docs/execution/engine-modes.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,8 @@ TUnit can run in two modes:

When publishing with Native AOT, the source generation mode provides additional performance benefits and full AOT compatibility.

The Reflection mode allows discovery of test cases that have been source generated by something other than TUnit, though, for example .razor files in bUnit.

## Source Generation Mode (Default)

By default, TUnit always uses source generation for test discovery and execution:
Expand All @@ -36,6 +38,8 @@ Enable reflection mode by running:
dotnet test -- --reflection
```

Alternatively, setting the environment variable `TUNIT_EXECUTION_MODE` to `reflection` enables the reflection engine mode globally.

## Native AOT Support

When publishing with Native AOT, TUnit's source generation mode provides additional benefits:
Expand Down