You asked, we delivered
We love to get feedback from users, and this month, we took that feedback to heart and delivered some often-requested enhancements. We're super excited about the results!
You said the “Baseline,” “Both,” and “Reject” options were too pedantic and inscrutable. We heard you.
When resolving changes, if the change was due to an intentional change, you now select “Correct Behavior.” If the change was due to dynamic application content or application data, now select “Dynamic Content.” If the change was unintended, now select “Defect.” We think these options make a lot more sense.
You let us know that your Scan results were too "noisy." We addressed this by adding additional configuration options that allow you to “mask” some changes and some additional “smarts” to better identify things that merely moved. Spotter now also provides significantly more recommendations. For example, it now makes an appropriate recommendation when a style or class change did not affect how the element is rendered.
On average, Full Scans complete in 35% of the time they did before. Not only did we make Spotter work faster, but we also made it work less with improved Event deduplication logic.
We also made many other small tweaks and improvements.
If you’d like a personalized walkthrough of these changes, let us know, and we’ll be happy to do it.
Making you more efficient
This month, we focused on making you more efficient in Spotter. Whether it's with new features like the ones listed below or by continuing to reduce Scan times, we're committed to making your testing efforts as productive as possible.
Grouping Scan Paths makes it easier to organize your Paths. Initiate Scans for all Paths in Group with a single click or a single webhook call.
You may now test various scenarios within the same Dataset by supplying more than one set of values for each form. This can significantly reduce the number of needed Datasets.
Quickly find a specific change by filtering the change lists.
To learn more about Spotter's recent enhancements, Sign up for a demo today
Identify visual defects quickly
While visual testing should never be used as the only means of testing, it's helpful to know if code changes affect the display of your app. Spotter now indicates when a View is visually different from the baseline.
Spotter also allows you to see each change individually and indicate if that change was intended.
To learn more about Spotter's visual testing abilities, Sign up for a demo today
Testing across iframes
Testing iframes is tricky. The security features browsers implement to protect users from malicious iframe content also make testing content informs nearly impossible.
Spotter changes all of this. In this month's release, Spotter now scans the content of iframes. You can now interact with elements inside iframes the same way you can with regular page content.
To learn more about Spotter, sign up for a demo today.