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.

Sign up for GitHub

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

Jump to bottom

Screenshot pixel comparison - visual regression testing #6874

Closed
ben-gooding-sky opened this issue Feb 14, 2022 · 1 comment
Closed

Screenshot pixel comparison - visual regression testing #6874

ben-gooding-sky opened this issue Feb 14, 2022 · 1 comment
Labels
STATE: Duplicate An issues has been already reported in the other thread. TYPE: enhancement The accepted proposal for future implementation.

Comments

@ben-gooding-sky
Copy link

What is your Scenario?

Visual regression testing using testcafe. Compare screenshots that testcafe takes to test for changes to page styling.

What are you suggesting?

Able to take a screenshot in a test, that then gets saved to a folder somewhere, then on subsequent tests that image is compared against to see for any regression.

What alternatives have you considered?

Currently use backstop.js, but we would much rather share our POM's and use the testcafe api to write these tests.

Additional context

No response
@ben-gooding-sky ben-gooding-sky added the TYPE: enhancement The accepted proposal for future implementation. label Feb 14, 2022
@need-response-app need-response-app bot added the STATE: Need response An issue that requires a response or attention from the team. label Feb 14, 2022
@VasilyStrelyaev VasilyStrelyaev added STATE: Duplicate An issues has been already reported in the other thread. and removed STATE: Need response An issue that requires a response or attention from the team. labels Feb 15, 2022
@VasilyStrelyaev
Copy link
Collaborator

Thank you for your suggestion!

However, we have a similar one here: #1207. Thus, I'm closing this issue. Please subscribe to #1207 to stay tuned and keep track of our progress.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
STATE: Duplicate An issues has been already reported in the other thread. TYPE: enhancement The accepted proposal for future implementation.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@VasilyStrelyaev @ben-gooding-sky