Utilise testing gap detection report
AC:
Define a process of how to utilize information from "targeted testing missing" label on merge request:
- How often MRs with the label should be reviewed
- What the actions should be? Talk with developer/QE on adding new tests where appropriate && rerunning testing when the test is added?
- How to correctly skip the label or missing testing in case of e.g. docs or
.gitlab-ci.yml
changes, so we minimize false positives when we start blocking merges on the label - Document the above in the test maintainer documentation after everything is agreed on between CKI and QE (talk to Evan/Linquing)
Also we should review each onboarded test ran with coverage and adjust the trigger files of targeted testing appropriately where it makes sense, as right now the trigger files are assigned manually based on guesses rather than any actual data and thus we will likely end up assigning the label incorrectly.
Edited by Veronika Kabátová