You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 16, 2022. It is now read-only.
Research the possibilities for automated visual testing, build a proof of concept, and supply a pull request. Ideally, this solution should conform to the following:
Able to run with a package.json script (similar to npm run test) so we can use it with Travis CI.
Have some option to automate internet explorer 11 testing, as this is important to the corporate market. (Suggestion: connect to BrowserStack with a webhook via Travis)
Compare supplied screenshots of desired output with screenshots that the tool makes on-the-fly to assess the correctness of the result.
Acceptance criteria
Research best tool to do automated visual testing with and post a small report of research results as a comment on this issue
Test with a simple component, such as button, and prove it works -- both a passing and a failing test
Make a package.json command like npm run test or similar to run the test.
Add to the Travis YML file and make sure on every build the test gets run on all components
Let Travis do an Internet Explorer 11 test on certain conditions -- at least on merges to develop and master, but preferably on every build.
The text was updated successfully, but these errors were encountered:
Description
Research the possibilities for automated visual testing, build a proof of concept, and supply a pull request. Ideally, this solution should conform to the following:
npm run test
) so we can use it with Travis CI.Acceptance criteria
npm run test
or similar to run the test.The text was updated successfully, but these errors were encountered: