Closed Bug 1185459 Opened 9 years ago Closed 6 years ago

[meta] Test coverage for the new extension API

Categories

(WebExtensions :: Untriaged, defect, P2)

34 Branch
defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: gkrizsanits, Unassigned)

References

(Depends on 1 open bug)

Details

(Keywords: meta, Whiteboard: triaged)

We need comfortable way to write add-on related tests. And need to get a decent test coverage for the new API.
Since Bug 1175770 has a patch with some initial tests, I think the first part is covered and this bug should focus on getting the test coverage. I'm transforming this bug into a meta bug for tests.
No longer blocks: webextensions-chrome-gaps
Summary: Need a way to test the new extension API → Test coverage for the new extension API
Sorry for the bugspam, I removed the wrong bug.
No longer depends on: 1175770
Depends on: 1190318
Depends on: 1190320
Depends on: 1190321
Depends on: 1190331
Depends on: 1190330
Depends on: 1190329
Depends on: 1190328
Depends on: 1190326
Depends on: 1190325
Depends on: 1190324
Depends on: 1190323
Depends on: 1190322
Summary: Test coverage for the new extension API → [meta] Test coverage for the new extension API
Component: Extension Compatibility → WebExtensions
Product: Firefox → Toolkit
Version: unspecified → 34 Branch
Blocks: webext
Flags: blocking-webextensions+
Depends on: 1220811
I figure that it should be possible for add-ons developers to write unit tests in a "comfortable way" too, like was possible with jpm or cfx, which is bug 1223616.  Maybe this bug should depend on it?
Depends on: 1236118
Depends on: 1236121
Depends on: 1236122
Whiteboard: triaged
No longer blocks: webextensions-chrome-gaps
Depends on: 1259617
Depends on: 1263167
Depends on: 1263900
I'm trying to keep make sure P1s are assigned to people, so dropping this down to P2 since its a tracker.
Priority: P1 → P2
Flags: blocking-webextensions+
Keywords: meta
closing tracking bug that is tracking a single open p5 bug.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Product: Toolkit → WebExtensions
You need to log in before you can comment on or make changes to this bug.