Open
Bug 1189360
(js-code-coverage)
Opened 11 years ago
Updated 2 months ago
[meta] JavaScript Code Coverage
Categories
(Core :: JavaScript Engine, task, P3)
Core
JavaScript Engine
Tracking
()
NEW
| Tracking | Status | |
|---|---|---|
| firefox42 | --- | affected |
People
(Reporter: nbp, Unassigned)
References
(Depends on 14 open bugs, Blocks 2 open bugs)
Details
(Keywords: meta, Whiteboard: sm-meta-retriage-2025)
This is a meta bug to add Code Coverage for JavaScript code executed in SpiderMonkey. We have multiple reasons to do that:
The most important is to support release management team, by producing Code Coverage information over executed JavaScript code, and producing gcov-like data files. This would help improve the quality of Firefox, and help evaluate the quality of our tests to accept/refuse new features.
The second reason is to expose this information to the dev-tools, such that JavaScript developers do not have to instrument their code to have code coverage results within the dev-tools.
The third, if the overhead is neglectable, is to make use of the same information to improve IonMonkey register allocation and removal of unused basic blocks ahead of time.
| Reporter | ||
Updated•10 years ago
|
Alias: js-code-coverage
Summary: (js-code-coverage) [meta] Add Code Coverage for JavaScript code. → [meta] Add Code Coverage for JavaScript code.
Updated•10 years ago
|
Blocks: code-coverage
Updated•7 years ago
|
Type: defect → task
Updated•3 years ago
|
Severity: normal → S3
Updated•2 years ago
|
Blocks: sm-runtime
Severity: S3 → N/A
Updated•2 years ago
|
Priority: -- → P3
Updated•2 years ago
|
Summary: [meta] Add Code Coverage for JavaScript code. → [meta] JavaScript Code Coverage
Updated•9 months ago
|
Whiteboard: sm-meta-retriage-2025
You need to log in
before you can comment on or make changes to this bug.
Description
•