Keep last run Test Results on merge requests

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

Proposal

Keep the last successfully run test results on an MR even when the last run pipeline does not contain the test job.

The problem to solve

Currently, for the Browser Performance Report widget (and other Coverage test results) to display correctly on Merge requests, the test job containing the artifact must be present in the last run pipeline.

A use case of this are customers that run merge trains but do not want to re-test the browser performance test on the merge train pipeline to increase performance. In such scenarios the browser performance widget is removed once the merge train pipeline is run.

What does success look like

  • When customers are able to keep the Browser Performance Result on the merge request if it ran successfully once or
  • When customers can choose from a list of successfully run browser tests against the MR
Edited by 🤖 GitLab Bot 🤖