Open loopy3025 opened 2 years ago
Ok. So the problem is probably not the bit about the files not being in the right place -- the problem looks like backstop is not getting a response from your dev box (thus, screen capture fails and weird stuff happens.)
@garris I have this problem aswell in an Alpine Docker container. Could you elaborate on what type of response the dev box should be giving and how this works exactly?
I have the same problem when running my test in a Docker container.
This error
TimeoutError: Navigation timeout of 60000 ms exceeded
Indicates that BackstopJS made a request for a scenario URL and never received a response. So, It's likely that your docker instance doesn't have access to the URL.
All the business with 0_document
-type of errors is just BackstopJS not doing a good job of handling the root cause timeout error.
Hope this helps!
I am getting the error while the reference file is in there correct location: Reference file not found D:\Dashboard UI\backstop_data\bitmaps_reference\backstop_default_Home_Page_0_document_1_Desktop.png
ENGINE ERROR: net::ERR_ABORTED at https://www.employeeportal.com/
@loopy3025 Did you manage to solve it? I have the same problem.
I've got a test that is, for some reason, looking for the wrong reference file. The scenario is callled "media center" and when I run
backstop reference --filter="media center"
, it generates the files as expected.But when I run
backstop test --filter="media center"
, I get the following response:Why would it be looking for "_0__0_mobile" and such when it should be looking for "_0_document0" and such?
The odd thing is that this doesn't occur with all the scenarios. They all create references with "_0document" in the filename, but only some of the tests come up with Reference image not found. The references are there, but some of the the tests just aren't looking for the correct file name for some reason.
The test:
Generic settings: