testing.md

Running Tests

Details on test metadata can be found in test-configuration.md.

Build All Tests

1. Build the CoreCLR product
   • Unix
   • macOS
   • Windows
2. Build the libraries in Release configuration. Pass the configuration of CoreCLR you just built to the build script (e.g. -runtimeconfiguration debug).
3. From the src/coreclr directory run the following command:
   • Non-Windows - ./build-test.sh
   • Windows - build-test.cmd
   • Supply -h for usage flags

Test priority

The CoreCLR tests have two priorities, 0 and 1. The priority 0 tests run by default on all pull requests (PRs), while the priority 1 tests run in outerloop CI runs.

Examples

• Build all tests priority 1 and higher
  • build-test.cmd -priority=1
  • build-test.sh -priority1

Build Individual Test

Note: CoreCLR must be built prior to building an individual test. See the first step, above, for building all tests.

• Native Test: Build the generated CMake projects
  • Projects are auto-generated when the build-test.sh/build-test.cmd script is run
    • It is possible to explicitly run only the native test build with build-test.sh/cmd skipmanaged
• Managed Test: Invoke dotnet build on the project directly. dotnet can be the dotnet.sh or dotnet.cmd script in the repo root.

<runtime-repo-root>/dotnet.sh build <runtime-repo-root>/src/coreclr/tests/src/JIT/CodegenBringupTests/Array1_d.csproj /p:Configuration=Release

Additional Documents

• Windows
• Non-Windows