Shannon Lee: So a quick recap on scriptless and validation.
So we did visit this in the last course. So if you need any refresher, I highly recommend our first course that we've done at Test Guild, but just do a quick recap.
( ** If you missed it you can watch the first course here **)
Scriptless or no code automation. It is powered by artificial intelligence that helps you write scripts so you don't write a single line of code. It's perfect to really hit that ground running in your automation.
So it helps you kind of jump over the hurdles of test automation that make it difficult to adopt mobile test automation. Specifically, mobile test automation could be very flaky. There's a big knowledge barrier as well. So you have to be aware of how to create scripts and how to code out scripts.
So for scriptless automation, that's not the case. It is actually no code.
So how it works is that A.I will capture a manual session, so you'll run one manual session, all that data, including all the top points of scrolling of any interactions with the device on your application are actually being captured by the A.I.
So Nova is Kobiton's AI engine. So in that manual session, or once you exit that session, Nova has the ability to capture that entirety of that session and be able to essentially rekick that off or revisit on additional devices without you having write a single line of code. The best way I like to put it is that scriptless automation will bring A.I. into play. It's kind of automating the automation process, so it's really creating those scripts for you so that you don't have to wait, not to use.
You don't have to spend time creating scripts from scratch or actually having to do your own homework to figure out what's the syntax or what's the code for writing out scripts. Now you have the ability to run one manual session and then be able to kick off and scale that across additional devices without having to write a single line of code. So that is a quick recap of scriptless automation.
Even further, Nova will also analyze those revisits to a baseline. That baseline could be a manual session or even an Appium script. We'll get to that in just a bit within this course. And as Nova's analyzing the baseline to those reruns, those kick-offs, or the revisits, we call them, any discrepancies that are found when comparing the two will actually be brought to your attention via validation.
So once again, we have text visual validations for functional testing as well as performance and accessibility validations for nonfunctional testing. So diving right into that Nova's text validation. So this really helps you see the difference between any text results from that baseline run can be done for a scriptless and scripted automation.
So when you think about manual testing or even in your script automation, it's very difficult to find that right. Like visually with your own set of eyes, it can be very difficult to do just that. So when we bring AI into play and to be able to analyze you might have heard pixel by pixel or text by text. The ability to analyze that via AI it one can be done in a far faster manner and two has the ability to catch more often than say, your own manual testing. Think about your application, maybe on a vertical view of the text line up correctly. But let's say you turn your device horizontally.
Now, you might have some like weird word wrapping, but you might have caught in you're testing. Maybe there's some even text misalignment. Anything of that sort, A.I can come into play to really help catch those for you via Nova's text validations. Same as text validations can be said for visual validation.
So here for both, more or less, we're actually incorporating visual testing into play, making use of artificial intelligence. With visual testing instead of catching more of the text, it's actually capturing your elements on the page.
So maybe your buttons or your page layout, any structural or layout changes across different devices and screen resolutions, how your application might look on an iPhone, say, 10 might look different on an iPhone 12 pro max or what have you or an iPad. So you're going from these different screen layouts and screen resolutions. It's very difficult to scale your testing given the amount of devices out there in the market.
And so incorporating visual testing into your say, of day to day testing once again helps you catch far more defects from a visual perspective, UI defects, making use of AI than you could have done, say, in your own day to day testing. This also can be done for scriptless automation or also with your Appium scripts as well. So once again, the ability to catch those visual differences by comparing the baseline run to any revisit session.
Nova can also catch performance indicators. Right. Nova can also catch performance response times, if you will. So from the moment that you tap an element. So say you want to tap that login button. To the time it takes for the next page to completely load and render and all the responses. And between any API responses, any of that communication to load the next page, any time those responses take longer than 2 seconds, Nova via performance validation will actually flag that and bring it to your attention to say, hey, looks like this API call or this response call, it took longer than 2 seconds.
There may be a performance scenario happening within your application that you might want to look into and see if you can help streamline your application responsiveness and reduce latency. I'm not sure about for you all, but whenever I am using an application and it takes a minute for the next page to load, I might get a little frustrated.
I might delete that application, and move on to a competitor application that's a little bit more streamlined and has a higher performance to it. So with performance validations also, any of the validations really helps you reduce that app abandonment also. And lastly, Nova can also be an accessibility checker essentially for your application via accessibility validation.
We are all accessibility is very important and it's a new trend bringing brought into the day-to-day of a quality engineer, a quality tester. We want to ensure that our applications are accessible by all users, even those with any visual impairments, color blindness, or any sort of limited accessibility, making use of an application.
So with that, any time Nova's comparing your application, if there is a scenario that's not meeting W3C compliant guidelines and the realms of color contrast and touch target size that should be flagged and brought to your attention from remediation essentially to say, hey, looks like this background color and this foreground color are too close and in color.
So anyone, like I mentioned previously with any visual impairment or colorblindness might not be able to see the difference and might not be able to really use your application. And that could cause some issues with the usability of your application. So accessibility is very important. So here Nova can actually help you meet W3C compliant guidelines in the realms of color contrast and touch target size.
Comments are closed.