Transcripted Summary
Next, I would like to bring your attention to the Strict match level.
MatchLevel.Strict
The Strict match level is the next evolution of the pixel-to-pixel comparison. In Applitools, the Strict match level actually uses artificial intelligence in order to figure out whether the change that has happened on the page is perceptible to the human eye. So that's really what defines the Strict algorithm — Is it perceptible to the human eye? And if it is, then is going to be spot it out as a discrepancy on the web page.
If it's not a change that is perceptible to the human eye, it will not be spotted out.
So, in this case, in this example, as you can see, if I tap through, it's very easy to see, right?
This is perceptible to everybody — everyone can see all of these changes without a problem because they're so obvious. And so, of course, Applitools will spot this out.
The Strict algorithm will basically help you to identify any changes that can happen to the page.
So, color changes, text changes, if the font style changes, it can help you see changes in shadows. If this changes to different colors, it will spot it all out. Basically, the majority of this course is going to be performed using the Strict level.
The Strict match level is actually the default level that comes in your code whenever you're using Applitools.
Let me show you what I mean by that.
Whenever you're using the CheckWindow() method, or any other of the "Check" methods, and you didn't specify a match level using Applitools, then you get the Strict match level.
I'm going to cover these, all this code in a second, but just keep that in mind that Strict is your default match level and for the majority of the situations, it's usually the best level to use.
In fact, for myself in doing about 5000 automated visual validations using Applitools, I've discovered that using the Strict match level, I've never had a false positive. Any time that Applitools tells me that there is an actual failure, that there's an actual visual discrepancy, there has been a visual discrepancy.
Then the question arises, is it an actual bug or is it an expected change and maybe the requirements weren't updated. But that's a conversation we always have. But I've never had it point out a difference that wasn't actually a difference that needed to be looked at.
So, the Strict algorithm is very smart and helps you to reduce those false positives.
Resources
Quiz
The quiz for this chapter can be found in section 7.4.
