garris/BackstopJS

Test fails silently and Report does not run

Opened this issue · 3 comments

seanfoo commented

I have a test setup running via node and a cron job on centos. We run 224 tests and 28 scenarios. Every so often we make a change and we can not get all 224 tests to run. Any failures are silent and then the html report doesn't run. So we know there are changes to review, but we have no means to review them.

I guess I'm wondering is there any way to have a more verbose error messaging, so I can see what's happening? It puts a damper on our automated testing having this happen.

We run
backstop test

from the command-line to initiate the tests.

this is the err file from the backstop run
css_test.txt

our backstop.json
backstop_json.txt

garris commented

Have you tried these first two params? https://github.com/garris/BackstopJS#debugging

seanfoo commented

Thank you. I re-ran it and saw a memory error.

I'm guessing what has been happening is that we moved to AWS recently and our machine has less memory, so the parallelization async settings were a bit too aggressive and we were running out of memory.

Thank you for the help and for the program. It's very helpful.

garris commented

Ah, Got it! Glad you figured it out -- cheers! ☮️