Easy Screenshot Comparison Means More Effective Testing
by Pamela Gillaspie, on 2/28/19
You’ve tested the latest release of your application, and it works just fine. From a functional perspective, it does everything it’s supposed to.
But what if the user experience has changed in a way that wasn’t picked up in functional testing?
For example, it might still be possible to tap on a button, but perhaps the text above the button is no longer visible, and it’s no longer clear what that button does.
The latest addition to Eggplant’s Digital Automation Intelligence suite introduces screenshot comparison—the ability to look at a screen (or part of a screen) on your system under test and tell you what has changed.
Screenshot comparison can tell you...
- If anything is missing from your screen since the last time you tested
- If things have moved
- If anything new has appeared
- If the text or other content of an item has changed.
What are some good uses of screenshot comparison?
- Ensuring that controls appear where the user expects to find them. This is important for any application but could be critical in a healthcare or military context.
- Ensuring brand consistency.
- Sanity-checking a layout.
- Being aware of new elements to test in your application.
Show me some examples!
Here, an item from the baseline is missing from the current screen:
This time, the advertisement is present, but the content has changed:
Here, there is a new item on the current screen:
How do I get started?
If you’re already using Digital Automation Intelligence, we’ve designed this feature to have virtually no set-up requirements. You will just need to make sure you’re using the latest version of Eggplant Functional.
Just put a CompareScreen command in your script with a descriptive name (like CompareScreen “HomePage”), and a baseline image is captured for you on your first execution. Every time you run that test, the current screen is compared against your baseline (read the full documentation).