Conversation
|
Tagging subscribers to this area: @agocke, @dotnet/ilc-contrib |
There was a problem hiding this comment.
Pull request overview
Updates the CoreCLR NativeAOT workflow documentation to clarify how to run individual built tests and note that the per-test runner scripts support filtering which tests execute.
Changes:
- Fixes the documented artifacts path for running an individual built test.
- Adds documentation noting that some test projects bundle many tests into one executable and can be filtered via script arguments.
|
|
||
| `$repo_root` is the root of your clone of the repo. | ||
|
|
||
| Some test projects (e.g., `Interop.csproj`) compile many test files into a single native executable. To run only specific tests (filter by namespace, class, method, etc.), pass a filter string to the `[.cmd|.sh]` script, e.g. `$TestName[.cmd|.sh] LayoutClass`. |
There was a problem hiding this comment.
Is this duplicated with coreclr/testing.md? Unless there's an extra native AOT step needed, I'd defer to testing.md. We already link to it below ("For more advanced scenarios"). We could reword that to "For more advanced scenarios involving building and running the tests".
There was a problem hiding this comment.
I'm kind of wondering if we should actually just fold the native AOT testing instructions in testing.md and just call out the extra argument whenever we need it.
Just adding that it's possible to filter the tests run by the script.