-
Notifications
You must be signed in to change notification settings - Fork 921
Adding visual testing #495
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
base: master
Are you sure you want to change the base?
Conversation
Updated package.json and yarn.lock to include necessary packages for automated visual regression testing to compare visual results the way a human would percieve them.
thanks for doing this! this is awesome! however, there is a small issue. I want this to run on ci on pull requests. but travis ci has some limitations on environment variable not being able to be accessed by builds on fork pull requests |
Hey @wuweiweiwu any luck with the TravisCI issue for this? |
Hey @wuweiweiwu, looks like this PR is passing all checks and is g2g. Can we go ahead and merge this in? cc @hannah |
Hey @wuweiweiwu pinging again to bring this to your attention. It is good to merge, is everything g2g on your end? |
@wuweiweiwu have you had a chance to look at this? Would love to get this merged ASAP |
@wuweiweiwu just pinging again on this. |
@wuweiweiwu another ping. would love to get eyes on this. |
@wuweiweiwu @tiff another ping hoping to see if y'all have had a chance to take a look at this |
@wuweiweiwu @tiff any luck with the Travis CI issue or had a chance to look into this? |
@wuweiweiwu @tiff any chance y'all can take a look and get some eyes on this? Would love to get it merged. |
@wuweiweiwu still looking to get this merged. any chance you have looked at this PR? |
@wuweiweiwu pinging again. thanks! |
This is crazy.... This repo is forsaken by maintainers... |
while this is nice to have, I think there are more critical issues that needs to be worked out in this repo, so i didn't do anything about it. |
Hi everyone!
I saw that you all were using Storybook, and thought that adding some visual testing would be helpful!
In case you aren't familiar, automated visual regression testing compares visual differences in a human readable manner, instead of comparing pixel by pixel as a machine would do. It's reflective of how a user will experience a website. The Storybook documentation has a pretty comprehensive overview of visual regression testing as a whole, and how it applies to React projects in particular.
Since Storybook is already installed in this project, adding automated visual regression testing was a simple task.
Applitools provides an SDK that makes testing easy. In order to run it, you need is to sign up for an Applitools account and add the key to your local environment. I’ve added
test:visual
as an alias that fits the current testing shortcuts in the command line.Applitools has a decent limit for their free tier accounts, but they also provide open source projects with free unlimited accounts if you contact them.