Fixing typo in TESTING.md (#1849)

Signed-off-by: Vacha Shah <vachshah@amazon.com>
This commit is contained in:
Vacha 2022-01-05 05:17:26 -08:00 committed by GitHub
parent 7a38109f4a
commit 6e26679274
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 3 deletions

View File

@ -1,4 +1,4 @@
OpenSearch uses [jUnit](https://junit.org/junit5/) for testing, it also uses randomness in the tests, that can be set using a seed, the following is a cheatsheet of options for running the tests for OpenSearch.
OpenSearch uses [jUnit](https://junit.org/junit5/) for testing, it also uses randomness in the tests, that can be set using a seed. The following is a cheatsheet of options for running the tests for OpenSearch.
- [Requirements](#requirements)
- [Creating packages](#creating-packages)
@ -64,7 +64,7 @@ In order to run OpenSearch from source without building a package, you can run i
### Launching and debugging from an IDE
**NOTE:** If you have imported the project into IntelliJ according to the instructions in [DEVELOPER_GUIDE.md](DEVELOPER_GUIDE.md#importing-the-project-into-intellij-idea), then a debug run configuration named **Debug OpenSearch** will be created for you and configured appropriately.
**NOTE:** If you have imported the project into IntelliJ according to the instructions in [DEVELOPER_GUIDE.md](DEVELOPER_GUIDE.md#intellij-idea), then a debug run configuration named **Debug OpenSearch** will be created for you and configured appropriately.
To run OpenSearch in debug mode,
@ -178,7 +178,7 @@ Change the logging level of OpenSearch (not Gradle)
./gradlew test -Dtests.opensearch.logger.level=DEBUG
Print all the logging output from the test runs to the commandline even if tests are passing.
Print all the logging output from the test runs to the command line even if tests are passing.
./gradlew test -Dtests.output=true