Fix docs on how to run specific Complement tests after recent complement.sh change (#12664)

This commit is contained in:
Eric Eastwood 2022-05-09 04:38:32 -05:00 committed by GitHub
parent 26c1ad71c5
commit 18d6c18aa1
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 3 additions and 2 deletions

1
changelog.d/12664.doc Normal file
View File

@ -0,0 +1 @@
Fix docs on how to run specific Complement tests using the `complement.sh` test runner.

View File

@ -270,13 +270,13 @@ COMPLEMENT_DIR=../complement ./scripts-dev/complement.sh
To run a specific test file, you can pass the test name at the end of the command. The name passed comes from the naming structure in your Complement tests. If you're unsure of the name, you can do a full run and copy it from the test output: To run a specific test file, you can pass the test name at the end of the command. The name passed comes from the naming structure in your Complement tests. If you're unsure of the name, you can do a full run and copy it from the test output:
```sh ```sh
COMPLEMENT_DIR=../complement ./scripts-dev/complement.sh TestBackfillingHistory COMPLEMENT_DIR=../complement ./scripts-dev/complement.sh -run TestImportHistoricalMessages
``` ```
To run a specific test, you can specify the whole name structure: To run a specific test, you can specify the whole name structure:
```sh ```sh
COMPLEMENT_DIR=../complement ./scripts-dev/complement.sh TestBackfillingHistory/parallel/Backfilled_historical_events_resolve_with_proper_state_in_correct_order COMPLEMENT_DIR=../complement ./scripts-dev/complement.sh -run TestImportHistoricalMessages/parallel/Historical_events_resolve_in_the_correct_order
``` ```