Question 1

How do I set up Prova for continuous integration?

Accepted Answer

Use headless browser commands like `prova -b -l phantom` or `prova -b -l chrome -e` with Xvfb. Ensure your CI environment has browsers installed and dependencies like Xvfb for headless execution.

Question 2

Prova vs Jest for browser testing: which should I choose?

Accepted Answer

Prova is better if you're already using Tape and Browserify and want a lightweight runner with live reload. Jest offers more features like snapshots and mocking but is heavier and may require more configuration for browser tests.

Question 3

How can I customize the HTML frame in Prova browser tests?

Accepted Answer

Use the `-f` or `--frame` parameter to specify a custom HTML file, e.g., `node test -b -f test.html`. This lets you modify the iframe content for specific UI testing needs.

Question 4

Does Prova work with ES6 modules without Babel?

Accepted Answer

No, Prova relies on Browserify, which primarily handles CommonJS. You need transforms like Babelify to use ES6 modules, as native support isn't built-in.

Question 5

How do I serve images or assets in Prova browser tests?

Accepted Answer

Prova provides an `/assets/in` endpoint to load files from the current directory, e.g., access `http://localhost:7559/assets/in/foobar.png` to include assets in tests.

Question 6

Can I use Prova to test React components?

Accepted Answer

Yes, but you'll need to set up Browserify transforms like Babelify for JSX and potentially additional tools to render components in the iframe environment.

Question 7

How to filter tests to run only specific cases in Prova?

Accepted Answer

Use the `-g` or `--grep` flag to match test patterns, e.g., `node test.js -g foobar` runs only tests containing 'foobar', useful for focused debugging.

prova

What is prova?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions