Hello, testing aficionados! It’s Feature Friday, and we’ve got a treat for you that’s sweeter than a double-chocolate fudge sundae. Parth and Milton are about to uncover the magic behind our email reporting updates. Imagine getting your test results delivered straight to your digital doorstep, neatly packed, and ready to share with your fellow testers. It’s like a testing picnic, and you’re the one bringing the potato salad!
Tell us more about our updates to our email reporting capabilities!
Parth: Some of our updates include more details of the test in the email report itself, so users can directly send these reports to others on their team. Users can now also download reports directly from the email, something we couldn’t do before.
Milton: On top of that, we all know how much people love PDFs! Especially when it comes to providing reports and analytics, it’s just better to consume with. Well, now users can directly view the PDF version of the report via email. These kinds of updates help users quickly share test results with teammates and collaborate more effectively.
What is the overall impact on the testing process these updates might bring?
Parth: Qyrus aims to make the entire testing process more collaborative. Instead of having testers in their own little silos, we can have them communicate and work together more effectively. And these updates are just one way that Qyrus aims to do so.
Milton: Reporting and analytics are definitely a strong aspect of Qyrus. With continuous updates to how we provide data and analytics, we are constantly trying to improve the reporting aspect of the testing process.
How might these updates help testers, developers, and business technologists? What value can this feature bring?
Milton: Testers can directly send these reports as soon as their test finishes to other members, and in turn, those members will receive all details of the execution directly to their email. Developers can be more in tune with the testing process and receive direct reports on bugs that show up in the application.
Parth: Business-oriented users can receive all this information as well but in an easy-to-consume format.
Qyrus aims to make testing more accessible to non-technical individuals, so they can easily interpret what’s going on in their testing ecosystem.
Does the same or similar functionality exist without Qyrus, and how do competitors address similar problems?
Milton: Building up such a robust reporting and analytics system would take a lot of development time for any individual testing team. All of this is already built out on the Qyrus platform and ready for anyone to use at the click of a button.
Parth: And we would say that we offer more robust reporting and analytics to the end user when compared to our competitors.
How do you see these updates impacting day-to-day operations across organizations?
Parth: Well, instead of triggering tests manually, testers can schedule their tests and have the email of the test reports directly sent to anyone on their team.
Milton: They don’t have to build an email report themselves. Qyrus automatically builds it for them, saving them a lot of time. Recipients of these email reports will know all the details of the application directly from the email without having to login to Qyrus.
So, dear Qyrus users, it’s time to embrace these sizzling updates! Sending reports has never been this easy, like tossing a Frisbee on a sunny day. Testers, developers, and business technologists can collaborate effortlessly, and non-tech folks can dive into reports without breaking a sweat. And here’s the cherry on top – we’ve baked in more robust reporting and analytics than your grandma’s secret cookie recipe! So, hop on board with these updates, and let’s make testing a walk in the park!
Global Banks are at risk of losing one in five (20%) of their customers due to poor customer experience, according to 10X banking. This is particularly relevant for mega retail banks, which can’t afford to jeopardize their customer base due to lackluster web and mobile app interactions.
With over 4,500 employees, our client is a retail bank with over 290 branches and a trusted customer brand that offers full-service banking to more than five million customers. They operate on a modern banking platform and serve customers through digital channels, native IOS and Android applications, and in branches across the UK offering personal and business banking options with 1.33 billion in revenue.
That said, they recognized the pitfalls of manual testing—resulting in strained resources, sluggish release cycles, underwhelming web and mobile app performance, and subsequent revenue loss—one retail bank embarked on a mission to overhaul its full-service banking through digital banking testing infrastructure. Their goal? Delivering unmatched user experiences.
The Problems In the context of this banking case study example, the bank sought to establish a dedicated process aimed at improving customer experience across their web and mobile applications. In the process, they encountered obstacles such as:
Inefficient manual testing The manual testing infrastructure led to redundancies in testing, with testers having to re-write test scripts, choking their bandwidth and as a result bottlenecks in product release cycles. The outcome? Inefficient testing, complex bug detection, and resolution.
Additionally, the manual approach impeded the creation of automated CI/CD pipelines, given its inherent requirement for manual intervention.
Direct loss of customers due to inferior apps With inefficient testing came substandard applications, resulting in a less-than-optimal user experience. This directly impacted the bank’s business with a noticeable loss of customers and revenue.
In an effort to put an end to losing customers to competition, the retail bank turned to Qyrus to completely automate its testing framework. The next section of this banking case study example highlights how Qyrus helped achieve this and the magnitude of the transformation.
The Solutions The bank was able to ramp up speed to market by automation resulting in the expansion of test coverage using Qyrus’ testing solutions. End result was a consistent customer experience across its full-service banking infrastructure. Here’s how:
The transition from full manual to automated testing Qyrus prioritized application testing, starting with automated test scripts for mobile and web. Employing cloud-hosted reports featuring step-by-step screenshots and videos of test executions, a foundation for robust, data-driven reporting was established.
The endeavor resulted in a substantial increase in the scale of testing with the bank achieving more than 2,500 automated test executions each week, coupled with over 10,000 manual and object spy sessions per week.
Comprehensive test coverage With Qyrus’ automation came expanded test coverage – from web and mobile to API and end-to-end customer journey test cases. As a consequence, testers could repurpose test scripts, eliminating the need to create scripts anew for scenarios ranging from logging in to verifying balances and other transactions. For perspective, the bank accomplished a test coverage rating of 90%, wherein 100% of the tests generated were automated and reusable.
Leveraging Qyrus’ diverse device farm, the retail bank scaled testing from 30 to over 50 real devices, spanning Android and Apple tablets and mobiles, as well as various browsers (Chrome, FF, Edge, Safari, etc.) and operating systems (Windows, Linux, Mac).
Improved testing and QA through collaboration Qyrus’ testing solution made test sharing among cross-functional teams a breeze with as many as 50 testers, developers, and analysts building automated tests. Furthermore, test de-bugging was simplified owing to live test executions on the web and mobile.
Qyrus’ solution also enabled direct issue logging in Jira,profiling performance metrics for gauging system responsiveness, and visual regression for preventing unintended visual discrepancies across different software builds. All this meant efficient testing, fewer release delays, and faster bug-free releases.
The Impact The retail bank’s success story in this banking case study example exemplifies how testing automation can translate to an unparalleled customer experience, the outcome translated to:
2,500+ automated executions per week
10,000+ manual and object spy sessions per week
90% test case coverage (Web and Mobile)
Expanded usage from 30 to more than 50 devices
Conclusion The banking sector is recognized for its customer-centric approach, and this principle applies equally to digital banking. Battling with the challenges in manual testing and subpar user experiences, the bank benefited from Qyrus’ scalable and secure testing automation solution. The outcome? A remarkable 90% test coverage streamlined operations across web and mobile platforms, and ultimately elevated customer experience to a class of its own.
Ladies and gentlemen, boys and girls, it’s Feature Friday, and we’ve got a story of partnership that’s sweeter than a scoop of vanilla ice cream on a warm summer day. Today, Suraj and Brett are here to tell us about the incredible collaboration between Qyrus and Quinnox, a duo that’s more dynamic than Batman and Robin, more harmonious than a symphony orchestra, and more unstoppable than a freight train with rocket boosters!
Tell us a little bit more about Qyrus and its parent company, Quinnox.
Suraj: So, Qyrus as a platform was developed by Quinnox, a professional services company with over twenty years of testing experience. As a result, we always have on-hand service members to help clients with testing needs.
Brett: Generally speaking, anytime there is not enough bandwidth in terms of testers required at a project level, clients always have the option to engage our services team to help them test a given application, feature, or release. Furthermore, in terms of migrating test cases onto Qyrus, there is a lot of value in having cases in Qyrus. And though there are import options, for large-scale or complex migrations a dedicated services team comes in quite handy.
Utilizing both Qyrus as a testing platform and Quinnox, what would be the overall impact on the testing process?
Suraj: Well, as Brett described, Quinnox can step in and be a game changer when it comes to larger releases when testing bandwidth becomes a commodity. In general, you can see a reduction of effort from your team’s side as work is offloaded to a professional team with unmatched expertise on the Qyrus platform.
How might this duo help both technical and non-technical users? What value can it bring?
Brett: Well, testers have the ability to give clear outlines on high-volume test scenarios and then have a team of trained members on hand to ensure test coverage overall.
Suraj: On top of that, our service members, all trained professionals, are able to effectively assist the entire process with close attention to detail. That way, business-oriented users can ensure that the high-volume features and functionalities of their applications are met within testing requirements. This allows them to identify and communicate issues without burdening them with detailed test case generation, infrastructure, or other taxing QA requirements.
Does the same or similar functionality exist without Qyrus, and how do competitors address similar problems?
Suraj: Other competitors do not have dedicated service teams, which means customers would have to engage a third party. This causes a range of problems, especially when these third-party testers do not know the platform by hand. It minimizes productivity as the new testers have to get up to speed with not only the testing that is required but also the platform on which they are testing.
Brett: Furthermore, without full product knowledge, they may not be getting full efficiency from the platform with which they are testing. This means inefficiency from the testers and the platform. This is all mitigated as Qyrus has a services team which are already experts on the solution.
How do you see this dynamic duo impacting day-to-day operations across organizations?
Brett: It offloads the burden of maximizing coverage and ensuring functionality. With large-scale releases or steadfast testing requirements, having the ability to call a team of testing experts who are already aligned with the Qyrus testing platform truly maximizes efficiency. Furthermore, being able to scale up and down with services as required gives the freedom required to ensure proper QA lifecycles.
Folks, it’s a match made in testing heaven! Qyrus and Quinnox are the ultimate tag team that can make your testing process a walk in the park, even if that park happens to be a jungle of complex applications. Whether you’re a tech wizard or a business guru, this power duo can simplify your testing journey. Say goodbye to testing headaches and hello to a brighter, more efficient testing future. Join us next Feature Friday as we keep unveiling the secrets of testing success!
Developing new banking products quickly while offering best-in-class service is difficult for most banks in the UK, given there’s no dearth of competitors and there’s a surge in demanding customers. Needless to say, banks have to struggle harder to retain their customer base in the UK.
One Yobota survey revealed that 77% of UK banks and financial services firms surveyed began to engage with new customer segments in recent years. Moreover, 80% of them were regularly seeking feedback from customers, and 71% were already implementing them by introducing new products. While many others are focused on modernizing their digital channels since over 50% of the UK population is expected to use mobile phone banking services by 2026.
Improving the customer experience significantly while introducing new products is even harder for specialist banks with lower budgets, given the higher web application development and testing costs. This case report highlights how Shawbrook Bank, despite lower budgets and higher development and technological costs, managed to improve the customer experience significantly. Let’s get right into it.
The Challenge Every bank’s success story for digitization begins with a challenge, usually web application development. But for this bank, it was testing.
When this UK bank began developing new digital banking features to woo its existing customers, they were faced with the following challenges:
Inefficient testing They had a hard time validating the customer experience across various browsers. Since the bank did not have parallel testing measures in place post-web application development, they were wasting over 2500+ person days and significant funds to simply validate changes and test their product.
High tester turnover The tester turnover was unbearably high, presumably due to redundant and inefficient testing processes, leading to poor maintenance of the testing ecosystem. At one point, the bank was spending over $400,000 solely on testing.
Poor customer experience Given the inefficient testing practices and high tester turnover, validation efforts were delayed. So, the bank had to release the software to production prematurely. This, in turn, meant that customers were at the receiving end of a buggy software experience.
To put an end to all these problems, the bank decided to automate testing and accelerate the software development and feedback times. And for that, they turned to Quinnox for help. In the next section of this case report, we go over how the UK bank solved its software testing problems with Qyrus.
The Solution Quinnox used Qyrus, its proprietary AI-powered automation platform, to implement a shift-left quality strategy, through which the specialist bank was able to release software updates quickly without compromising the stability of business processes. Here’s how.
Automated tests The Qyrus team successfully automated a range of tests for the bank’s software through CI/CD pipeline integrations and Qyrus-native plugins and streamlined crucial processes like savings account activities, customer due diligence, and customer onboarding in its savings applications, lending applications, and customer apps.
Through Qyrus CI/CD automation, tests were executed immediately after the build, increasing testing efficiency. X-ray was used for test management and reporting was simplified as well, given reports got added directly to the pipeline.
Such automation lowered the number of hours spent by the UK bank’s testing team and reduced the number of manual errors dramatically. For perspective, such automation prevented the release of over 2500+ bugs into production.
Repurposed functional tests for performance testing To reduce the testing time, the bank repurposed functional tests for performance testing with Qyrus. They executed tests for over 1000+ users simultaneously, increasing test reusability and improving testing efficiency. Furthermore, thanks to repurposing tests, they were able to ensure greater consistency and run reliable tests, given there was no scope for introducing errors manually.
This meant that their savings applications, lending applications, and customer-facing applications were bug-free.
Scalable infrastructure and coverage With Qyrus’ help, the bank was also able to expand its test coverage across multiple platforms, browsers, devices, and operating systems, quickly. This ensured the bank’s customers had a consistent user experience across platforms, no matter which platform they used, savings applications, lending applications, or others.
The Impact The Shawbrook Bank success story is an excellent example of how companies can follow through with their promise of providing its customers the best experience possible, with better testing.
After all, with Qyrus’ AI-based testing automation platform, the UK bank was able to streamline testing considerably.
For the purpose of this case report, it translated to:
60% reduction in manual efforts with Qyrus automation
85% effort reduction across testing and QA lifecycle
200% ROI within first 12 months
“Quinnox is a key partner of ours, not only supporting our technology delivery teams but also with tools like Qyrus. Test automation is a critical capability for any engineering team, and Qyrus supports the testing of our web, API, and mobile components as a part of our CI/CD processes, and also in ongoing regression testing across our partner ecosystem. The real power of Qyrus is that we have this extremely broad testing capability in one tool, run in the Cloud, and reusable across all our development teams.” – Russ Thornton, CTO, Shawbrook Bank
Hey there, testing heroes! It’s Feature Friday, and we’re about to embark on a mobile testing adventure that’s as wild as a squirrel with a caffeine addiction. Have you ever felt like finding that elusive element in your mobile app was like searching for your keys in the Bermuda Triangle? Well, fear not, because Dan and Steve from Qyrus are here with their secret sauce. They’ll spill the beans on how to find those elements with our action types like “Tap by Relative Coordinates,” “Send Text,” and the superhero-sounding “Dynamic Press Keys.” So, grab your coffee, lean in closer, and let’s unveil these nifty mobile testing hacks together!
Tell us, what happens when a user cannot find the element they’re looking for when building mobile tests?
Dan: Well, we have a few ways that users can get around not being able to find an element they’re trying to interact with in their script. And that comes in a few different ways through using a few of our various action types. Firstly, we have “Tap by Relative Coordinates,” then we have “Send Text,” and lastly “Dynamic Press Keys.”
Steve: Qyrus can provide a more robust way of interacting with elements than simply using “Tap By Coordinates,” which can be very flaky between devices. By using “Tap By Relative Coordinates,” the user can use a parent element locator as a reference point to interact with an internal element that has been hidden. A user can then use “Send Text” to set data or “Dynamic Press Keys” to add data from a dynamic variable.
What is the overall impact on the testing process?
Dan: Well, by implementing the strategy we outlined above, users can reduce the amount of time it takes to build or create test scripts. Also, this workaround is much simpler than each time adjusting the coordinates you want to tap on each based on the device being tested.
Steve: Imagine testing on a range of different devices, all with differing resolutions. That means each device would almost require its own script because of the coordinate issue. Furthermore, it’s an easy-to-understand process that all takes place on the Qyrus UI with no code involved. That means it’s also more accessible to the potential business users of Qyrus.
Does the same or similar functionality exist without Qyrus, and how do competitors address similar problems?
Dan: Competitors typically utilize a coordinate-based approach when it comes to workarounds for these types of issues. These solutions tend to be flaky. Sometimes we also see a computer vision-based approach to match an element from an image. To be clear, Qyrus has this capability as well, but we have found that it can slow down performance.
Steve: Before “Tap By Relative Coordinates,” a user would use the phone coordinates on the image to interact with the element. To handle tests on multiple phones, they would have to create a series of variables and environment profiles, which is time-consuming. The other way would be the computer vision route, which would require uploading an image and then taking a performance hit during test execution.
How do you see this solution impacting day-to-day operations across organizations?
Steve: It reduces the potential for flaky tests in the element not found use case. It also reduces the amount of work to find a path towards working with the solution. There is also obviously less hassle with broken tests from unreachable elements.
Dan: Again, the biggest benefit is that the same locator information can be shared across different devices, improving the potential of reusing the same test script across different phones.
And there you have it, fellow testing heroes! We hope you’ve enjoyed this caffeinated journey through the mobile testing jungle with Dan and Steve. Just remember, when you find yourself hunting for those elusive elements, you now have some superhero action types in your utility belt. So go forth, conquer those mobile testing challenges, and may your app always be as smooth as a perfectly brewed cup of coffee. Stay caffeinated, stay testing, and stay awesome!
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.
Flakiness, brittleness, and fragmentation—these are testing nightmares even for veterans. Failed tests usually translate to substantial time spent on script refactoring and maintenance. Self-healing test capabilities can seamlessly mitigate test brittleness or the probability of a breaking test.
Ensure the fastest time to market for your software with Qyrus Healer – AI testing automation tool. Right from Web app functionality tests to automatic updating of element shifts, Healer brings immense QA possibilities. Healer’s rich feature set enables real-time test script monitoring and modifications.
A breaking test can recover from failures in microseconds when Healer comes into the picture. That too, with accuracy of more than 99.9%.
Requirements like updates of locator element changes in apps gain significantly from Healer’s avant-garde capabilities. AI-enabled test script correction means that Healer learns on the go without advance training on your application.
The Healer – AI testing automation tool is ideal to effortlessly avoid test brittleness, a capability which is further supplemented by Qyrus’ no code capabilities. It puts an end to worries about integrity of element attributes or flakiness in tests. This means that test processes stay ahead of code refresh and update cycles.
Advanced AI algorithms of Healer even account for the structural and visual attributes of every page element. For instance, Healer can intelligently identify element changes across the application lifecycle. Updated locator values are then used to ensure that your test script stays relevant.
In this session of The Qyrus Test-pert, join Rohith R Nair to learn how to:
Rapidly improve test automation reliability and ship faster
Save time spent fixing flakiness and test brittleness
Streamline testing automation and test resources
Automatically recreate a breaking test script’s functionality
Dynamically diagnose and update element changes
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.
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.
