Painless visual test automation
npm install appraise
Appraise is a tool for visual approval testing. It can help you:
- Review and approve changes to web pages, visual layouts and browser components quickly through visual inspection
- Automate acceptance/regression tests for visual look and feel in a visual language, rather than xUnit style code
- Publish easily maintainable/verifiable developer docs with visual examples to Github easily (markdown) or as a static site (html)
- Start Spec by Example/BDD from a sketch (hand-drawn, wireframe, or from a graphic tool), easily compare actual outcomes, then just approve the final result to make a regression test
This is what it will help you do in the near future:
- Speed up visual exploratory testing by making it easier to rebuild visual components from example data/configuration
- Run visual tests quickly/in parallel using AWS Lambda
For a more detailed introduction on when Appraise might be useful and why we built it, check out:
* Painless Visual Testing presentation from Agile Tour Vienna 2017.
* Slides from the Painless Visual Testing presentation
* Automating Visual Testing with Appraise, interview with Gojko Adzic for InfoQ
The files in the Examples directory are automated tests, described in Markdown, that nicely render when viewed in GitHub and serve as living documentation for the tool. Check out the raw markdown source to see how the tests are set up.
* Check out the Getting started guide to learn about the basics.
* The Docs directory contains all the information on command-line arguments.
* For more info on writing and managing tests, check out:
* Creating test pages
* Customising execution
* Fixture types
* Formatting examples
* Controlling screenshots
Head over to the AppraiseQA Chat on Gitter and let's talk about it!
Alpha -- useful to us, let's make it useful to you together.
We've been using Appraise for a while now for developing MindMup so it is quite usable for our usage scenarios, but it's likely that we've not covered 100% of what you need.
Assume that before version 1.0, important stuff is likely going to change in a backwards-incompatible way based on community feedback.
Here's a list of tasks that we plan to do, so join in and take one of those!
MIT, see the license file.