Garris
One common issue here happens when a console event fires prior to backstop initializing in your app. This is probably what is happening. Potentially, instead of using the console you...
Its ordinary to wait for a class or other DOM state using the regular backstop config. And if you really need something custom you can add it to the onReady...
Sorry @raDiesle -- it is hard for me to understand the issue here.
That doesn't sound good. This happened when you bumped your version?
Does the smoke test run for you? https://github.com/garris/BackstopJS#smoke--feature-tests
@kaipahl This is great troubleshooting data -- thank you very much for these clear observations. Is this intermittent? Or consistent? Does it happen only with selectorExpansion -- or it doesn't...
@kaipahl and everyone else -- can you try adding this flag to your config? Please see the help doc here... https://github.com/garris/BackstopJS/blob/f360992b3d4ef4b7dac7928ae4f6fe1cbd5ec629/README.md#alternate-way-of-taking-a-full-page-screenshot Would very much like to see if this resolves...
@kaipahl thanks for this. What is your node version? And what is the hardware profile? The thing that is not adding up for me is that no one is complaining...
@Alexbirvik You will need to run backstop remote server in parallel with your normal BackstopJS app -- the following will be added to our docs soon... --- # Backstop-Remote Run...
Question here to clarify the problem since I am not a storybook user. Let's say you have a storybook with a custom menu dropdown component. In storybook -- how do...