Authors
Feature Friday – Improve Your Testing With New Wait Action Types
Tired of waiting around just for… waiting around? Well, we are too here at Qyrus! That’s why we have released our brand new line of action types all focused around… well… you guessed it… waiting! At Qyrus we strive to constantly improve our platform in any way, shape, or form possible. Waiting might seem something small or not very important, but we’re joined here today by Tim and Suraj to convince us exactly why it is all that important. Well, we won’t keep you waiting any longer, let’s jump right in!
Tell us more about the new wait action types and their possible use cases.
Suraj: With the wide variety of new wait action types, users now have more conditions that can be checked before continuing with an execution. In general, it’s a major improvement compared to just applying implicit waits, which wastes a lot of precious execution time.
Tim:
Imagine we are waiting for a certain element to load and it usually takes anywhere between 2-5 seconds to load. Instead of having to apply implicit waits all throughout the test, a user can use the “Wait for Element” action type that will just wait for the element to load. Some other new wait action types we have include waiting until an alert is present, waiting until the title of the page or URL equals a certain value, or waiting until an element is clickable or is visible.
What is the overall impact on the testing process that these new wait action types might have?
Tim:
Well, like Suraj just stated, it saves a lot of execution time. Instead of possibly wasting a few seconds here and a few seconds there, which add up over time, we can use these new wait action types. And that will help overall with test building and test coverage. With these new action types, we are able to cover more scenarios and edge cases that might pop up.
How might these new action types help testers, developers, and business technologists? What value can they bring?
Suraj:
Testers will be able to be smarter about how they build out their test scripts. They will utilize the new and helpful action types to not waste time during execution and better handle the scenarios they encounter.
Tim:
It just makes sense to use these new wait action types over regular implicit waits. They work so much better and actually make the tests run better. And if for some reason the element you might be waiting for takes too long to load, we also include timeouts in the action types. That way, you don’t waste time waiting for a condition that is never met.
Suraj:
Developers and business users will see how easy it is to work with and implement these action types and create more complex and advanced test scripts to cover a wider array of scenarios and use cases. Qyrus’ whole idea is that it’s easy to use and simpler than actually learning a code base and using some library like Selenium for automated testing.
Does the same or similar functionality exist without Qyrus, and how do competitors address similar problems?
Tim:
Well, yes, these capabilities do exist outside of Qyrus, like in traditional test automation using Selenium for example. However, it’s much more difficult than it might seem to code out these capabilities into your test automation framework. Instead, Qyrus has everything ready for you right out-of-the-box.
Suraj:
That’s exactly the point. Qyrus is an intuitive, simple, easy-to-learn, comprehensive platform. Although we call it simple, when utilized correctly, Qyrus can automate your entire testing process from start to finish.
How do you possibly see these new action types impacting day-to-day operations across organizations?
Suraj:
Well, it’ll change how these tests are being built on a day-to-day basis. I know it sounds a bit like a broken record, but again, instead of using implicit waits, users can use these new action types to make their scripts run better.
Tim:
But on top of that, instead of adding some implicit wait, executing a test, and then waiting for the execution to finish just to find out that the wait wasn’t long enough is a big time consumer. Because at that point, the tester then would have to go back to the test script, change the wait value to a higher number, and then execute again. Let’s then assume that during the building process this happens multiple times. Something that with our new action types would take minutes to build now takes up to an hour if not more to build out due to trial-and-error runs.
Wait! Don’t click out yet! We just wanted to thank you for your time and for reading our Feature Friday blog today. We hope you learned something about… waiting… and hope that we were convincing enough in our argument that waiting is in fact all that important. Well, without keeping you waiting any longer, we wish you a very happy weekend. The weather is getting nicer, so stop waiting around and get outside and enjoy the weather! Thanks!
