Skip to content

Commit

Permalink
[mono][docs] Reflect current workflow of building individual runtime …
Browse files Browse the repository at this point in the history
…tests

Due to optimizing effort of building and running runtime tests #54512, some tests don't generate `*.sh` files by default after build. It is necessary to `export BuildAsStandalone=true` or modify the test's `.csproj` file.

---

Contributes to: #90254
  • Loading branch information
matouskozak authored Dec 15, 2023
1 parent 2987aba commit ffc1c33
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions docs/workflow/testing/mono/testing.md
Original file line number Diff line number Diff line change
Expand Up @@ -20,8 +20,8 @@ cd src/tests
./build.sh mono <release|debug>
```

To build an individual test, test directory, or a whole subdirectory tree, use the `-test:`, `-dir:` or `-tree:` options (without the src/tests prefix)
For example: `./build.sh mono release -test:JIT/opt/InstructionCombining/DivToMul.csproj`
To build an individual test, test directory, or a whole subdirectory tree, use the `-test:`, `-dir:` or `-tree:` options (without the src/tests prefix).
For example: `./build.sh mono release -test:JIT/opt/InstructionCombining/DivToMul.csproj`. To generate executable `.sh` files for tests that are not set to be run individualy it is necessary to `export BuildAsStandalone=true` before building the tests.


Run individual test:
Expand Down

0 comments on commit ffc1c33

Please sign in to comment.