bazelbuild / bazelbuild/rules_closure

Replace phantomjs for closure_js_test

Open
#469 6 comments 0 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
159
Forks
111
PR merge metrics
No merged PRs in 30d

Description

I find that phantomjs renders closure_js_test rather limited in terms of web apis, it's hard to use, and the error messages aren't very good.

Is there any appetite for replacing phantomjs with some sort of headless chrome or other browser? Has anyone started on such work?

For those interested in seeing phantomjs go away, what alternative(s) would you like to see?

Contributor guide

Open the contributing guide

Research direction

Start by examining the closure_js_test entry point and how it invokes PhantomJS. Research suitable headless-browser alternatives and their web API and error-reporting support; done would require an agreed replacement and a migrated test path, but the issue does not specify either.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
build-system, testing-qa
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.