Add Test Coverage Visualization validation

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

• Close this issue

Proposal

There are cases when Test Coverage Visualization might not parse the reports properly because of these common scenarios.

If the test coverage visualization is not displayed in the diff view, you can check the coverage report itself and verify that:

• The file you are viewing in the diff view is mentioned in the coverage report.
• The source and filename nodes in the report follows the expected structure to match the files in your repository.
• The pipeline has completed. If the pipeline is blocked on a manual job, the pipeline is not considered complete.
• The coverage report file does not exceed the limits.

It would be helpful if we have some form of validation that would raise verbose warning/error messages to inform the user where the issue might be.

In one case scenario, the report had entries like these which we did not parse properly and caused some silent failure.

<line number="661" hits="undefined" branch="false"/>