Open Bug 1588449 Opened 5 years ago Updated 4 months ago

[Automated review] Node tests not being taken into account for code coverage

Categories

(Testing :: Code Coverage, defect, P3)

defect

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

Summary: [Automated review] UPDATE → [Automated review] Node tests not being taken into account for code coverage

Marco, do you know if it would be hard to do ?

Flags: needinfo?(mcastelluccio)

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.

Component: Source Code Analysis → Code Coverage
Flags: needinfo?(mcastelluccio)
Product: Firefox Build System → Testing

The priority flag is not set for this bug.
:ekyle, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(klahnakoski)

I will assume supporting coverage on Node tests is not a priority

Flags: needinfo?(klahnakoski)
Priority: -- → P3
Severity: normal → S3

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.

Flags: needinfo?(nidhioberoi999) → needinfo?(mcastelluccio)
Flags: needinfo?(mcastelluccio)
You need to log in before you can comment on or make changes to this bug.