Run mocha tests with TaskCluster
Categories
(DevTools :: Console, defect, P2)
Tracking
(firefox68 fixed)
Tracking | Status | |
---|---|---|
firefox68 | --- | fixed |
People
(Reporter: linclark, Assigned: nchevobbe)
References
Details
Attachments
(3 files)
Reporter | ||
Comment 1•9 years ago
|
||
Comment 2•9 years ago
|
||
Reporter | ||
Updated•9 years ago
|
Updated•9 years ago
|
Updated•8 years ago
|
Updated•8 years ago
|
Updated•8 years ago
|
Assignee | ||
Updated•8 years ago
|
Comment hidden (mozreview-request) |
Comment hidden (mozreview-request) |
Comment hidden (mozreview-request) |
Updated•8 years ago
|
Updated•8 years ago
|
Updated•8 years ago
|
Updated•8 years ago
|
Updated•8 years ago
|
Updated•8 years ago
|
Updated•8 years ago
|
Updated•8 years ago
|
Updated•8 years ago
|
Updated•7 years ago
|
Updated•7 years ago
|
Assignee | ||
Updated•7 years ago
|
Assignee | ||
Updated•6 years ago
|
Assignee | ||
Comment 7•6 years ago
|
||
This adds missing preferences to mocha-test-setup.js.
Assignee | ||
Comment 8•6 years ago
|
||
To make the test pass, we need to define URLSearchParams
if it doesn't exist.
Depends on D25044
Comment 9•6 years ago
|
||
-
What about trying to run each test suite individually?
It looks like we could do a better at running only the webconsole tests when only the webconsole folder is changed, only framework when framework is changed and so on. -
Is there any plan to integrate these node tests into
*.ini
files and./mach test
?
Supporting ini file would help being tier 1/2 and be "sheriffable".
While supporting ./mach test would help running them when you are not used to DevTools specifics.
Comment 10•6 years ago
|
||
It looks like we could do a better at running only the webconsole tests when only the webconsole folder is changed, only framework when framework is changed and so on.
It is an option. Felt like an overkill for "framework" and "aboutdebugging" right now, because they both have just one test. My idea was to wait until we had more tests written, but if you feel strongly about this we can change it here.
Is there any plan to integrate these node tests into *.ini files and ./mach test?
Supporting ini file would help being tier 1/2 and be "sheriffable".
While supporting ./mach test would help running them when you are not used to DevTools specifics.
Would be nice, I don't know if this is being worked on. Note that this is why we added READMEs in the jest test folders for framework & aboutdebugging. I think the list of things to improve for those tests is long: error reporting, mach support, sheriffing.
Comment 11•6 years ago
|
||
(In reply to Julian Descottes [:jdescottes] from comment #10)
It looks like we could do a better at running only the webconsole tests when only the webconsole folder is changed, only framework when framework is changed and so on.
It is an option. Felt like an overkill for "framework" and "aboutdebugging" right now, because they both have just one test. My idea was to wait until we had more tests written, but if you feel strongly about this we can change it here.
TBH I'm fine with the current in-flight patch. I mostly wanted to raise these two points so that they are being addressed at some point. Followups and proper staffing on this would be great!
Comment 12•6 years ago
|
||
Here is a meta for improving the node tooling bug 1535113. I'll add two bugs for *.ini and mach integration
Comment 13•6 years ago
|
||
Comment 14•6 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/4fe8d3976d58
https://hg.mozilla.org/mozilla-central/rev/4338bf79beb2
Description
•