-
-
Notifications
You must be signed in to change notification settings - Fork 111
perf: run test executable directly and remove SingleFile test mode #4718
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.
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
Conversation
Run the built TUnit.TestProject executable directly instead of going through `dotnet run --no-build`, eliminating CLI overhead on every engine test invocation. Remove SingleFileApplication test mode since AOT already covers trimming coverage, saving both CI build time and test execution time. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Code reviewNo issues found. Checked for bugs and CLAUDE.md compliance. This is a well-executed performance optimization that aligns with TUnit's "Performance First" principle. The changes eliminate the |
Code reviewNo issues found. Checked for bugs and CLAUDE.md compliance. This PR represents a solid performance optimization that aligns well with TUnit's "Performance First" principle. The changes: Performance improvement: Running test executables directly eliminates the overhead of the Code cleanup: Removing the Consistent patterns: The executable discovery logic in Clean refactoring: All references to |
Summary
dotnet run --no-buildin engine tests, eliminating thedotnetCLI process startup and project resolution overhead on every test invocationSingleFileApplicationtest mode — AOT already covers trimming coverage, so this was redundantTest plan
🤖 Generated with Claude Code