The year 2022 is now coming to a close and, with that, we come with our final installment of Feature Friday for 2022, as well. Over the last year, we have talked about numerous features and qualities of Qyrus that highlight just exactly how we improve testing. And, if you’ve been paying attention, you’ll realize that Qyrus is chock-full of useful tools and capabilities that improve all aspects of testing ranging from the test building phase to the test executions, and in the end the reporting and analytics. And, along the way, we’ve made several small and large quality-of-life updates that aim to improve the smaller but still important aspects of day-to-day testing. So, today, we will take a stroll through memory lane and recap and highlight some features that augment different aspects of testing.
The aim of Qyrus is to enable testers to build tests in a more efficient manner. Through reducing the amount of time it takes to build tests, the testing process as a whole has reduced its lifecycle significantly. There are many ways that we help achieve this goal, but to highlight a few:
When it comes to building test scripts for mobile applications, Qyrus has a mobile recorder that enables users to build tests by recording user actions performed on a mobile device. It’s super simple and intuitive to use and is enabled by the click of a button. More advanced actions like performing verifications can also be recorded during this process. More information about our mobile recorder can be found here in its edition of Feature Friday.
And very much like our mobile recorder, Qyrus also has a web recorder. It does all the same great things that the mobile recorder does, allowing users to have test scripts built around recording their actions on a web page. The Feature Friday for web recorders can be found here and provides more information.
Qyrus enables users to also inspect elements on a mobile application. This means that more precise test building can be done. Instead of recording user actions, enabling the inspect mode gives users the ability to get locators of specific elements as well as the ability to verify the existence of elements on a page. To learn more about inspect mode, you can find its Feature Friday here.
Building, rebuilding, and rebuilding again is no way to go about creating your suite of test scripts. Qyrus enables users to reuse test scripts in multiple ways. This empowers testers to spend less time recreating some script that already exists out there. This can also help empower collaboration and teamwork. Click here to learn more about how reusing test scripts can help speed up testing.
Once test building is out of the way, the continuous execution of test scripts is the next thing on the list. Comparing traditional Selenium testing to Qyrus is like comparing night and day when it comes to test executions. Qyrus already has all that one might need, and we’re here to highlight a few below:
Qyrus enables users to execute two tests at the exact same time. This already doubles our efficiency when it comes to test execution, but Qyrus can go even beyond that. Parallel testing in Qyrus gives the users the ability to execute as many tests at the same time as their concurrency allows. This means that, if one has the resources, they can execute 5, 10, 20, or even 50 tests all at the same time. This means that Qyrus can scale to the needs of the client. Read more here about parallel testing.
Test data management in Qyrus brings another testing tool into the fold. No longer do testers have to manage or create their own test data – or perhaps use a 3rd party tool for that – but instead it can all be done right on the Qyrus platform. Create test data manually, have Qyrus synthetically generate data for you, or grab data from an API call or database query. Click here to learn how test data management can augment testing today.
Utilize data-driven testing on Qyrus through the use of our parameterization feature. By selecting to parameterize specific steps in a script, a tester is able to take one script and have it cover multiple scenarios. As a simple example, imagine having a login script that can be parameterized to test not just one login, but the login of dozens or even hundreds of other accounts into the system. Through the use of test data management, parameterization becomes an even more versatile tool. Learn more about parameterization here.
The most important thing, arguable, is how the reporting is generated by a testing system. Whether that be manually collecting screenshots of reports, keeping some spreadsheet to track testing progress, or using some other test management tool, reporting can often times be fragmented and not adequate. On Qyrus, we automatically generate sharable reports that come with step-by-step analytics with screenshots and video evidence. However, that just scratches the surface as to what capabilities Qyrus has when it comes to reporting and analytics. Let's take a look at a few features that augment this area:
Although simple, this tool can be extremely useful in certain situations. Comparing API reports is a feature that Qyrus implemented to make life a bit easier for users who must constantly go back and forth between API reports. Although a small task, it can become rather tedious through repetition. This is a great example of how Qyrus takes into account user feedback and ways that we can help improve our platform to become even more all-encompassing when it comes to testing. Learn more here about comparing API reports and hear more from our team.
Keeping up with the health of APIs, especially when there are a lot of them, can be quite a challenge. Ensuring that response times are in an acceptable range, that the API doesn’t go down every now and then, and that the responses are correct are all things that can take up a lot of time Qyrus has a useful tool that can do all of that for you and provide you with notifications about the health of your API. Read here about how API monitoring helps testers today.
Last but certainly most not least is performance profiling. Qyrus is able to get performance profiling metrics for your mobile applications during test executions. This gives better insight for the tester into how an application might perform on different mobile devices or while performing different tasks. A slow or clunky application is not a good one, and Qyrus can help assure the opposite of that for your applications. Click here to read more.
I hope that that stroll through memory lane helped jog your memory about a few of our testing capabilities and features. We’re just scratched the surface here when it comes to that, however, and we still have so many more features to talk about in future editions! Qyrus is an ever-evolving platform that hopes to meet the needs of every tester across every type of testing. We’re like a one-stop-shop when it comes to testing. Next year, we’ll touch on new features like Qyrus Bot, new updates to analytics and insights, as well as new updates to web, mobile, and API testing, and so much more! New features are always just around the corner with Qyrus.
Thank you for joining us for our final edition of Feature Friday for 2022 and we hope you will join us for more next year! Happy holidays to everyone on behalf of the Qyrus team!
Don't miss out on this must-attend event - mark your calendars for April 30th to May 5th, 2023 and join us at #STAREAST!
Performance profiling metrics on Qyrus enable testers to get a more granular view of how their API or APIs perform over time.
There have been a range of additions to mobile test building that make the process even simpler and more efficient. Learn More how you can improve your Mobile Testing with Qyrus.
The Xray integration is an out of the box integration that provides a link between your Xray issues and your Qyrus test scripts. Upon execution of these test scripts, the results are then populated straight to Xray to view execution results and updates from a single platform.
Low-code/no-code platforms can provide a wide range of benefits for teams in the testing industry. By identifying specific use cases, carefully evaluating different platforms, and implementing governance and security measures, teams can use low/no-code automation to improve their testing processes and achieve their goals
Testing an individual API is good but testing the functionality of multiple APIs together in a chain is an even better API testing strategy because that’s how APIs work in a real-world scenario.
CLI commands allow users to interact with, inspect, or execute automated test scripts without visiting the Qyrus UI. They have a range of functionality including allowing testers to execute scripts, update global variables, upload IPA/APK files, delete IPA/APK files, and send reports via email, all through pipeline.