Skip to content

Commit

Permalink
Documented how to run exhaustive tests
Browse files Browse the repository at this point in the history
  • Loading branch information
mihnita committed Dec 9, 2024
1 parent e23801f commit edf6e86
Showing 1 changed file with 4 additions and 1 deletion.
5 changes: 4 additions & 1 deletion docs/processes/cldr-icu.md
Original file line number Diff line number Diff line change
Expand Up @@ -472,12 +472,15 @@ mvn install -pl main/common_tests -Dtest=MeasureUnitTest#TestGreek
13b. Optionally run the tests in exhaustive mode

Optionally run before committing changes, or run to diagnose failures from
running exhaustive CI tests in the PR using `/azp run CI-Exhaustive`:
running exhaustive CI tests in the PR using exhaustive localy:
```sh
cd $ICU4J_ROOT
mvn install -DICU.exhaustive=10 2>&1 | tee $NOTES/icu4j-newData-mvnCheckEx.txt
```

Exhaustive tests in CL can ve triggered by running the "Exhaustive Tests for ICU"
action from the GitHub web UI.

Running a specific test is the same as above:
```sh
mvn install --pl :core -DICU.exhaustive=10 -Dtest=ExhaustiveNumberTest
Expand Down

0 comments on commit edf6e86

Please sign in to comment.