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

Choosing an apt threshold for Visual Regression tests #143

Open
sharath-sriram opened this issue Mar 3, 2020 · 0 comments
Open

Choosing an apt threshold for Visual Regression tests #143

sharath-sriram opened this issue Mar 3, 2020 · 0 comments
Labels
enhancement New feature or request good first issue Good for newcomers

Comments

@sharath-sriram
Copy link
Contributor

Current Scenario

All existing components have a visual regression threshold of 0.1. This means that Visual Regression will not throw errors until the difference in the images crosses 0.1. While this works fine enough at the moment, there are times when the threshold fails to identify certain breaking changes for a few components. At such times, it is left to the developer committing the changes to responsibly identify the scope of error and reduce threshold to create new reference images and revert back to the old threshold.

What needs to be done ?

Given how each component has its own set of renders for which the visual regression tests are run, it will make sense for the developer to identify what might be an apt threshold for each of the components and set the same, ensuring that it doesn't fail on CI. It is definitely not a necessity that we should maintain a uniform threshold (open to arguments on this) for all components.

For more understanding on how the mismatch threshold is calculated, visit:
https://github.com/rsmbl/Resemble.js/blob/af57cb2f4edfbe718d24b350b2be1d956b764298/resemble.js#L495

@sharath-sriram sharath-sriram added enhancement New feature or request good first issue Good for newcomers labels Mar 3, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

1 participant