Puppeteer node based tests should use toolchains rather than installing from npm for each test run
Categories
(Remote Protocol :: Agent, task, P3)
Tracking
(firefox149 fixed)
| Tracking | Status | |
|---|---|---|
| firefox149 | --- | fixed |
People
(Reporter: standard8, Assigned: jdescottes)
References
(Depends on 1 open bug, Blocks 1 open bug)
Details
(Whiteboard: [webdriver:m19])
Attachments
(1 file)
Currently the Puppeteer tests all install directly from npm for every test run. We should move those across to toolchains, to avoid having to rely on external servers etc -e.g. this failure due to an issue with npmjs.
The toolchains should be built once when package*.json is changed, and then used for each test until the next change.
A previous example of this is bug 1920970.
| Reporter | ||
Updated•1 year ago
|
| Reporter | ||
Comment 1•1 year ago
|
||
Note: bug 1957705 now has a patch on which is probably simpler to reference/understand than the other bug I mentioned.
Updated•1 year ago
|
| Assignee | ||
Updated•9 months ago
|
| Assignee | ||
Comment 2•9 months ago
|
||
Mark, is this something you could take or should our team do it?
| Reporter | ||
Comment 3•9 months ago
|
||
(In reply to Julian Descottes [:jdescottes] from comment #2)
Mark, is this something you could take or should our team do it?
I would prefer your team to take a look, iirc, there was something I was unsure about at the time, and I thought your team might be able to handle it better, but I can't remember what that was now. In any case, I don't really have time for this at the moment.
| Assignee | ||
Comment 4•9 months ago
|
||
Thanks let's keep it in our next milestone then!
| Assignee | ||
Updated•6 months ago
|
| Assignee | ||
Updated•2 months ago
|
| Assignee | ||
Comment 5•2 months ago
|
||
Description
•