Add test history to test report MR widget
What does this MR do?
For #241759 (closed), !45187 (merged) will expose a recent_failures count per test case in the test report data.
This MR shows the recent_failures count in three ways/places within the test report MR widget:
-
Report-level: As a total count of tests with more than one recent failure in the report summary,
10 out of 100 failed tests failed more than once in the last 14 days -
Suite-level, once the widget is expanded: As a count of tests with more than one recent failure in each suite's summary,
3 out of 9 failed tests failed more than once in the last 14 days, forrspec,jest, etc. -
Case-level, once the widget is expanded: As a badge of the number of recent failures on each test case
Failed 8 times in the last 14 days
This MR is behind the feature flag :test_failure_history, and therefore should not have a changelog entry or documentation yet.
Testing before the backend is merged
To generate random numbers for the recent_failures counts for each test case, grab this patch Mock-recent_failures-with-random-number.patch and:
git apply Mock-recent_failures-with-random-number.patch
Screenshots
| Collapsed (default) | Expanded |
|---|---|
 |
 |
Does this MR meet the acceptance criteria?
Conformity
- [-] Changelog entry
- [-] Documentation (if required)
-
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers -
Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
- [-] Label as security and @ mention
@gitlab-com/gl-security/appsec - [-] The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
- [-] Security reports checked/validated by a reviewer from the AppSec team
Edited by Miranda Fluharty