Question 1

How do I set up Hardy to test with Chrome?

Accepted Answer

You need to install ChromeDriver separately and ensure it's in your path. Then, run Hardy with the --browser=chrome flag to specify Chrome, as detailed in the README's browser setup section.

Question 2

Does Hardy support headless browsers for faster testing?

Accepted Answer

Yes, Hardy supports PhantomJS, a headless browser, by running tests with --browser=phantomjs. However, the local PhantomJS install might require manual path configuration, as noted in the README.

Question 3

What's the difference between Hardy and BackstopJS for visual regression testing?

Accepted Answer

Hardy uses Selenium and Cucumber for a more integrated, multi-browser approach with readable syntax, while BackstopJS focuses on visual diffs with a simpler setup but may lack the same cross-browser automation depth.

Question 4

Can I use Hardy with Jenkins or other CI tools besides Travis?

Accepted Answer

Yes, Hardy is CI-ready and can be adapted for any CI system supporting Node.js and Selenium. The README provides a Travis guide, but the principles apply to others like Jenkins with similar configurations.

Question 5

How does Hardy handle dynamic CSS or animations?

Accepted Answer

Hardy uses Selenium to capture the rendered page state, so it should handle dynamic CSS and animations as they appear in browsers, though test steps may need to manage timing or interactions explicitly.

Question 6

Is GraphicsMagick required for Hardy to work?

Accepted Answer

No, GraphicsMagick is optional but recommended for significantly faster image comparisons. Without it, Hardy still functions but may be slower in visual regression tests.

Hardy

What is Hardy?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions