Authors
Feature Friday – How Device Farm Can Improve Your Manual Testing
As a Chicago based company, we often get queries about the weather and statements like, “No way it’s snowing in April!” And we explain to others that this is what we deal with every year. As we all know, seeing is believing and one can never truly understand Chicago weather until experiencing it. Much of the same can be said about testing. Visual testing is at the forefront of innovation as it holds the ability to clearly show problems in action.
This week’s Feature Friday is brought to you by Jorell and Ameet who will discuss Qyrus’ manual testing feature which uses real devices located in device farms across the globe to promote visual and interactive application testing.
Tell us more about manual testing offered by Qyrus, its use cases, and impact on testing processes?
Jorell:
That’s a great question, the purpose of this feature is to allow users to manually test applications, generating reports based on different use cases. Simply select a device, launch your application, and start testing.
Ameet:
And upon termination of test, a session report is automatically generated with detailed metrics and device specifics. Manual testing using device farm is a multi-purpose feature optimizing test building, live visual testing, alongside user experience and functionality testing.
Manual testing is one of the most common testing methods, and it’s been around for quite some time. As there are a multitude of manual testing options, it becomes integral to differentiate feature specifics and offerings that Qyrus contains.
Does the same or similar functionality exist without Qyrus, and how do competitors address similar problems?
Ameet:
You are correct, there is no shortage of manual testing solutions. Although Qyrus focuses on automated testing, the manual testing feature is still powerful. It gives you the freedom of live device interaction with the power of a device farm at your fingertips. Qyrus’ manual testing is a feature driven, comprehensive manual testing solution.
Jorell:
You can seamlessly switch from testing Android devices to iOS, from phones to tablets, and use built-in features to simplify mobile interactions and enhance the test building process. Not every testing and QA team has started their automation journey and our manual testing solution is a good transition to understand the Qyrus UI, devices, and device farm, even if automation is later down the pipeline.
Ameet:
Do manual testing options exist? Sure. But Qyrus’ feature-dense UI, extensive coverage, robust reporting, and scalability truly differentiate the platform from competition.
We’ve established the relevance of this feature and some unique qualities in relation to competition and other industry tools. And though being unique and relevant is important, nothing is more important than practicality and usage. It is essential that the feature promotes value, leading us to ask:
How might manual testing with Qyrus help testers, developers, and business technologists? What value can it bring?
Jorell:
Business analysts gravitate to this feature because when we say device farm and live-testing we mean it with emphasis. Interact with a real device that’s running your application in real time, taking notes and screenshots along the way. This level of visual testing allows business analysts the ability to test application functionality and user experience enabling the development of quality applications.
Ameet:
Developers love saving time and money on application testing. Qyrus gives users the ability to login and start interacting with their application across a range of devices and operating systems. Afterwards, they are provided with a session summary with vital test device metrics including CPU usage, RAM usage, and network usage data. All of this data is stored on Qyrus and easily visible to any team members, additionally test reports of defects and their evidences can easily be added to Jira with our native integrations.
Jorell:
Let’s not forget testers. We find testers downloading their applications across Android and iOS mobile devices and tablets. Further utilizing the device freedom to test websites and web applications across mobile device browsers, testers have the freedom and resources to test edge cases and take a shift-left in the testing lifecycle.
Understandably, this feature produces value for multiple personas across a business or organization. But what establishes the quality of a feature is its reusability. The difference between a good and a great feature comes with usage. In other words, is this a one-time-use feature, or is this a feature that will be referred to consistently throughout the testing and QA lifecycle?
How do you see manual testing impacting day-to-day operations across organizations?
Ameet:
This depends on the maturity of the user’s automation journey. If there is no prior automation, this is the perfect stepping stone to achieving test automation. With a device farm full of testing options, interactive and feature dense testing, alongside rich visual and data driven reporting, Qyrus’ manual testing option with a device farm provides a robust solution.
Jorell:
And, assuming there is a level of automated testing, the manual testing solution still offers a location for visual testing, robust visual reporting capabilities, and device metrics upon session termination. Automation is not perfect, and a quick connect manual testing feature offers an advanced troubleshooting option.
What is manual testing’s overall impact on the testing process?
Jorell:
Qyrus’ manual testing feature is continually optimized with features to promote the best manual testing option. As one of our original testing solutions, it has developed in succession with the entire platform. As our knowledge of testing and automation increases, we continually monitor and innovate our manual testing solution.
Ameet:
Our original automated testing solutions were created with the knowledge and understanding brought about by years of manual testing. These fundamentals can be seen throughout Qyrus’ manual testing solution. We find using the UI and familiarizing yourself with device farm leads to a swift automation journey when implemented, especially when using Qyrus.
Jorell:
And with these thoughts in mind, we see manual testing as not only a powerful, well-built solution, but a gateway for companies who have yet to begin their automation journeys to optimize their current testing and QA lifecycle and streamline their road to complete test automation.
That concludes our interview with Jorell and Ameet about manual testing using the Qyrus device farm. We’ve discussed use cases and specifics, how manual testing can help different users, and the overall impact of this feature on the testing process. Join us next week on Feature Friday as we speak on more new and exciting testing features that help mitigate stressful situations. Until then, relax and enjoy the weekend!
