There’s always room for improvement. That is true for just about everything in life, and that does not exclude testing. Innovation never sleeps, and testing has an ever-moving goalpost, so strive for continuous improvement rather than perfection. Every week, we post about some new feature or set of features that can help improve your testing in some way, and this week we are going to talk about our recent improvements to API test building on Qyrus. Joining us today are Adhiraj, Amy, and Jorell from our Chicago office to tell us more.
The biggest update comes to our API Process testing section. There’s a new UI update that has completely revamped how API Process tests are chained together. This improves the user experience of those building these tests by making it simpler for them to see what connections are made.
The goal of the new update was just that – to make things simpler. Instead of requiring the user to configure connections between APIs on a separate page. Users would go back and forth between two pages, and with this update everything is done from the same page and one place.
And on top of that, a new navigation button has been added to aid in navigation between the different sections in API Process testing. This helps reduce the amount of clicks it takes to get to a certain page.
Overall, these improvements help reduce the amount of time a user has to spend building these process tests. Similar to how going through a doorway and into another room can make you forget what you were going to do, the same can happen when it comes to navigating pages on a website.
Furthermore, these improvements can help improve test coverage through a better user experience and a reduced amount of time taken to build out a process test. That means testers can cover more and at a faster pace. This also leads to a reduced amount of effort put forth to chain everything together in a large flow.
Well, for testers, their entire job just got easier. Making a process test is already not that difficult to do on the platform, but with these improvements and further down the line, testers should expect more smooth sailing ahead.
Because this tool the updates made to test building mostly revolve around the tester, as this is a platform built just for them. But developers can use API Process testing to perform basic unit tests of their systems they built out. The updates also help improve their lives when doing so.
In general, a business technologist would be able to better understand the connections between the APIs as well, and how the data transfer is happening. Again, having to navigate from one screen to the next can be a hassle, and for less technical people it can just make things downright hieroglyphic.
One big differentiator with some competitors is our completely cloud-based approach. Everything can be done from a browser and from anywhere, without anything being downloaded. But to further that, the whole point of these updates is to make our test building simpler than others.
In a traditional sense, a good deal coding knowledge would be required in order to make a process test similar to what we’ve done here. And on top of that, it’s still a hassle, unless time is taken to build out a UI for a similar system. Even then, the time and resources put in just about outweigh the benefits coming out. Maintenance and upkeep are another problem, then.
Keeping testers on one page, easier navigation, better connections for better understanding, and reusability are some things that will impact a user’s day-to-day when using this platform, specifically the API section.
Well, simply put, making the whole process a degree easier. Less time and effort mean higher productivity and happier workers.
And on top of all that, there are about another 10 or so features that build off this one, taking things to another level with each one, making things even faster and more efficient. And we here at Qyrus never stop coming with more.
Improvement – whether that be faster executions, more robust reporting, or better test building, Qyrus is here to improve it all. API Process testing is just one stop on our route to improving the overall user experience here on Qyrus. Besides just improving user experience, we’re doing so much more! Come on and sign up for a Free Trial to see for yourself. Join us next week to learn about more improvements to be made in your testing ecosystem!
Don't miss out on this must-attend event - mark your calendars for April 30th to May 5th, 2023 and join us at #STAREAST!
Performance profiling metrics on Qyrus enable testers to get a more granular view of how their API or APIs perform over time.
There have been a range of additions to mobile test building that make the process even simpler and more efficient. Learn More how you can improve your Mobile Testing with Qyrus.
The Xray integration is an out of the box integration that provides a link between your Xray issues and your Qyrus test scripts. Upon execution of these test scripts, the results are then populated straight to Xray to view execution results and updates from a single platform.
Low-code/no-code platforms can provide a wide range of benefits for teams in the testing industry. By identifying specific use cases, carefully evaluating different platforms, and implementing governance and security measures, teams can use low/no-code automation to improve their testing processes and achieve their goals
Testing an individual API is good but testing the functionality of multiple APIs together in a chain is an even better API testing strategy because that’s how APIs work in a real-world scenario.
CLI commands allow users to interact with, inspect, or execute automated test scripts without visiting the Qyrus UI. They have a range of functionality including allowing testers to execute scripts, update global variables, upload IPA/APK files, delete IPA/APK files, and send reports via email, all through pipeline.