BackstopJS
BackstopJS copied to clipboard
Catch CSS curve balls.
**Context:** Quite often some of the [advanced scenario settings](https://github.com/garris/BackstopJS#advanced-scenarios) apply to every scenario and are "global". For example the `hideSelectors` are the same for each scenario, e.g. for Cookie Banners,...
When I run my configuration with the Chromy driver and use the `hideSelectors` global option, it doesn't work. It only works when I add `hideSelectors` to individual scenario configurations. Steps...
Or does it need to be per scenario? For example, I'd like to remove a div using the `removeSelectors` option but would like to add that reference once instead of...
So it seems that per scenario you can add ``` "hideSelectors": ["div[data-autoid='station_clock']", "button[data-autoid='status_button']"] ``` but this means i have to duplicate this line on every test, is there a way...
Hello, Looks like v6.1.1 update "puppeteer": "^14.2.1", to "puppeteer": "^15.4.0", when postInteractionWait on backstop.json file is greater than 0 (ie 3000) backstop will throw an error below Puppeteer encountered an...
Hi Garris, I have this test:  it's failing from a 1px difference. When I run the image on my local docker, it passes, but I run it on the...
I'm using hideSelectors on ".slick" slideshows as timing may otherwise cause differences. For "test" everything works fine and as expected, but for "reference" the hideSelectors don't seem to work: ...
How can i do this? 
The currently available docker images are only available to _amd64_ architecture: https://hub.docker.com/r/backstopjs/backstopjs/tags?page=1&ordering=last_updated Soon Apple will change to architecture of all Macbooks to **arm64**. The current Macbook Pro 13 inch is...
Currently debugging invalid ready code is pretty tricky. For example, it's possible for `waitForSelector` to timeout, but there's no easy way to determine what test case actually caused the error....