Open Bug 1301174 Opened 3 years ago Updated 7 months ago

[META] Tracking bug for JS Debugger code coverage collection. (Disabled linux64-jsdcov build)

Categories

(Testing :: Code Coverage, task)

task
Not set

Tracking

(Not tracked)

People

(Reporter: sparky, Unassigned)

References

(Depends on 3 open bugs, Blocks 1 open bug)

Details

(Keywords: meta)

User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:48.0) Gecko/20100101 Firefox/48.0
Build ID: 20160823121617
This bug will be used to track all work that has to do with the JS Debugger code coverage and the linux64-jsdcov build.
Depends on: 1301197
Status: UNCONFIRMED → NEW
Ever confirmed: true
Depends on: 1301981
Depends on: 1301984
Depends on: 1301985
Depends on: 1336813
Are there other test suites that we are interested in instrumenting with per test js debugger code coverage?
I think web-platform-tests and maybe jsreftest, mochitest-clipboard, mochitest-webgl, mochitest-media, mochitest-gpu, mochitest-a11y.  That is most of the tests, I think we change enough stuff that we can re assess our coverage when we get done with that list.
Ok, I'll make some bugs for those. Would marionette be another one we'd like to instrument?
I think so, we should at least try it out.
I spent some time looking at marionette and it seems like it doesn't run any javascript tests even though it does have the capability to do so: https://dxr.mozilla.org/mozilla-central/source/testing/marionette/harness/marionette_harness/marionette_test/testcases.py#301 .

If we have javascript running inside the marionette python tests, then we'd have to find a way to hookup the coverage collector so that it can gather up that data.
I would imagine much .js code inside the browser would be covered by marionette tests.
Depends on: 1360667
(In reply to Joel Maher ( :jmaher) from comment #7)
> I would imagine much .js code inside the browser would be covered by marionette tests.

There is an easy way to test that, you can run the full test suite with JS_CODE_COVERAGE_OUTPUT_DIR environment variable, which will dump one *.lcov file per JSRuntime instance.

You might still have issues as the child process is not properly closed, and the JSRuntime destructor is not closed properly.
Depends on: 1378241
Depends on: 1380189
Depends on: 1391483
Depends on: 1418852
Depends on: 1418858
Depends on: 1451849
Depends on: 1454265
Depends on: 1496277
Depends on: 1496791
The linux64-jsdcov build has been disabled, and no longer runs in taskcluster, see bug 1496791. But the tooling still exists so that data can be obtained locally.
See Also: → 1496791
Summary: [META] Tracking bug for JS Debugger code coverage collection. (Linux64-jsdcov build) → [META] Tracking bug for JS Debugger code coverage collection. (Disabled linux64-jsdcov build)
No longer depends on: 1380189
Type: defect → task
You need to log in before you can comment on or make changes to this bug.