New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Backstop hangs on last scenario when using "readyEvent" #1208
Comments
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 can use |
Thanks @garris. So it sounds like I should forgo using Thank you |
I had some issues with readyEvent and started to look for workarounds. One solution was to hack a timeout into BackstopJS so that a failing test would block the suite which is a PITA with automated testing. |
Here i have the same issue that after last scenario will finish when using any readyEvent will not stop process. |
Ya, |
I fear we have to patch Backstop and hope that Garris approves our patch. But with 53 pull requests waiting I have no hope. Too bad Backstop is a one person project. |
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 script without any need to post a PR. This is no different from using vanilla puppeteer or selenium. Maybe you can prototype your scenario in puppeteer to arrive at a convention you prefer and then use that pattern in your onReady script. |
Hi @garris , |
Sorry @raDiesle -- it is hard for me to understand the issue here. |
I've just tried out readyEvent and I have the same issue ... |
I've just created a PR to fix the hanging; any idea who can release it? |
@klodoma Nice! Looking forward to testing this out. |
We can close this one: |
We've got a static Gatsby site running and we're using backstop for visual regression. For the most part it has been working pretty well for us.
One thing I wanted to improve is the hard coded delays that are in place via use of the
readyEvent
and so we implemented a console log accordingly. The problem that I have and cannot figure out is backstop appears to hang indefinitely when usingreadyEvent
. At first I thought it would hang in random spots but then realized it was also hanging on the very last scenario as defined in thebackstop.json
file.Things I've tried:
readyEvent
Has anyone else experienced this, looking for some insight.
Thanks
The text was updated successfully, but these errors were encountered: