[Automated review] Node tests not being taken into account for code coverage
Categories
(Testing :: Code Coverage, defect, P3)
Tracking
(Not tracked)
People
(Reporter: ladybenko, Unassigned)
References
(Blocks 1 open bug)
Details
Phabricator URL: https://phabricator.services.mozilla.com/D48870#1482416
Hi, I got this automatic code coverage review in Phabricator about some files not being tested, but they are with node/Jest tests (see https://searchfox.org/mozilla-central/search?q=&path=devtools%2Fclient%2Fapplication%2Ftest%2Fcomponents%2F**%2F*.test.js )
Could Node tests be taken into account for code coverage? Thanks
Reporter | ||
Updated•5 years ago
|
Comment 1•5 years ago
|
||
Marco, do you know if it would be hard to do ?
Comment 2•5 years ago
|
||
I don't have much info on the infra of these kind of tests. Are they yet another kind of test? Are they using Node with v8 and so no SpiderMonkey?
If they are run via SpiderMonkey, adding support should be relatively easy.
If they are not, it would be a bit more involved.
Comment 3•5 years ago
|
||
The priority flag is not set for this bug.
:ekyle, could you have a look please?
For more information, please visit auto_nag documentation.
Comment 4•5 years ago
|
||
I will assume supporting coverage on Node tests is not a priority
Updated•2 years ago
|
Comment hidden (spam) |
Comment 6•4 months ago
|
||
Redirect a needinfo that is pending on an inactive user to the triage owner.
:marco, since the bug has recent activity, could you have a look please?
For more information, please visit BugBot documentation.
Updated•4 months ago
|
Description
•