Authors
Feature Friday – Web Test Recorder and Its Capabilities
Friday? More like Fri-YAY! The weekend is here and our time to unwind and relax is nigh. Call the pizza place, get some soda, pop in a movie, whatever it is you like to do to relax. However, before we do, we’d like to thank you for joining us for this weeks’ Feature Friday! This week Adhiraj and Parth join us from our Chicago Qyrus team to give us a little bit of an insight to Qyrus’ web recorder tool. Whether you’re still at the office or kicking up your feet at home – or kicking your feet up at the office – let’s get into it!
Tell us more about the web recorder offered by Qyrus and its use cases.
Adhiraj:
The Qyrus web recorder is an extension that we offer on Google Chrome. It helps users record their steps and actions in the Chrome web browser. It’s quite helpful in how fast it allows us to build tests out, especially if it’s primarily navigational. Afterwards, it just imports straight into Qyrus and is editable and executable right away.
Parth:
The recorder does go even further, though. You can do some dynamic data handling as well as the basic verifiers from the recorder tool, as well. It’s not just limited to navigational actions. And the local browser execution allows for you to execute these tests you’ve built locally.
Well, doesn’t this sound familiar? Just the other week, we covered Qyrus’ mobile test recorder and its capabilities. Many similar advantages exist between the two. So, let’s dive deeper and learn more about the web recorder.
What is the web recorder’s overall impact on the testing process?
Adhiraj:
Well, mainly, it has the most impact on test build ing. I mean, it’s a recorder, after all. So it takes the need of having to manually build these steps out of the equation. And that’s stating something, because prior to codeless test building like on Qyrus, it would take even more of an effort to build a simple test.
Parth:
That’s right. Essentially, it takes Qyrus test building to another level. It was easy before, but now it’s even easier. And with things becoming easier, it can save a lot of resources in terms of working hours spent writing and building test scripts.
Adhiraj:
I’d even say that it can help with overall test coverage in the same manner. With building becoming faster, coverage can increase. The recorder prevents testers from having to write long lines of code.
How might the web recorder help testers, developers, and business technologists? What value can this feature bring?
Parth:
Well, obviously, this feature is a great thing for testers. It can cut building time down in half if used. On top of that, the tests you build using the recorder can be extremely complex. However, sometimes we see that more technical users prefer to go at it in a more manual fashion due to their expertise in the matter already. With that, we see less technical users taking more advantage of this tool.
Adhiraj:
I’d agree with Parth on that. I mean it really is a fast and effective way to build out complex test scripts. But with regards to developers, they can use it to also build their unit tests. And with business technologists, we see them taking advantage of this tool to build out tests of their own. It’s pretty easy!
Parth:
Developers can also build tests on localhost apps! In that way, testers already have a few baseline tests for when the app is in QA or staging. And, this extension also allows users to make localhost API calls.
That’s fascinating. All of the benefits that come from the web recorder are evident. This feature makes a lot of sense to have, and leads us to ask Adhiraj and Parth…
Does the same or similar functionality exist without Qyrus, and how do competitors address similar problems?
Adhiraj:
Well, it is true that other recorders exist out there, but none that can offer the same capabilities that the rest of Qyrus does. Along with the tests you record, the reports you get back are unparalleled. The information, visual reporting, and logs provided are great.
Parth:
And many other recorders out there don’t work out of the box like ours does. All that’s required is to download an extension on Chrome! We also plan to extend our recorder to other browsers, as well. And if you wanted to make your own recorder, well that’d take a lot of coding and prior knowledge.
Very well, other tools like this do exist out there, but it’s obvious from the points Adhiraj and Parth made that none are as versatile and powerful as ours. When looking at the bigger picture, the overall testing process, it’s evident that our web recorder (combined with powerful reporting capabilities, etc.) is a pack leader.
How do you see the web recorder impacting day-to-day operations across organizations?
Parth:
As we’ve mentioned before, it definitely makes test building easier. So, you’d probably see a typical tester spend a lot less time on test building in their day-to-day operations. Not only that, but a significant less amount of manpower would be required to complete the same tasks.
Adhiraj:
All that’s really required is knowledge of the platform being tested.
Parth:
Yeah, overall it really saves time and money. These resources can be spent in other areas of the business, whether that be more focusing on user experience or expanding and improving applications.
Is that pizza I’m smelling, or is it just the weekend getting to me? We won’t keep you guys any longer than necessary! Thanks for joining us on this week’s Feature Friday! We hope that you learned quite a bit about the power of our web recorder feature that we have on Qyrus. Take a look for yourself and start a free trial this weekend! (Or on Monday, we wouldn’t blame you!)
Join us next week for more exciting news and information on features!
