The client is a London-based, consumer-facing fintech company founded in 2016, providing its customers with free digital-only accounts for personal finances.
The neobank startup set out with the goal to revolutionize social banking and make it as frictionless as possible through innovative products and enjoyable customer experiences. This is a case study of how the said challenger Neobank achieved this feat, more so on a tight budget.
The problem The hero of this case study, the challenger bank, was keen on automating their mobile testing for Payments, Split Transactions, Settlements, User onboarding, and User experience with a small testing budget. That meant the bank was burdened with several testing problems, including:
1. Insufficient QA testers The neobank had 4 manual testers for testing payments, and other software modules, given their low revenue and budget constraints. This meant that their software testing efforts took additional time and effort, wasting both time and resources.
2. Inefficient QA testing In addition to having a small number of testers, the bank was carrying out all its software testing efforts manually. This meant that the testing was prone to errors and cost several more employee hours.
3. High testing costs Perhaps most significantly, the bank wanted to test multiple client-facing applications across web, mobile, and business processes but did not have the budget to cover the costs. Had they not scaled up their testing rapidly, they would have faced multiple dissatisfied customers. This is precisely why they turned to Qyrus for help.
The solution After thoroughly screening multiple automation platforms on various critical parameters, the company selected Qyrus, the intelligent,codeless automation platform for Mobile and API licenses as well as devices on the Device Farm for both Android and iOS.
The challenger bank transformed its software testing for payments and other modules by training its QA testers to operate the Qyrus test automation platform for 3 weeks. With testers proficient with the platform and having a 9.5/10 comfort level using the tool, the bank moved on to improve its testing processes. Here’s how Qyrus helped with it.
1. Expanded test coverage Qyrus expanded the bank’s testing process and started off with 100+ Android and 200+ iOS tests built within the first few months, with an average test build time of 10 minutes. Besides that, Qyrus also scaled mobile and business process testing to increase instances, browsers, and devices, including 5 end-to-end business process tests. This made for a comprehensive testing system. In fact, the Neobank further expanded coverage by creating over 706+ Android tests and 716+ iOS tests with an average execution time of 5 minutes.
2. Fast tracked testing Through its AI-enabled plugin, Qyrus helped the bank startup deploy automated tests right after development, reducing the time spent on manually building and deploying tests. For perspective, the bank observed a 50% decrease in test build time through cloning (8 minutes per script) and close to a 5-minute execution time.
Furthermore, given the reports were uploaded directly onto the pipeline, Qyrus simplified reporting as well. Thanks to this, the challenger bank could validate end-to-end functionality in less than 2 hours post-release, allowing for quicker error resolution.
3. Improved testing practices With Qyrus, the challenger bank enabled data-driven testing through parameterization for the first time. They not only optimized organization and maintenance through Qyrus action types but also helped testers automate tests effortlessly. For instance, the bank’s testers developed 8 automated tests that would get triggered and executed immediately after the build.
The Impact This case study is a timely example of how neobanks can successfully validate the functionality of its software applications with Qyrus, no matter their budget constraints. For the social banking startup, in this case study, the subscription with Qyrus translated to:
~50% decrease in test build time through cloning
1500 total executions
Zero bugs leaked into QA & production
In 10 weeks of subscribing to Qyrus, the Neobank startup, achieved 90% test coverage across mobile, APIs, and end-to-end scenarios using two resources. Besides that, the bank successfully managed to scale its testing efforts across various platforms, despite its budget, and offer its customers a high-quality social banking experience.
Topic:Role of Test Data Management in Modern Software Testing Date: 2nd November 2023 Time: 12 PM, Eastern Time
In-time availability of accurate test data amps up the efficiency of automated testing cycles. A comprehensive Test Data Management assumes top-shelf priority at this point.
Test Data Management empowers QA professionals to leverage consolidated test data from a single location. This “set it and forget it” approach delivers advantages on fronts like test coverage, build times, and execution.
QA teams gain significant management and governance benefits with a full-fledged test data strategy. Irrespective of whether the external source is an Excel file, API call, or a database, new-age test data management ensures seamless access to the right data every time.
Frameworks like Qyrus also facilitate synthetic data generation within the test data management system itself. This eliminates the need to rely on fragmented third-party data generation tools.
Join this Lunch and Learn Web Series to learn more about ‘The Role of Test Data Management in Modern Software Testing.’
Scheduled for the 2nd of November 2023 at 12 PM Eastern Time, this 15-minute Webinar will help you discover how you can utilize test data management best practices to significantly improve software quality.
This webinar will cover:
Introduction to Test Data Management Tools
Snapshot of how to explore data sources such as database queries and API calls
How to leverage data tables for efficient data-driven testing within the Qyrus framework
Speaker: Timothy Miller, Platform Expert and Senior Consultant, Qyrus Speaker Bio: Tim Miller is a Platform Expert and Senior Consultant for Qyrus. He is a professional in the field of automated software testing and quality engineering. Tim has developed a deep understanding of various testing methodologies and frameworks. His passion for quality engineering is evident in his meticulous attention to detail and his commitment to delivering robust and reliable software. With a strong analytical mindset, Tim excels in identifying potential defects and vulnerabilities in complex software systems.
Step into the world of test reusability with Qyrus’ innovative approach, as presented by Jorell and Kiwaun. Qyrus’ arsenal of features empowers users to make tests reusable, whether it’s through importing Selenium tests or the intuitive embedding and cloning of test scripts. They also explore the seamless export and import capabilities within the platform. Join us in understanding the broader implications of reusability within the testing landscape and how it aids testers, developers, and business technologists.
Tell us more about Qyrus’ ability to make tests reusable.
Jorell: Qyrus has multiple ways that tests can be made reusable. We have options to import Selenium tests onto our platform, as well as the ability to clone test scripts on the Qyrus platform itself. We can embed test scripts within other test scripts and even flag test scripts for end-to-end business process testing, or what we like to call Component testing.
Kiwaun: Qyrus can also export its scripts. That being said, if a script exists in one project or team on Qyrus, it can be quickly moved over to another project or team by exporting. Then, these tests can just be imported quickly back onto the platform.
What is the overall impact that “reusability” has on the testing process?
Jorell: Making scripts reusable is important because it cuts down on the amount of time that it takes for a team to complete certain tasks. Having redundant work is never good.
Kiwaun: Cutting down on time obviously saves money and resources in general, allowing these testers to focus more on what matters… testing. In that way, they can move on to create or build more scripts, thus increasing test coverage. And the awesome thing is how simple it is to move tests around and make them reusable on Qyrus. It’s not like we’re copying and pasting large amounts of code from one file to the next, hoping things will work.
How might this help testers, developers, and business technologists?
Kiwaun: More business-oriented users would find making these tests reusable very simple. Again, no coding is involved. As a matter of fact, you don’t have to look at one single line of code to do these various tasks. If a business technologist wanted to export and import tests themselves, it’s no different from downloading and uploading files to the internet. We all have experience in this!
Jorell: Exactly! This is also a benefit to testers and developers. It helps them get work done in a much timelier manner. Testers can work more collaboratively, and share test scripts, and ideas on how to overall test more effectively.
Does the same or similar functionality exist without Qyrus, and how do competitors address similar problems?
Kiwaun: Other companies and competitors definitely have the capability to make their tests reusable within their own platforms, but the process and the steps in which to do so can often be convoluted or confusing. Qyrus’ simplistic UI seeks to make testing easier in every aspect. Doing something simple like making tests reusable or embedding tests within each other should not be something that requires a large amount of research or knowledge of the platform to do. At most, a quick trip to the documentation should suffice.
How do you see reusability impacting day-to-day operations across organizations?
Jorell: Their day-to-day would get easier, as embedding test scripts reduces the time required to build out certain scenarios and cases. For example, a tester can build out a common set of steps that might be found in many scenarios and then go on to share that with his colleagues to embed within other scripts for simplicity.
Kiwaun: Then, if something requires a change or the script requires maintenance, there is only one point of change. So, let’s say we have to add, edit, or remove a step, we can do that in our one script and have that reflected across every other script it’s embedded within.
In conclusion, the ability to create reusable tests offered by Qyrus represents a significant leap forward in enhancing the efficiency and productivity of testing teams. The reduction of redundant work not only saves time but also conserves valuable resources. This streamlined approach allows testers to focus on what truly matters – thorough testing. The simplicity of moving tests within Qyrus, without the need for complex coding, empowers business technologists to actively participate in the testing process. Testers and developers benefit from collaborative efforts, ensuring quicker test script creation and, ultimately, expanded test coverage. With Qyrus, test reusability becomes a cornerstone of effective testing.
Explore the evolution from API to database testing with the latest feature enhancements brought to you by Qyrus. Brett and Joyal take us on a journey through the expanded API testing landscape, shedding light on the integration of database testing and validations. This feature bridges the gap between APIs and databases, ensuring data accuracy and integrity in your applications. From supporting additional database types to asserting lambda functions, Qyrus’ updates enhance the versatility of API to DB testing. Let’s delve deeper into the profound impact this feature promises to have on your testing processes.
Tell us more about the expanded API to database testing features.
Brett: API testing, for those not aware, also includes database testing and validations that can be made on those tests. Essentially, it takes some API call that might do something like post data, and then it makes a database query to see whether or not the data was entered correctly into the database.
Joyal: The updates include expanded support for other types such as Snowflake, Netezza, DynamoDB, and DB2. But beyond that, we also have the capability to assert lambda functions, as well. This increases the overall versatility of API to DB testing.
What is the overall impact on the testing process this feature might have?
Brett: API testing involves a higher level of technicality compared to evaluations of web and mobile applications. It’s susceptible to failures, primarily due to improper test setup. Therefore, we’ve made a concerted effort to simplify the required configurations in this testing domain. Additionally, we’re committed to offering users clear feedback and visual aids to streamline the test creation process. For instance, our JSON tree mapping tool provides a graphical representation of the API’s request body, allowing users to interactively select the desired node and extract the necessary JSON path for database mapping.
Joyal: Furthermore, this approach presents a solution to several issues by ensuring the correct functionality of both post-API execution logic and the API itself within a single test. In essence, it enables the testing of two distinct entities using a unified test case.
How might these updates help testers, developers, and business technologists? What value can this feature bring?
Brett: That’s an excellent question. Typically, testers initiate the API testing process with functional testing to validate that the API is performing as intended. They establish suitable assertions within their functional tests to confirm that the API exhibits the desired behavior. Once they are confident that the API behaves correctly, they proceed to set up database assertions to verify the accurate storage of data within their database. This approach helps testers ensure seamless communication between their APIs and databases.
Joyal: Developers can leverage this approach to ensure the proper functioning of the API itself and validate the correctness of post-API execution logic. Additionally, it allows for the validation of the final output stored in the database, ensuring that the database functions as expected. Developers can incorporate these test executions into their development sprints and continuous integration (CI) pipelines to maintain data processing integrity with each new software build.
Brett: This feature offers robust reporting capabilities and user-friendly assertion creation, making it an excellent tool for business technologists and analysts seeking deeper insights into their application’s inner workings. Following the data transfer and storage processes is made straightforward with comprehensive reporting, and collaboration is facilitated with options for shared reporting. Furthermore, the codeless approach empowers non-technical specialists to even create test scripts, ensuring synchronization and functionality between the application and the database.
Does the same or similar functionality exist without Qyrus, and how do competitors address similar problems?
Brett: Well, the tester can call their API from a tool like Postman, then navigate inside the database to make sure the expected data was input successfully. In the case of lambda, the tester would need to check the logs and review that the expected data was sent over to the lambda.
Joyal: And in terms of competition, the API-to-DB functionality allows the users to test both the API and DB at the same time. Competitors do not have the same capability. We have not seen any competitors that can assert lambdas with their functional API tests.
How do you see this feature impacting day-to-day operations across organizations?
Joyal: Well, a user doesn’t need to write any code to test databases or lambdas, and they can be tested at the exact same time, as we just stated. With Qyrus, anyone can make these tests. You don’t need a deep understanding or knowledge of coding or testing frameworks to achieve this level of testing.
In conclusion, Qyrus’ expanded API to database testing features represents a significant leap forward in ensuring the reliability and functionality of your applications. Testers will benefit from simplified configurations and enhanced feedback, making the testing process smoother and more efficient. Developers gain the ability to validate API functionality and data storage simultaneously, seamlessly integrating testing into their development workflows. Moreover, this feature empowers business technologists with comprehensive reporting and codeless test script creation, democratizing the testing process across organizations. With Qyrus, the future of API and database testing is here, accessible to all.
Across the world, 25% of mobile apps are forgotten by users after the first use. In these cases, a subpar user experience (UX) is often the culprit. This can be due to application bugs, slow performance, complex interfaces, or crashes. Such abandonment impacts user retention, transaction fulfillment, and overall brand value.
Chartbuster mobile apps usually have a unique trait that contributes to their success. In all these mobile apps, the USP is a great user experience that goes beyond just fluid navigation.
Outstanding user experiences are all about familiar experiences along with seamless fulfillment of services and transactions. Aspects like application performance, personalization, and user accessibility also contribute significantly to these interactions. This is where comprehensive mobile application testing becomes imperative to improve UX.
Here are four mobile UX testing best practices to ensure an outstanding end-to-end user experience.
Best practice #1
Automate testing across the mobile app lifecycle Faster time to market is a non-negotiable for mobile apps. The resulting QA challenges can detrimentally affect end-to-end user experiences. Automation of mobile app testing is an ideal way out of this catch-22 situation.
Mobile app test automation accelerates go-to-market cycles. It increases test coverage and ensures continuous mobile app UX improvements. These testing solutions also reduce bugs and overall risk, which contributes to the creation of outstanding user experiences.
New-age software testing platforms reduce complexities in mobile application testing with codeless interfaces, AI, and machine learning (ML). Benefits like elevated levels of automation and test script reuse accompany the use of these platforms.
The usage of features like test step recording in mobile testing solutions exponentially scale up automation. These make it easier to automate and customize complex tests for reuse. For example, Qyrus’ Mobile Recorder feature effortlessly captures and converts user interactions into test steps. This is complemented by intuitive form-led test step creation that boosts mobile app testing efficiency.
Higher levels of test intelligence are now achievable due to the integration of AI in mobile app testing services. These can be beneficial to ensure outstanding end-to-end user experiences. AI accelerates the detection and classification of errors. It accurately detects false negatives and true positives that affect UX testing outcomes.
Best practice #2
Mitigate bugs proactively with black-box testing The powerful combination of AI and ML paves the way for advanced user experience testing options like exploratory testing. For instance, reliance on black-box mobile UX testing tools that utilize AI and ML is ideal for unsupervised functional testing of user interfaces.
Today’s innovative black-box mobile app testing tools reduce the need for expert testers. QA teams can ensure considerable time, cost, and man-hour savings with such UX automation testing tools.
The use of AI and ML-backed black-box solutions for mobile user experience testing also delivers benefits like:
Faster and stable mobile app UI testing
Maximization of test and state coverage
Automatic input generation
Intelligent test execution
In-depth insights into user behavior
Utilization of production data to create new tests
To take a case in point, Qyrus Rover is an end-to-end, fully autonomous mobile app testing solution powered by AI and ML. Designed for DevOps and QA teams, Qyrus Rover visually maps user journeys to identify traffic patterns and UI issues. Integration of reinforcement learning ensures the automatic creation of optimal test steps for every use case.
Mobile UX testing tools like Qyrus Rover can create a flip-book of clicks or use dynamic locators within a mobile app’s interface for faster test execution. Or it can be used for mapping of navigation flows to create new tests. In addition, Qyrus Rover’s seamless integration with test environments translates to stable tests and quicker bug fixes.
Best practice #3
Bank on the power of self-healing tests Frequent update cycles mean that mobile apps are in a state of constant flux. Due to this, flakiness, brittleness, and fragmentation create constant mobile app testing bottlenecks. The use of AI for self-healing tests can be handy to improve UX in such test environments.
A case in point is a mobile app test’s failure due to changes in an element’s ID value. In such cases, AI ensures automatic updates of the element’s locator values to mitigate test flakiness and brittleness. This eliminates the need for manual test script reviews, ID changes, and rebuilds.
Self-healing tests intelligently optimize the efforts, time, and costs that go into mobile UX testing. This results in smarter and quicker tests that evolve automatically with the dynamic changes of app components.
For example, Qyrus’ Healer AI tool integrates robust self-healing capabilities for mobile user experience testing. It factors in every change without any effect on mobile app test automation. All this is possible with the need for prior training on the mobile application.
Qyrus Healer ensures AI-enabled script correction with more than 99.9% certainty. This means no more “object not found errors” or manual searches for the correct locator value. Tests can recover in a matter of microseconds in case of failures.
Best practice #4
Utilize device farms for real-world UX simulations When it comes to great user experiences, there is no substitute for testing on actual mobile devices. This is why QA teams increasingly rely on device farms as their test infrastructure of choice.
From a mobile UX testing context, device farms are ready-made test beds that consist of actual mobile devices. Device farms offer a wide variety of mobile app testing options in terms of operating systems, browsers, and highly customizable network configurations. This ensures that testers can ensure optimal UX despite issues like mobile device fragmentation, screen resolutions, application types (native or hybrid), or upgrade cycles.
Available as cloud-based services, extensive simulation capabilities, and highly secure infrastructure are the inherent strengths of device farms. These services eliminate the cost and management complexity associated with self-owned test device infrastructure.
AI augmentation is a standard feature in next-gen device farms like Qyrus’ Device Infrastructure. This service’s highlights include a highly scalable and low-latency mobile device farm with guaranteed 99.9% availability.
AI-augmented UX automation testing tools like Rover and real-time dashboards are part of Qyrus Device Infrastructure. The toolkit also includes in-depth test script optimization options with network throttling, biometrics (beta), SDK, and CI functionalities.
Qyrus Device Infrastructure offers mobile app testers instant access to Android, Windows, and iOS devices using Qyrus’ codeless test environment creation approach. The highly secure ISO 27001 and SOC 2 compliant device farm from Qyrus allows testers to optimize mobile UX testing on the fly. Easy-to-use management features ensure rapid on-demand deployment of device labs based on business demands.
Enter the realm of cutting-edge web application testing with Qyrus’ ChatGPT plugin, a transformative tool driven by the power of AI. This groundbreaking tool leverages advanced AI to redefine the testing landscape, offering a seamless experience from test creation to execution. It empowers testers, developers, and business technologists to navigate the complexities of web application testing effortlessly. Join us as we delve deeper into the immense potential and transformative capabilities of this game-changing plugin.
Tell us more about the ChatGPT plugin offered by Qyrus and its use cases.
Dan: Qyrus has made its first ChatGPT plugin that works for testing. The plugin can build, create and execute test scenarios by simply providing a URL to your web application.
Linto: The ChatGPT plugin is for web application testing specifically. It helps the user to quickly build tests by analyzing the web application’s structure and behavior. It then can do things like suggest new scenarios for the user to build upon. Then, it can run all of those with the Qyrus test engine.
What is the ChatGPT plugin’s overall impact on the testing process?
Dan: Overall, the plugin aids in every step of the testing process. This includes the initial phases of testing, which include identifying scenarios and cases that can be automated and stretching through the building and creation of the scripts all the way to the execution and reporting of said scripts.
Linto: And given that it helps along every step of the way, it provides a good amount of effort reduction when it comes to testing in general. Because the tool helps to identify new or previously undiscovered test scenarios, it can help improve test coverage. And, given how much assistance it provides, the cost-benefit of using a tool like this is apparent.
How might this feature help testers, developers, and business technologists? What value can this feature bring?
Linto: The plugin can help build a good portion of the testing process for the tester, giving them more time to work on refining the test coverage. This allows the tester to focus on the special cases and scenarios where the tester’s skills really shine.
Dan: A developer can use this to quickly create test cases for new features they may be working on. This gives the developer more time to refine their work. Since the plugin also executes the tests on the Qyrus engine, the developer does not have to worry about any kind of environment setup for testing. They get instant feedback without having to set anything up.
Linto: And lastly, the plugin gives the business technologist insight into the testing process. By simply needing a URL, the plugin guides the business technologist through the testing process, teaching the business technologist as they go along. The business technologist doesn’t need to know much about the inner workings of their product to help build effective tests. The plugin handles that for them.
Does the same or similar functionality exist without Qyrus, and how do competitors address similar problems?
Linto: This is the first LLM-powered testing solution. We are one of the first testing platforms to use generative AI in the testing process and include it in every step of the testing process.
How do you see this plugin impacting day-to-day operations across organizations?
Dan: It removes a large chunk of the test-building process such as testers don’t need to find locators for specific elements on the webpage, testers do not need to build common test cases, as the plugin knows how to build these, and the plugin provides instant feedback for the tester as it builds and executes the tests.
Linto: Additionally, there will be less boilerplate tests. You don’t need a high level of skill to build effective and proficient tests. On top of that, no environment setup is required and there is significantly less navigation required throughout the building process.
In conclusion, the ChatGPT plugin from Qyrus represents a monumental leap in web application testing. Its AI-driven features not only simplify the testing process, but also significantly enhance efficiency and accuracy. Testers can create and execute scenarios with ease, developers can quickly generate test cases, and business technologists gain valuable insights, all within a unified platform. Qyrus continues to lead the industry with innovative solutions that are set to revolutionize the way organizations approach web application testing, making it more accessible and effective than ever before.
When: October 22nd – October 25th, 2023 Where: The Venetian, Las Vegas #Money20/20
Are you ready to discover how Qyrus has played a pivotal role in the success stories of Shawbrook? Our codeless, automated solution unlocked a new era of testing mastery – accelerating testing, expanding coverage, and enhancing application quality.
The Qyrus team is participating in Money 20/20, USA, and we can’t wait to meet you, share our vision, and explore how we can shape the future together at this premier global event. It serves as a convergence of industry leaders, start-ups, entrepreneurs, and professionals actively shaping the future of payments, fintech, and banking.
“Qyrus Web testing enables our agile development teams to speed up release cycles by increasing the quality of our testing through automation. This helps deliver our core savings and lending platform changes on time, through a substantial reduction of defects and rework.”
Chief Technology Officer, A Leading UK Challenger Bank
Qyrus is here to empower your vision, accelerate your success, and reshape the way you approach test automation with our AI-enabled automated testing platform. With excitement and anticipation, we look forward to meeting you at Money 20/20, USA!
Topic: End-to-end Business Process Testing using Qyrus Date: September 28th, 2023 Time: 12 PM Eastern Time
Consistent user experiences across channels are non-negotiable in today’s businesses. Traditional functionality tests often falter when the business demands an omnichannel functionality assessment. Automation of component tests emerges as the only solution at this point.
So, what is component testing, also known as end-to-end business process testing?
Existing business process test techniques tend to focus on siloed aspects like Web, mobile, or APIs. Component testing tools like Qyrus differ on this front with their entire business process coverage features.
The Qyrus platform guarantees optimal customer journeys with its end-to-end business process testing philosophy. With Qyrus, QA teams are not dependent on point solutions, complicated configurations, or custom code to test business process functionality. It also equips QA professionals with powerful features to reuse existing tests.
Extract the power of holistic test scripts that cover an entire business process with Qyrus’ component testing features. QA teams can connect and chain Web, mobile, and API test scripts to operate as a single script. These business process testing tools are ideal for functionality evaluations that span the entire cycle.
This Webinar will help you understand:
What is component testing and its role in a business process test?
How to ensure end-to-end business process testing and functionality
Techniques to reuse test scripts and create highly customized component tests
Business process testing tools that consolidate Web, mobile, and API test scripts
Speaker: Timothy Miller Platform Expert and Senior Consultant, Qyrus
Speaker Bio: Tim Miller is a Platform Expert and Senior Consultant for Qyrus. He is a professional in the field of automated software testing and quality engineering. Tim has developed a deep understanding of various testing methodologies and frameworks. His passion for quality engineering is evident in his meticulous attention to detail and his commitment to delivering robust and reliable software. With a strong analytical mindset, Tim excels in identifying potential defects and vulnerabilities in complex software systems.
Get ready for an enlightening Feature Friday, as we unveil Qyrus’ cutting-edge solution – the API Discovery Recorder. This AI-powered marvel promises to transform the landscape of API testing. Join us as we journey through the key features and advantages of this tool, and discover how it empowers testers, developers, and business technologists to achieve comprehensive and efficient API testing without the complexity of traditional methods.
Tell us more about the API Discovery Recorder offered by Qyrus and its use cases.
Dan: The API Discovery Recorder is a generative, AI-powered extension that tracks APIs that can be critical to the functionality of your web application. It helps the user quickly build API tests and generate assertions by simply browsing the web application locally on your machine.
Linto: The recorder has the ability to filter APIs that are not directly related to the functionality of your web app. That way, it doesn’t create test scripts and assertions that don’t make any sense or are not needed. Users can directly import these API tests that were generated directly to the Qyrus platform for further testing in the API testing service.
Dan: Furthermore, the recorder is super easy to use. A non-technical user can fire up the recorder and just as easily import these tests directly into the platform, and also without requiring documentation on the APIs under test. Of our various core services, API comes off as the most technical and difficult for non-technical users to understand and get started with. Now, that is an issue no longer.
What is the recorder’s overall impact on the testing process?
Dan: The recorder takes the test building and creation part of the testing process and expedites it. That way, users can create more API tests at a faster rate and without as much work put into creating assertions for the actual test. Qyrus handles all of that for the user. And, the user can always go into the test themselves and edit as they see fit.
Linto: And with users being able to churn out more test scripts, that means testers can focus on increasing test coverage where needed and even expanding into other areas of their application to automate testing.
How might this feature help testers, developers, and business technologists? What value can this feature bring?
Linto: A tester could quickly and exhaustively generate API assertions to improve both test coverage and the speed of their API test-building process. And a developer could find use in this tool to quickly test their APIs as they build them. The more you test, the more bugs you catch, and a developer would be able to very easily perform this testing without having to dedicate time to actually building out the script themselves beyond the basic functionality of the API test. This is part of that “shift left” mentality that is often mentioned in development and testing.
Dan: Furthermore, a business technologist or business-oriented user would be able to build out tests and indeed an entire test suite themselves. And that’s all with zero knowledge of the functionality of the APIs. The generative AI nature of the tool even helps to create descriptions for the API calls, taking even more load off of the user’s hands. That way, business users could also get an idea of what certain APIs are doing.
Does the same or similar functionality exist without Qyrus, and how do competitors address similar problems?
Dan: Currently, there are only a handful of tools out there that are developing generative AI-powered tools for API testing. One of the things that stands out in our tool is that it can generate assertions for the API and not just the skeleton of the test itself. By working with the Qyrus API Testing service, API process tests or chaining tests can be quickly built out, as well.
Linto: Many API testing solutions still involve a bit of coding, or at least the knowledge of it. Even the “low-code” solutions require an understanding of code snippets or basic JavaScript in order to create assertions on the API. At roughly the same time that a tester can write two assertions using other methods, the API Discovery Recorder is able to generate between ten to twenty. These can then be directly imported onto Qyrus where the tester can leverage all of the advantages of a cloud-native environment.
How do you see this feature impacting day-to-day operations across organizations?
Linto: Not only does this tool make building solid API test scripts easier, it makes it more accessible to completely non-technical users, as well. As we just mentioned, you can generate ten to twenty assertions in the time it takes a user to make two using traditional testing methods.
Dan: The API Discovery Recorder’s ability to filter out non-functional APIs, in addition to its ability to be plugged into Qyrus’s API process testing, are two stellar features that bring a smart testing mindset to API testing. Another important “smart” feature is the ability to generate easy-to-understand descriptions that make it easy for non-technical users to comprehend what is going on in the background of their web application.
In wrapping up this Feature Friday, we’ve explored the transformative power of Qyrus’ API Discovery Recorder. With its generative AI features, smart assertion generation, and user-friendly interface, this tool is poised to redefine how API testing is conducted. As organizations embrace this innovation, they open doors to faster, more comprehensive testing, boosting efficiency and ensuring the reliability of their applications. Qyrus continues to lead the way, providing solutions that revolutionize the testing landscape.
Welcome to this week’s Feature Friday, where we embark on an extraordinary journey into the realm of mobile testing with Qyrus. Imagine stepping into the enchanted world of testing, armed with a mystical compass that leads you to the perfect device for your test executions. Today, we are thrilled to explore the remarkable “First Available Device” feature that revolutionizes how testers and developers execute their tests. Choosing the right device from an extensive pool can be akin to navigating a labyrinth of choices. This is where the “First Available Device” feature comes to the rescue, like a guiding compass, pointing testers in the direction of optimal test executions. Join us as Jorell Socorro and Amairani Lopez shed light on this game-changing capability and its impact on mobile testing.
Tell us more about the First Available Device offered by Qyrus and its use cases.
Jorell: The “First Available Device” feature on Qyrus is a true game-changer for mobile testing. It allows testers and developers to select and utilize the first available real mobile device for their test executions. Gone are the days of setting up dedicated device pools for each test, as this feature streamlines the testing process and ensures faster test executions without waiting for device allocation.
Amy: Absolutely, Jorell! With AI integration, Qyrus intelligently suggests the best device for testing at any given moment, ensuring optimal device utilization and enhancing testing efficiency and accuracy. Testers and developers can readily view all available devices, making informed decisions on device selection for their test runs.
What is First Available Device overall impact on the testing process?
Jorell: The impact is significant, Amy. By eliminating the need to create device pools for every test, testers can directly choose the first available device, saving valuable time and effort. This feature optimizes the testing workflow, resulting in faster test executions and increased productivity.
Amy: Indeed, the convenience and efficiency it brings are unparalleled. Testers can quickly proceed with their test scripts without worrying about device availability, making the entire testing process seamless and hassle-free.
How might First Available Device help testers, developers, and business technologists? What value can this feature bring?
Jorell: For testers, the feature ensures faster test executions, as they can immediately run tests on available devices without any delays. This reduces idle time and improves testing efficiency.
Amy: Developers can also benefit from this capability by easily accessing available devices when they need to perform ad-hoc tests or troubleshoot issues on specific devices. It streamlines their testing and debugging process, enabling quicker feedback and resolution.
Does the same or similar functionality exist without Qyrus, and how do competitors address similar problems?
Jorell: While some testing platforms offer device pooling options, the “First Available Device” feature is unique to Qyrus. Many competitors do not provide the convenience of directly choosing the first available device for test executions, which sets Qyrus apart.
Amy: The simplicity and efficiency of this feature make Qyrus stand out in the market, providing a seamless and optimized testing experience that is hard to match.
How do you see First Available Device impacting day-to-day operations across organizations?
Jorell: This feature will streamline and expedite mobile testing in various organizations. Testers and developers will no longer need to worry about device allocation, and they can focus on testing and improving the software quality.
Amy: Additionally, the AI-driven suggestions for device selection will lead to better testing outcomes and faster feedback loops, enhancing the overall software development process.
What other features complement the “First Available Device” capability, and how do they work together to create a robust testing environment?
Jorell: Qyrus’s low code no code platform and the Component service are excellent complements to the “First Available Device” feature. Testers can build and reuse tests across web, mobility, API, and desktop applications, making test creation and execution even more efficient.
Amy: With Qyrus’s infrastructure testing capabilities, users can execute tests at lightning speed in parallel on real mobile devices, adding to the agility and scalability of mobile testing. This seamless integration provides a complete and powerful testing environment.
The “First Available Device” feature in Qyrus is a testament to the platform’s commitment to innovation and efficiency in mobile testing. The cumbersome task of setting up device pools for each test is replaced with a seamless experience, where testers can focus on refining their scripts and accelerating their testing schedules. By streamlining device selection and utilization, this feature empowers testers and developers to deliver high-quality software at an accelerated pace.
Thank you, Jorell and Amy, for sharing your insights on this remarkable feature! Stay tuned for more exciting innovations in the world of software testing. Happy testing!
Kumar Vivek
Development
Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim.
