Currently the phantomjs process is functioning, but needs some work to get it into a stable place from a testing infra perspective.

Identified issues:
phantomjs should be its own container
phantomjs should use an official release, not the fork
phantomjs/run-tests.sh needs to be able to support parallel testing - this may be a haproxy front end to a pool of phantomjs workers with sticky cookies, or it may be some other solution. Our current serial run of tests will not be sustainable once we hit a certain number of tests.

Comments

Mixologic created an issue. See original summary.

Mixologic’s picture

Mixologic
He/Him/His
Primary language English
Location Portland, OR
commented
Component: Containers » Environments
Mixologic’s picture

Mixologic
He/Him/His
Primary language English
Location Portland, OR
commented
Issue summary: View changes

Using not the fork now.

elachlan’s picture

elachlan commented
Project: DrupalCI: Test Runner » DrupalCI: Environments
Component: Environments » Code

Moved to DrupalCI Environments.

Mixologic’s picture

Mixologic
He/Him/His
Primary language English
Location Portland, OR
commented
Component: Code » PHP Containers

https://groups.google.com/forum/m/#!topic/phantomjs/AefOuwkgBh0 phantomjs has a 2.5.0 beta. something to be aware of.

Mixologic’s picture

Mixologic
He/Him/His
Primary language English
Location Portland, OR
commented
Status: Active » Closed (won't fix)

phantomjs is now abandonware. We're not going to be optimizing for it, and will keep it running. javascript testing should follow on either nightwatch or on webdriver/mink.

elachlan’s picture

elachlan commented

Thanks Mixologic.

For people wondering, here is the post of confirming the maintainers decision.
https://github.com/ariya/phantomjs/issues/15105

It was because headless chrome came out and is much better:
https://github.com/GoogleChrome/puppeteer