Skip to content
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

"fullPage" Screenshot inconsistent / wrong stitching #2175

Closed
egucciar opened this issue Jul 19, 2018 · 3 comments
Closed

"fullPage" Screenshot inconsistent / wrong stitching #2175

egucciar opened this issue Jul 19, 2018 · 3 comments

Comments

@egucciar
Copy link
Contributor

egucciar commented Jul 19, 2018

Current behavior:

This screenshot compares 2 images taken from 2 runs on the same environment. They are both full page. there was no other changes between runs.

image

Desired behavior:

It would be better if the fullPage could always be captured like the below screenshot. However, from one run to the next, it can be inconsistent, sometimes looking good, sometimes looking not so good. At least it should be consistent, if not perfect, so that we are not at risk for false negatives when diffing.

Steps to reproduce:

compare full page screenshots from one run to the next and observe their inconsistency.

Versions

cypress 3.0.2, circleCI linux

Note: A nice feature would be to have better control over the "viewport" size of the headless test runner so that we could take longer/wider screenshots, rather than relying on a algorithm that cannot perfectly replicate with accuracy what users see.

@maple-leaf
Copy link

maple-leaf commented Apr 12, 2019

I can confirm this issue exists and happens very often. It seems like the algorithm that hide others and use helper pixels doesn't works well.
I don't know this would be possible, but can we run spec on cypress and take screenshot on puppeteer with headless chrome when current spec want to make screenshot, of course, all state should be kept?

@jennifer-shehane
Copy link
Member

Unfortunately we'll have to close this issue if no reproducible example is provided. Can anyone provide a way to reproduce this?

@cypress-bot cypress-bot bot added stage: needs information Not enough info to reproduce the issue and removed stage: needs investigating Someone from Cypress needs to look at this labels Jul 16, 2019
@jennifer-shehane
Copy link
Member

Right now there doesn't seem to be enough information to reproduce the problem on our end. We'll have to close this issue until we can reproduce it. This does not mean that your issue is not happening - it just means that we do not have a path to move forward.

Please comment in this issue with a reproducible example and we will consider reopening the issue. Here are some tips for providing a Short, Self Contained, Correct, Example and our own Troubleshooting Cypress guide.

@jennifer-shehane jennifer-shehane removed the stage: needs information Not enough info to reproduce the issue label Oct 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants