Replacement needed for PhantomJS
Bug #1845693 reported by
Jeff Davis
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
Medium
|
Unassigned | ||
3.3 |
Won't Fix
|
Medium
|
Unassigned |
Bug Description
We've been using PhantomJS to run unit tests for the web client. Unfortunately that project has been abandoned and is no longer being developed:
https:/
The final release is now several years old and increasingly outdated, so we should be looking for alternatives. Headless Chromium has been suggested as a possibility, although we should avoid bringing in a bunch of dependencies that are only needed to run tests.
There has been periodic discussion of PhantomJS alternatives in IRC, most recently here:
http://
tags: | added: webstaffclient |
tags: | added: pullrequest |
Changed in evergreen: | |
status: | New → Confirmed |
assignee: | nobody → Bill Erickson (berick) |
Changed in evergreen: | |
assignee: | nobody → Galen Charlton (gmc) |
importance: | Undecided → Medium |
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
I hesitate to mention this, since it's far afield of our current testing practices, but it may be worth noting that it's possible to run unit tests with Chrome proper on a Linux desktop (VM or otherwise). It requires Evergreen/OpenSRF checkouts, npm, Perl LibXSLT (for IDL parsing), and a few manual steps to make the test environment happy.
I was able to run unit tests for both Ang and AngJS builds. (Ang image attached to prove it wasn't a hallucination).
Mostly I was just curious if it would still work and was pleased to find it did.