Repository navigation
fix(test): load unit test metrics into bq - #10474
Conversation
|
Images are ready for the commit at 47fe6d1. To use with deploy scripts, first |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #10474 +/- ##
==========================================
- Coverage 47.89% 47.89% -0.01%
==========================================
Files 2280 2280
Lines 163224 163224
==========================================
- Hits 78179 78169 -10
- Misses 78843 78851 +8
- Partials 6202 6204 +2
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
gavin-stackrox
left a comment
There was a problem hiding this comment.
I think this PR should also handle create_job_record() and update_job_record(). Current reporting depends on it and the job record has more detail related to the overall run. Support for GHA might be missing though.
porridge
left a comment
There was a problem hiding this comment.
Just a few nitpicks. No idea about the thing mentioned by Gavin...
|
@gavin-stackrox How about adding support for job records in a separated PR. Currently pre/post actions are not supported in composite action so we need to rewrite junit2jira action to have it or create a dedicated action for job record |
Signed-off-by: Tomasz Janiszewski <tomek@redhat.com>
Signed-off-by: Tomasz Janiszewski <tomek@redhat.com>
Signed-off-by: Tomasz Janiszewski <tomek@redhat.com>
Signed-off-by: Tomasz Janiszewski <tomek@redhat.com>
Signed-off-by: Tomasz Janiszewski <tomek@redhat.com>
Co-authored-by: Marcin Owsiany <porridge@redhat.com>
Signed-off-by: Tomasz Janiszewski <tomek@redhat.com>
dfd4b37 to
47fe6d1
Compare
Signed-off-by: Tomasz Janiszewski <tomek@redhat.com>
Description
This PR enhance junit2jira action with uploading test metrics into bigquery.
Checklist
If any of these don't apply, please comment below.
Testing Performed
Here I tell how I validated my change
Reminder for reviewers
In addition to reviewing code here, reviewers must also review testing and request further testing in case the
performed one does not seem sufficient. As a reviewer, you must not approve the change until you understand the
performed testing and you are satisfied with it.