Garris
Oy. So, if you just run point to backstop.org, is it still inconsistent? You can just use the default init config to test this.
I would like to rule out that this is not a timing problem or some weird content problem. Can you try to test a simple webpage on your domain? Something...
1) I think it's relevant that you haven't gotten `president` to fail. But also more importantly... 2) It looks like you are mounting the docker container and manually running backstop...
Ok. Just noticed this in the log... `ERROR { requireSameDimensions: false, size: isDifferent, content: 16.12%, threshold: 0.1% }: HES backstop_default_HES_0_document_1_desktop.png` `size: isDifferent` suggests that we _don't_ have GPU issue. Instead--...
This isn't natively supported-- maybe just edit your viewports properties in the config? Comment out the ones you don't want while debugging? You can optionally add a viewports property to...
It could also be related to this https://github.com/garris/BackstopJS#using-docker-for-testing-across-different-environments -- you can try running the docker version to see if the same thing happens.
This is built-in -- You can just use the `--docker` argument to your test command. Backstopjs will make a call to docker and render in the container. [Details here](https://github.com/garris/BackstopJS#using-docker-for-testing-across-different-environments) e.g....
Oh, I think I understand. If you want to build a docker image into your local docker repo from the current BackstopJS source... _Locally from backstop root_ ``` docker build...
This is a little confusing to follow -- but please check the docs for the `referenceUrl` property. Maybe this helps? Otherwise you may need to do a dynamic config.
Yup, there is no cleanup per se. but it would be really easy to do this on the command line or as you mentioned, using BackstopJS as a node module...