-
Notifications
You must be signed in to change notification settings - Fork 273
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update the name to test-report and add README for report workflow #3864
Changes from 1 commit
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,24 @@ | ||
#### Generate test-report manifest for each test. | ||
The input requires a mandatory `test-manifest-path`, `--artifact-paths`, `--base-path`, `--test-type` and `--test-run-id`, optional `--output-path` and `--component` to automatically generate the test-report manifest after testing. | ||
|
||
*Usage* | ||
``` | ||
./report.sh <test-manifest-path> --artifact-paths opensearch=<...> opensearch-dashboards=<...> --test-run-id <...> --test-type integ-test --base-path <...> | ||
``` | ||
e.g. | ||
``` | ||
./report.sh manifests/2.9.0/opensearch-2.9.0-test.yml -p opensearch=https://ci.opensearch.org/ci/dbc/distribution-build-opensearch/2.9.0/8172/linux/x64/tar --test-run-id 5328 --test-type integ-test --base-path https://ci.opensearch.org/ci/dbc/integ-test/2.9.0/8172/linux/x64/tar | ||
``` | ||
The following options are available. | ||
|
||
| name | description | | ||
|----------------------|--------------------------------------------------------------------------------| | ||
| test-manifest-path | Specify a test manifest path. | | ||
| -p, --artifact-paths | Artifact paths of distributions used for testing. | | ||
| --base-path | Base paths of testing logs. | | ||
| --test-type | Type of tests report generates on. | | ||
| --output-path | Specify the path location for the test-report manifest. | | ||
| --test-run-id | Specify the unique execution id for the test. | | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This test-run-id should be equal to the the test runs build number right? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yes, this id will be used to retrieve the component yml. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Can you specify that it should match the test-run-id from already run tests? Seems like you can enter anything which is not right There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Thanks. Just updated. |
||
| --component | Specify a specific component or components instead of the entire distribution. | | ||
| --verbose | Show more verbose output. | | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: Add
<required>
and<optional>
in the below table so that all information related to params is in one placeThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You can remove this from here and instead add more description what this workflow actually does.