Run the stylelint-plugin-mozilla tests on automation
Categories
(Developer Infrastructure :: Lint and Formatting, task)
Tracking
(firefox139 fixed)
Tracking | Status | |
---|---|---|
firefox139 | --- | fixed |
People
(Reporter: hjones, Assigned: hjones)
References
Details
Attachments
(1 file)
Once we've added some tests for our custom stylelint rules in 1921095 it would be ideal to get them running on automation. I expect we'll need a custom reporter along the lines of what was implemented for the eslint tests, though the stylelint tests will be backed by Node test runner instead of mocha. Some info on implementing custom reporters for Node tests can be found here.
I also expect a lot of the task configuration for eslint will be relevant to stylelint. :standard8 do you have any thoughts/pointers on how best to go about this? It looks like you did the initial work for running eslint tests in bug 1379119 and has evolved a bit since.
Comment 1•6 months ago
|
||
(In reply to Hanna Jones [:hjones] from comment #0)
Once we've added some tests for our custom stylelint rules in 1921095 it would be ideal to get them running on automation. I expect we'll need a custom reporter along the lines of what was implemented for the eslint tests, though the stylelint tests will be backed by Node test runner instead of mocha.
Yes, the important parts are the TEST-UNEXPECTED-FAIL
, TEST-PASS
etc, they're the lines that treeherder & code review log parses detect.
I also expect a lot of the task configuration for eslint will be relevant to stylelint. :standard8 do you have any thoughts/pointers on how best to go about this? It looks like you did the initial work for running eslint tests in bug 1379119 and has evolved a bit since.
Thankfully it got a lot simpler recently.
Comment 2•6 months ago
|
||
(In reply to Mark Banner (:standard8) from comment #1)
(In reply to Hanna Jones [:hjones] from comment #0)
I also expect a lot of the task configuration for eslint will be relevant to stylelint. :standard8 do you have any thoughts/pointers on how best to go about this? It looks like you did the initial work for running eslint tests in bug 1379119 and has evolved a bit since.
Thankfully it got a lot simpler recently.
[pressed return too early]
I think you'll need to duplicate this toolchain, and the associated script. Then you'll also need to duplicate the task configuration as you linked to.
Assignee | ||
Comment 3•5 months ago
|
||
Updated•5 months ago
|
Comment 5•4 months ago
|
||
bugherder |
Description
•