Authors
Feature Friday – How Qyrus Device Farm Can Improve Your Testing Process
Shoes, clothing, and water bottles, with almost all consumer items, there is often a negotiation between quality and price. As brands flourish on being high quality and best in class, consumers can often find a similar money-conscious option available. But as with most decisions, it is important to be critical and note that if it sounds too good to be true, it just might be. These ideals remain true across a range of industries, including development and quality assurance. This week’s feature Friday discusses manual and automated testing using the Qyrus device farm, and some of the benefits of testing applications using real Android and iOS mobile phones and tablets located across the globe. Let’s dive in as we interviewed Jorell and Raoul to learn more.
Tell us more about the testing process using the Qyrus device farm, its use cases, and its impact on testing and QA processes?
Jorell:
Though very powerful the Qyrus device farm is actually simple. Real physical Android and iOS devices hosted within the cloud to support manual and automated testing of native applications and web applications.
Raoul:
Exactly, all the functionality, each test has videos, screenshots, performance profiling metrics, and device logs. This means that if a defect is found – the developer has as many pieces of evidence to comprehend, recreate, and remedy the issue – Qyrus has native configurations to Jira which means an issue can be filed directly from the Qyrus test report!
Does the same or similar functionality exist without Qyrus, and how do competitors address similar problems?
Raoul:
Prior to device farm capabilities and during the testing process, testers would have to set up and maintain all required devices for testing purposes. Missing out on a range of features and functionalities, the process also requires more resources and time.
Jorell:
And though other device farms exist, Qyrus differentiates itself through experience and capabilities. Feature-rich including the ability to toggle between network options, extensive reporting with screenshots and videos, all the way through offering beta and previous versions of Android and iOS to test on.
What is the overall impact on the testing process when using the Qyrus device farm?
Jorell:
When considering the testing process as a whole, the device farms impacts are clear. From the beginning, device setup, and maintenance are mitigated. That’s a heap of time and resources, and as requirements grow, the cloud-native solution grows as well, offering custom and private device options.
Raoul:
Furthermore, during the testing process devices are easily accessible at all points in time. Teams can share devices, monitor runs across devices, and test in parallel, with extensive reports and collaborative features making the entire testing and QA process more efficient.
How might the Qyrus device farm testing options help testers, developers, and business technologists? What value can this feature bring?
Raoul:
Very broadly – you can test any scenarios, applications, and devices through this feature. Anything that the tester needs from manual testing to automated testing is both available, maintained, and ready to scale up or down as requirements change with no testing or developmental resources or overhead from the client side. This increases test case coverage allowing testers a range of devices on hand to test application functionality.
Jorell:
We often find developers uploading beta versions of Android and iOS applications to test within the developmental process. Furthermore, with out-of-the-box Jira integrations, communication between developers and testers becomes seamless. Promoting high-quality applications.
Raoul:
Furthermore, coupled with an amazing UI and rich visual reporting, Qyrus creates ease of access for business analysts to access application information. Providing screenshots, videos, and the ability to email and download reports, Qyrus provides the necessary application information and collaborative capabilities for business analysts to integrate themselves into the testing process and QA lifestyle.
How do you see the Qyrus device farm impacting day-to-day operations across the organization?
Jorell:
The day-to-day impacts of this feature cannot be downplayed. Teams have access to any and all required devices for testing purposes. By enabling efficient testing utilizing parallel testing features, testers, and developers can establish functionality across a multitude of both Android and iOS devices simultaneously.
Raoul:
Furthermore, by offering both private devices and a public device pool, clients can utilize devices across the globe. Test case coverage is no longer a concern. Furthermore, with options to scale up and down as seen fit, clients can ramp up devices during release and scale down accordingly to prevent excess spending as requirements change.
As applications dominate the forefront of business, there are certain things that are worth going the extra mile for. High-quality mobile applications are functional regardless of the device. But building out device-agnostic applications and testing them across a range of Android and iOS devices to promote the best user experience can be a daunting task. With a multitude of devices and mobile operating systems at your fingertips, and the ability to upload and test beta versions of applications, within a powerful solution providing robust visual and data-driven reporting, Qyrus’ Device farm aims to mitigate all aforementioned headaches by increasing testing efficiency, coverage, and enabling high-quality application production.
