Closed
Bug 1185459
Opened 9 years ago
Closed 7 years ago
[meta] Test coverage for the new extension API
Categories
(WebExtensions :: Untriaged, defect, P2)
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.
Reporter | ||
Updated•9 years ago
|
Blocks: webextensions-chrome-gaps
Depends on: 1175770
Reporter | ||
Comment 1•9 years ago
|
||
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
Reporter | ||
Comment 2•9 years ago
|
||
Sorry for the bugspam, I removed the wrong bug.
Blocks: webextensions-chrome-gaps
No longer depends on: 1175770
Reporter | ||
Updated•9 years ago
|
Summary: Test coverage for the new extension API → [meta] Test coverage for the new extension API
Priority: -- → P1
Component: Extension Compatibility → WebExtensions
Product: Firefox → Toolkit
Version: unspecified → 34 Branch
Depends on: 1197507
Updated•9 years ago
|
Flags: blocking-webextensions+
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?
Updated•9 years ago
|
Whiteboard: triaged
Updated•9 years ago
|
No longer blocks: webextensions-chrome-gaps
Comment 4•8 years ago
|
||
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
Updated•8 years ago
|
Flags: blocking-webextensions+
Comment 5•7 years ago
|
||
closing tracking bug that is tracking a single open p5 bug.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Updated•6 years ago
|
Product: Toolkit → WebExtensions
You need to log in
before you can comment on or make changes to this bug.
Description
•