Question 1

How do I run browser-run headless in GitHub Actions?

Accepted Answer

Use xvfb-run before your npm test command, as shown in the README's YAML example. This sets up a virtual display for the browser to run without a screen in CI environments.

Question 2

browser-run vs Puppeteer: which is better for testing?

Accepted Answer

browser-run is simpler for executing code and capturing console logs, while Puppeteer offers full control over browser interactions. Choose browser-run for quick scripting, Puppeteer for complex page automation.

Question 3

Can I use Chrome instead of Electron with browser-run?

Accepted Answer

Yes, install Chrome and use the --browser chrome flag. The README notes that Chrome must be installed separately, unlike Electron which is bundled by default.

Question 4

How to mock an API back-end with browser-run?

Accepted Answer

Create a mock.js file exporting a function to handle requests, and use the --mock option. The README provides an example that echoes requests to /mock/echo for testing dynamic responses.

Question 5

How to integrate browser-run with browserify in a Node script?

Accepted Answer

Pipe the browserify bundle to browser-run using the programmatic API, as shown in the README where browserify('main.js').bundle() is piped to run(). This allows seamless testing of bundled JavaScript.

Question 6

Why does my browser-run script hang in CI?

Accepted Answer

Ensure your script calls window.close() to exit the browser; otherwise, it may hang indefinitely. The README warns to set timeouts in CI, like in the GitHub Actions example.

browser-run

What is browser-run?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions