Open
Bug 1602377
Opened 6 years ago
Updated 3 years ago
mochitest run should fail if a test file is not part of any manifest file (browser.ini, mochitest.ini etc.)
Categories
(Testing :: General, enhancement, P3)
Tracking
(Not tracked)
NEW
People
(Reporter: aryx, Unassigned)
Details
(Whiteboard: dev-prod-2020)
https://hg.mozilla.org/releases/mozilla-beta/rev/263976454789 added a browser-chrome test but didn't add it to any manifest. As a result, it didn't get executed.
There should be a failure message under this condition but the mochitest run the test from the manifest anyway to catch issues with product changes or modified test or tests added to the manifest.
Updated•6 years ago
|
Whiteboard: dev-prod-2020
Comment 1•6 years ago
|
||
This should probably be implemented as a linter.
It's not entirely clear how to determine whether a file is a test or not. We'd need to invent heuristics (e.g, any file that starts with browser_ or test_ in a test(s) directory). There could be false positives we'll need to rename.
Priority: -- → P3
Updated•6 years ago
|
Component: Mochitest → General
Updated•3 years ago
|
Severity: normal normal → S3 S3
You need to log in
before you can comment on or make changes to this bug.
Description
•