[SPARK-46597][SQL][TESTS] Optimize the run tests command in the doc of XXIntegrationSuite in docker-integration-tests module
#44597
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
LuciferYang
changed the title
docker-integration-tests moduledocker-integration-tests module
MaxGekk
approved these changes
Jan 4, 2024
Member
|
+1, LGTM. Merging to master. |
Contributor
Author
|
Thanks @MaxGekk |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
The class descriptions of the test cases in the
docker-integration-testsmodule provide suggested commands for executing the test cases, but these commands will search for corresponding test cases in all modules. This pr adds the module namedocker-integration-teststo these commands, so that the test commands only search for corresponding test cases in thedocker-integration-testsmodule.Why are the changes needed?
Refine docs.
Does this PR introduce any user-facing change?
No
How was this patch tested?
I have manually checked the new command locally.
Was this patch authored or co-authored using generative AI tooling?
No