-
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
Conversation
Signed-off-by: Zelin Hao <[email protected]>
src/report_workflow/README.md
Outdated
@@ -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. |
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 place
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.
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.
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. | |
As the name specifies, the test report workflow helps to automatically generate a consolidated report of the tests run at distribution level along with commands to reproduce the error and associated failures. | |
These tests include integration tests, BWC tests. |
src/report_workflow/README.md
Outdated
| --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 comment
The 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 comment
The 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 comment
The 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 comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks. Just updated.
Codecov Report
@@ Coverage Diff @@
## main #3864 +/- ##
==========================================
+ Coverage 91.62% 91.78% +0.15%
==========================================
Files 186 186
Lines 5633 5633
==========================================
+ Hits 5161 5170 +9
+ Misses 472 463 -9
|
Signed-off-by: Zelin Hao <[email protected]>
Signed-off-by: Zelin Hao <[email protected]>
Description
Update the name to test-report and add README for report workflow
Issues Resolved
Part of #1274
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.