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

Add a way to run quick screenshot tests to catch simple differences early #10137

Open
jcfranco opened this issue Aug 21, 2024 · 0 comments
Open

Add a way to run quick screenshot tests to catch simple differences early #10137

jcfranco opened this issue Aug 21, 2024 · 0 comments
Labels
0 - new New issues that need assignment. estimate - 13 Requires planning and input from team, consider smaller steps. p - medium Issue is non core or affecting less that 60% of people using the library tooling Issues relating to build system fixes or improvements.
Milestone
2025-05-13 - 3.2....

Comments

@jcfranco
Copy link
Member

jcfranco commented Aug 21, 2024 •
edited
Loading

Priority impact

p - medium

Summary

We need a way to run quick screenshot tests locally to catch simple visual diffs early. This feature will allow developers to detect and fix visual regressions before submitting to Chromatic, helping to avoid unnecessary team involvement and keeping our screenshot quota low.

Desired Outcome

Implement a local screenshot testing mechanism that allows developers to identify and address visual regressions early in the development process. This feature should be easy to integrate into the existing workflow, enabling automated detection of visual differences before they reach the Chromatic review stage.

Resources

No response

Additional information

No response
@jcfranco jcfranco added tooling Issues relating to build system fixes or improvements. 0 - new New issues that need assignment. needs triage Planning workflow - pending design/dev review. p - medium Issue is non core or affecting less that 60% of people using the library needs milestone Planning workflow - pending milestone assignment, has priority and/or estimate. estimate - 13 Requires planning and input from team, consider smaller steps. and removed needs triage Planning workflow - pending design/dev review. labels Aug 21, 2024
@geospatialem geospatialem added this to the 2025-01-28 - Jan Release milestone Sep 6, 2024
@geospatialem geospatialem removed the needs milestone Planning workflow - pending milestone assignment, has priority and/or estimate. label Sep 6, 2024
@geospatialem geospatialem added the needs milestone Planning workflow - pending milestone assignment, has priority and/or estimate. label Feb 18, 2025
@geospatialem geospatialem removed this from the 2025-02-25 - Feb Milestone milestone Feb 18, 2025
@DitwanP DitwanP removed the needs milestone Planning workflow - pending milestone assignment, has priority and/or estimate. label Feb 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
0 - new New issues that need assignment. estimate - 13 Requires planning and input from team, consider smaller steps. p - medium Issue is non core or affecting less that 60% of people using the library tooling Issues relating to build system fixes or improvements.
Projects
None yet
Milestone
2025-05-13 - 3.2.0 May Main Release
Development

No branches or pull requests
3 participants
@jcfranco @geospatialem @DitwanP