Skip to content

Conversation

hannah
Copy link
Contributor

@hannah hannah commented Jun 5, 2019

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.

Screenshot of completed visual regression tests in Applitools

hannah added 2 commits June 3, 2019 13:55
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.
@hannah hannah marked this pull request as ready for review June 5, 2019 17:29
@coveralls
Copy link

Coverage Status

Coverage remained the same at 75.579% when pulling 1f78280 on hannah:add-visual-testing into c87715a on frontend-collective:master.

@wuweiweiwu wuweiweiwu self-assigned this Jun 7, 2019
@wuweiweiwu
Copy link
Member

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

see frontend-collective/react-image-lightbox#177 (comment)

@cmwhited
Copy link

Hey @wuweiweiwu any luck with the TravisCI issue for this?

@cmwhited
Copy link

Hey @wuweiweiwu, looks like this PR is passing all checks and is g2g. Can we go ahead and merge this in?

cc @hannah

@cmwhited
Copy link

Hey @wuweiweiwu pinging again to bring this to your attention. It is good to merge, is everything g2g on your end?

@cmwhited
Copy link

cmwhited commented Oct 1, 2019

@wuweiweiwu have you had a chance to look at this? Would love to get this merged ASAP

@cmwhited
Copy link

cmwhited commented Oct 7, 2019

@wuweiweiwu just pinging again on this.

@cmwhited
Copy link

@wuweiweiwu another ping. would love to get eyes on this.

@cmwhited
Copy link

cmwhited commented Nov 5, 2019

@wuweiweiwu @tiff another ping hoping to see if y'all have had a chance to take a look at this

@cmwhited
Copy link

@wuweiweiwu @tiff any luck with the Travis CI issue or had a chance to look into this?

@cmwhited
Copy link

@wuweiweiwu @tiff any chance y'all can take a look and get some eyes on this? Would love to get it merged.

@cmwhited
Copy link

cmwhited commented Dec 2, 2019

@wuweiweiwu still looking to get this merged. any chance you have looked at this PR?

@cmwhited
Copy link

@wuweiweiwu pinging again. thanks!

@AndrewKiri
Copy link

This is crazy.... This repo is forsaken by maintainers...

@lifejuggler
Copy link
Collaborator

lifejuggler commented May 24, 2020

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.

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

Successfully merging this pull request may close these issues.

6 participants