Closed Bug 1597390 Opened 6 years ago Closed 5 days ago

Searchfox integration exposes code coverage links for pages without coverage and a confusing 400 error is displayed

Categories

(Testing :: Code Coverage, defect, P3)

Version 3
defect

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: asuth, Unassigned)

References

Details

Right now the following test files show "Code Coverage" links in searchfox:

If I click on them, I get 400 errors "Failed to load coverage: 400 - BAD REQUEST" which is confusing.

It appears that dom/test/ isn't indexed at all per https://coverage.moz.tools/#revision=latest&path=dom&view=directory ?

It's possible the files in question are disabled, and while it would be best if the coverage tool knew that, just having an error better than 400 would be helpful I think. (Or maybe this is a legit error that should be fixed, in which case, that would also be good! :)

We intentionally don't have coverage for test files. While that might change in the future, I think for now the best solution would be:

  1. Us showing a nicer error message;
  2. If possible, Searchfox not adding a "Code Coverage" link on test files.

The priority flag is not set for this bug.
:ekyle, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(klahnakoski)
Flags: needinfo?(klahnakoski)
Priority: -- → P4
Severity: normal → S3
No longer blocks: 1823747
See Also: → 1823747
Duplicate of this bug: 1823747

We intentionally don't have coverage for test files.

This problem is general for all files that don't end up being compiled.

Searchfox doesn't link to coverage.moz.tools at all since https://github.com/mozsearch/mozsearch/commit/962360f92c4fc559ed1dffc174e317b63097faea.

Status: NEW → RESOLVED
Closed: 5 days ago
Resolution: --- → FIXED
Resolution: FIXED → WORKSFORME
You need to log in before you can comment on or make changes to this bug.