Did you know that more than 50% of development efforts across organizations are taken up by APIs? Source
The API testing market will be worth USD 1.56 billion in 2022, and exhibit a CAGR of 18.97 per cent between 2023 and 2032. Source
While there is no doubt that API investments remain strong, and the API testing market is growing rapidly, API testing might not be a top priority for organizations as they cannot address its complexities.
Their API testing strategy is unable to shift left, which leaves APIs just short of becoming a strategic asset. Organizations must move to an automated API testing approach to accelerate the API testing process and ensure various stakeholders can identify bugs early on in the development cycle.
In this e-book, we discuss the various API testing challenges that stop an organization from moving to shift left testing and how an automated approach to API testing helps address these challenges.
This e-book also covers:
The Importance of the Shift Left Approach to Testing
Testing Complexities that Act as a Barrier to the Approach
Addressing Complexities with Automated API Testing
How Qyrus Supports API Testing Efforts?
Tangible Results from Qyrus
“Progress is impossible without change.” These are words spoken by Walt Disney, one of the most culturally influential men to walk the Earth. These are words that Qyrus personifies and that our amazing minds here live by. Change is what makes the world go round, and what keeps us writing these amazing Feature Fridays! This week we are joined by Tim, Jorell, and Linto to go over some changes that are coming to our main page’s dashboard. Let’s hear about how these changes can help you!
Tell us more about updates to analytics and insights on Qyrus.
Tim: Well, for starters, the first thing you might notice is the update to the main dashboard. Previously, we were making little use of the available space on the dashboard. Now, we’ve changed that. You’re able to access information on passing versus failing rates across different projects, the total number of tests built and executed across the team, and a list of tests recently worked on.
Jorell: Furthermore, we’re able to see daily contributions and login activity on a specific team, allowing team members to collaborate more efficiently. Users can also get a quick overview of their infrastructure setup. Lastly, on the page, you’ll see we’ve added a checklist to keep track of things to do.
Linto: We’ve found that overall, this update helps improve the user experience of the platform’s main dashboard, specifically in terms of navigation. We’ve moved the list of services from the main part of the page to be part of a collapsible sidebar, now. That way, the most important things are in your face first.
How can this impact the testing process?
Jorell: Well, in general, there’s an impact in the area of reporting and analytics. There’s a lot more offered to the user to analyze the testing results across projects and teams. Instead of having to navigate all the way to a specific test’s report, we can view those details directly on the dashboard.
Tim: It gives us a better general overview of the testing ecosystem. We can specifically target Web projects, Mobile projects, or API projects on the dashboard. Overall, we can see how the amount of time spent viewing and analyzing a larger amount of reports might be impacted.
What kind of possible improvements or extra features might we see added in the future?
Linto: Adding more customizable widgets is one thing we’ve brainstormed, like providing more choices for the user to make the dashboard their own and tailor it to their needs.
Jorell: For example, one user might not require such a large overview of an entire team or project, but rather something more granular. We want to enable users to customize their dashboards to help them become more efficient.
How might these updates help testers, developers, and business technologists? What value can this feature bring?
Tim: This is exactly where customization would come in handy! No matter what role you play, the dashboard can play to your needs. Testers and developers might quickly see the data on passing and failing rates in projects. But they can also get a quick view of the test infrastructure and its usage. Checklists also come in handy to keep track of tasks directly on the project.
Jorell: Business technologists could use the dashboard for more business-oriented or managerial tasks, such as checking on the health of projects and testing various applications. They can also get a good overview of team contributions and activity.
How do you see these updates impacting day-to-day operations across organizations?
Jorell: Well, in general, I would give a better overview of operations, allowing users to spend less time navigating around the platform to view specific reports and results.
Linto: A user can see the already recently worked on tests, and in that way, they can be prevented from recreating a test that is already existing. Then, they can just clone and reuse it.
Although nothing astronomical, these updates provide proof that Qyrus is an ever-evolving platform, constantly looking to improve the lives and day-to-day of testers using it everywhere. And besides that, we’re committed to keep improving to help you achieve your testing goals more efficiently. Progress never stops, and neither does Qyrus. Thanks for joining us this week, and we hope you enjoy the rest of your Friday!
In recent times, the digital workplace has accelerated in numerous ways, with many of us using more digital tools to get work done and digitizing every possible operational process. As a result, organizations deliver more software, and development cycles are getting increasingly complex, especially when considering customer experience expectations across connected systems. At the crossroads of customer expectations and the demands of speed to market, the cost is usually the central issue.
What about Quality? The augmented speed and increase of digital have put a lot of fire on testing leaders who need to make sure their enterprises are not just delivering software fast and within budget but with quality.
This webinar features industry-leading analyst Diego Lo Giudice VP Principal Analysts from Forrester and, Ravi Sundaram Chief Strategy Officer, from Quinnox. They will share how AI-augmented testing can make digital teams faster and smarter.
We will discuss:
Market trends in testing and test automation and how the use of AI and ML impacts testing.
What are the most common use cases and opportunities?
How Quinnox has embraced AI for its automation-testing platform – Qyrus.
Qyrus roadmap for AI and testing and their potential impacts on client environments.
SPEAKERS
Diego Lo Guidice
VP Principal Analysts, Forrester
With Forrester since July 2005, Diego primarily contributes to and advises on Forrester’s offerings for Application Development & Delivery Professionals. He partners with Forrester’s global application leaders and is a leading expert on SDLC processes and practices, covering topics such as Agile development, Agile and Lean transformations, Agile development sourcing strategies and services, Agile testing practices and tools, DevOps, and software testing and quality, with a key focus on systems of engagement. Diego also covers software delivery metrics, artificial intelligence, and open source governance.
His 28 years of industry experience, in addition to application development, allow him to give expert advice on change management programs for optimizing the overall modern application delivery process, execute technology management assessments, review technology management strategies, and make comparisons. He also has experience in complex mission-critical project and client engagement management
Ravi Sundaram
Chief Strategy Officer, Qyrus
Ravi Sundaram leads the strategy & business for Intelligent Automation product within Quinnox. He has over two decades of experience driving business development, product strategy, and delivering innovative solutions for challenging business problems.
Ravi is the founding team member of the intelligent automation product called – Qyrus. He has spearheaded business & IT transformation for Quinnox and its Fortune 500 customers. An engineer at heart, Ravi excels in advising customers in their transformation journey through his experience in SaaS products, intelligent automation, SAP, Cloud deployments.
He spent the last decade building SaaS products specializing in intelligent automation testing. He has helped multiple customer’s set-up their CoEs and become early adopters of intelligent testing. His experience includes senior positions with consulting firms, advisory and board roles at B2B, wellness, and collaboration startups.
Topic: Mobile Automation using Qyrus
Description:
In this fast-paced digital world, mobile automation has become fairly complex and laborious, especially to an untrained eye. Moreover, to maintain the competitive edge, organizations strive to achieve the best combination of speed, quality and cost to get on top.
Utilizing a codeless, automated, AI and ML driven mobile testing platform can improve mobile automation testing quality while increasing efficiency and reducing time to market.
In this testing webinar, Suraj will take you through Qyrus’ mobile testing platform in detail and talk about how automating mobile application testing provides a faster, more efficient testing process with a wider range of coverage and better test results.
How to achieve full automation – Integrations and Foundations
Mobile testing demo in detail
Speaker:
Suraj Patel, Platform and Sales Engineer, Qyrus
Speaker Bio:
A platform expert with nearly half a decade of industry experience and a specificity towards developing and maintaining automated testing frameworks, Suraj Patel focuses on understanding and optimizing unique testing requirements through automation. Commanding a background in software development with gained experience across industry leading events and conferences, Suraj is passionate about the cutting edge of development and learning how to utilize different technologies to enhance the Quality Assurance lifecycle.
As he would say, reciting a quote by Godfrey Reggio, “It is not that we use technology, we live technology” and in the same light, Suraj is empowered to bring end users the smile they deserve by promoting high quality, functional applications through optimization of testing and quality assurance practices.
As David Copperfield once said, “The magic lives in the performance!” Although we all know David Copperfield to be a magician, not a tester, the same can be said in the testing world, as well! Performance testing is such an important and integral part of testing an application. Measuring the time it takes for your webpage to load or the time it takes for some tasks to be completed is included in performance testing. However, today, we are here to talk a little bit about the performance testing of APIs. But, wait, there’s more! We’re going to be talking specifically about the performance testing of end-to-end API processes. Here to deliver more information for us today are our good friends Parth and Steve; without further ado, let’s delve in!
Tell us more about end-to-end API performance testing offered by Qyrus and its use cases.
Steve:
We have seen many people take advantage of our API Process Testing service, in which we enable users to stitch or chain together API tests in order to make a complete end-to-end flow. This gave users the kind of holistic testing they were looking for. With Qyrus, we can check the functionality of each individual API, but with this, we can also check that these APIs work together exactly as they should.
Parth:
Now, being able to test this process’ performance is a big step forward. Previously, we were able to see the basic response times for each API call in a process, but now we can get a much more granular view that we were never able to before.
Steve:
Exactly. We are, for example, able to get values back for the response time of the entire API flow, the response time per API, as well as the status code per API. This is tested over a certain thread count, or users accessing the same resource—or in this case, flow—concurrently.
Adding more tools and functionality to Qyrus is a never-ending task here. Going further into process testing, you can learn more about our individual API performance testing here from another Feature Friday. If interested, here are two more about web performance profiling and mobile performance profiling.
What is end-to-end API performance testing’s overall impact on the testing process?
Parth:
In general, the impact we see is a larger amount of test coverage. This is because the user is able to reuse these API Process tests that they created for functional purposes, but instead run them to test performance.
Steve:
Furthermore, users can now, in a literal sense, perform performance tests on these processes. Prior on Qyrus, you had to run performance tests on each functional API in order to get an idea of what the performance metrics were like. But still, you had an incomplete picture.
How might this feature help testers, developers, and business technologists? What value can this feature bring?
Parth:
Like Steve previously stated, a tester can now actually run performance tests across a whole process or end-to-end flow and can see the bigger picture, you might say.
Steve:
Beyond that, developers could test max stress levels for their APIs when they’re all connected in a flow and make adjustments from there. This can be helpful at catching performance flaws early on in the development process.
Parth:
And for business technologists, they can get better information about performance at a faster pace. These test results can be shared, emailed, or even downloaded.
Collaboration, although not an explicit feature on Qyrus, is a key quality that Qyrus upholds across the platform – whether that be collaboration during the test building phase, collaborating on test executions, or sharing reports and collaborating with other teammates that way. You can learn more about our collaborative efforts in one of our previous Feature Fridays.
How do you see this feature impacting day-to-day operations across organizations?
Steve:
Well, to start, as we mentioned before, users are now enabled to run these types of tests across entire end-to-end API flows. This would mean that day-to-day, testers no longer have to run individual process tests over and over again. Now, they can do it all from one place, and that includes functional testing, as well.
Parth:
Furthermore, no prior coding knowledge is required. It’s all been simplified down to a no-code experience where any user can understand what’s going on. As a last point, all tests here are just reused from our API Functional Testing section. Nothing has to be recreated, just reused and modified if necessary.
What might we expect to see improved about end-to-end API performance testing?
Steve:
Well, we’d like to see more performance metrics added for the user’s benefit. Things are still in progress here, and improvements never stop coming to the platform as a whole.
Parth:
Right. Some of these metrics might include ones that are currently present under our “Advanced Metrics” under API Performance Testing. This might include response latencies over time per API, hits per second, transactions per second, active threads over time, and a general summary tab where we can see max, min, and average response times and more.
If the number of features that we have across the platform isn’t magical, then I don’t know what is! Well, besides David Copperfield, Oh, and Fridays, those sure are magical! Speaking of, it must be Friday, since you’re reading this. Please have an enchanting weekend and enjoy the time off with family and loved ones. Don’t worry, though, next week we’ll pull some more fantastical features out of our hat for you to learn about! See you next week on our next iteration of Feature Friday!
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.
Tell us more about the recent updates to test building in the API solution.
Adhiraj:
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.
Amy:
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 on the same page and in one place.
Jorell:
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 number of clicks it takes to get to a certain page.
What is the overall impact these API updates have on the testing process?
Adhiraj:
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.
Jorell:
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 at a faster pace. This also leads to a reduced amount of effort put forth to chain everything together in a large flow.
How might these API updates help testers, developers, and business technologists? What value can this feature bring?
Amy:
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.
Adhiraj:
Because of this tool, the updates made to the test building mostly revolve around the tester, as this is a platform built just for them. However, developers can use API process testing to perform basic unit tests of the systems they build. The updates also help improve their lives when doing so.
Jorell:
In general, a business technologist would be able to better understand the connections between the APIs as well as 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.
Does the same or similar functionality exist without Qyrus, and how do competitors address similar problems?
Amy:
One big differentiator from 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.
Adhiraj:
In a traditional sense, a good deal of 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.
How do you see these improvements impacting day-to-day operations across organizations?
Jorell:
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.
Amy:
Well, simply put, making the whole process a degree easier. Less time and effort means higher productivity and happier workers.
Adhiraj:
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 the 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!
The holiday rush is officially over! With this holiday season now in the rearview mirror, it’s time to look forward to the road ahead and get prepared for an undoubtedly busy 2023. But don’t worry, Qyrus isn’t throwing on the breaks anytime soon when it comes to features! This week, we are joined by Daniel and Joyal from our Chicago Qyrus team to learn more about some new mobile native locator strategies that have been introduced to the Qyrus platform. Without further delay, let’s race into this topic!
Tell us more about this capability offered by Qyrus and its use cases.
Daniel:
Qyrus mobile testing now has support for 3 native locator strategies when users are building out their test scripts. There are two that are supported for iOS—class chain and predicate string—and one for Android: UIAutomator.
Joyal:
This is helpful for those mobile testers who are more experienced. Native locators can speed up test executions by improving the performance of locating the element. There are elements out there that cannot be found by using ID, name, accessibility ID, or XPath locator types.
Daniel:
Even though this strategy is the most common out there and platform-agnostic—that is to say, it works for both iOS and Android devices—it can be the most time-intensive choice. By choosing a native locator strategy, a tester can leverage the flexibility that an XPath can provide without incurring a performance penalty.
For the reader’s benefit, we have provided an example below:
Example of XPath on iOS: //XCUIElementTypeOther[@label=’login’)]
As a class chain, this XPath can look like this: **/XCUIElementTypeOther[label matches “login”]
But using a predicate string, it could look like this: label matches “login”
What is the overall impact this might have on the testing process?
Daniel:
We can see this having an impact during the test-building phase when users are creating and building up their catalog or suite of test scripts for execution. This can help expedite the test-building process since, to an experienced mobile tester, using something like a predicate string is much quicker than having to get an XPath for every element.
Joyal:
Not only that, but since we see faster run times, we can say there’s a definite impact on test executions. The new native locator strategies provide an overall speed boost to the testing process as a whole.
Qyrus is always looking to push the limit when it comes to developing new tools and strategies to help enable better testing across the board for everyone involved. This is not limited to different levels or types of testers, but also to less technical personnel.
How might these new native locator strategies help testers, developers, and business technologists? What value can this feature bring?
Joyal:
Well, as we mentioned before, an advanced tester might find the most use out of this feature. In general, it makes their testing experience easier. But besides that, using a predicate string also makes it easier for less technical users of Qyrus to understand what is being searched for. Seeing “label matches ‘login’” makes it much easier to understand what the test is looking for than a long, exhaustive XPath.
Daniel:
And for developers, they’d find use in this, much similar to a tester. It would make their unit testing and quick tests much easier to create, run, and maintain in the long run.
Does the same or similar functionality exist without Qyrus, and how do competitors address similar problems?
Joyal:
There are a few competitors out there that do offer all these strategies already, but on Qyrus we are striving to make these strategies more usable for both experienced and newer testers.
Dan:
And when it comes to using these strategies outside of Qyrus, anyone can really do it when they’re scripting their own automated tests. It’s just that everything has to be done through code, whereas on the Qyrus platform, everything is no-code and simple to use.
Our features on Qyrus have the one goal of making testing more efficient, but that can be done in several ways. Speeding up the time it takes to build and execute tests, providing more insight into reporting, and enabling more intuitive test building are just some ways we are actively working to make testing more efficient.
How do you see these impacting day-to-day operations across organizations?
Dan:
Speed is really the main benefit of using these strategies. But there are some other advantages that can help to even further speed up day-to-day operations. “UIScrollable” can be used to automatically scroll the element if it is not in view, for example. This functionality is built into the locator strategy and is not possible with other strategies.
Joyal:
To further the topic of speed, the time taken to find elements during iOS testing is significantly reduced. For example, what might take an XPath strategy of 2.8 seconds to find an element can be done in 1.8 seconds with a predicate string and even quicker at 0.7 seconds using a class chain.
That wraps up this week’s Feature Friday. The drive for new and innovative testing strategies is greater than ever, and slowing down now could mean getting into a wreck in the future, so help protect yourself by switching to Qyrus as your testing platform! We hope that this weekend you take some time to slow down, stop, and enjoy some time off from your busy, racing weekly schedule. And then on Monday, maybe sign up for a Free Trial and check us out! Thanks again!
Notifications are everywhere in a person’s daily life nowadays. As per research done by the Pew Research Center, 97% of Americans own a cell phone of some kind, and 85% of Americans own a smartphone. This is astonishing considering that the last research done 10 years ago concluded that only 35% of Americans owned a smartphone. Not only that, but a third of high schoolers now own a smartphone.
With the evidence laid out in front of us like that, it’s a no-brainer that everyone everywhere is constantly getting notifications. And it’s about time that Qyrus joined in on that trend! Previously, we have talked about how we can give notifications via email to users to notify them about test executions, but now, we have a new feature that can enable Qyrus notifications in Teams and Slack channels! Joining us today are Milton and Kiwaun who’ll give us more insight into this topic.
Tell us more about the integrations with messaging apps offered by Qyrus and its use cases.
Kiwaun:
Yeah, so, basically what this feature enables users to do is set up Qyrus to deliver notifications to Microsoft Teams or Slack channels. This is a really simple feature, but one that can be considered super important for testers and developers.
Milton:
Email notifications are already a thing on Qyrus, but we all know how bloated our inboxes can get. Getting notifications for your Slack or Teams channels is much more convenient as a whole. That way, entire teams or multiple stakeholders can be notified instantly about test results. And lastly, if someone has those messaging apps on their mobile devices, they’ll also get these notifications on the fly.
Getting notifications on the fly is always helpful. Here at Qyrus, we seek to help. That is, it helps make testing more efficient, helps testers test smarter, and helps testers stay up-to-date with their testing landscape.
How might the integrations with messaging apps impact the testing process overall?
Kiwaun:
This feature only really has an impact on the reporting side of testing. The whole point is to get those notifications of test executions straight to your channel.
Milton:
But, overall, it can help in terms of effort reduction. Testers don’t have to manually log into Qyrus in order to view the report of an execution, but rather can just get that quick view of it as a notification in their Slack or Teams channels.
Like many features on Qyrus, this feature can be utilized by more than just testers. Qyrus helps to enable a better understanding of testing and the testing landscape that a company has by making everything more digestible when it comes to test building and even reporting and analytics.
How might this feature help testers, developers, and business technologists? What value can this feature bring?
Milton:
Obviously, testers would use this feature to get notifications straight to their messaging app channels, but developers can utilize this as well when they build and execute their unit tests on Qyrus.
Kiwaun:
Business technologists would get great snapshot information from these notifications, as well. They can stay up to date without having to get into the nitty-gritty of things or even navigate their way through the platform. They can get a great overview of what’s going on, all on the go.
Qyrus’ goal is to improve the day-to-day operations of everyone involved in the testing process. Our features are meant to make a lasting impression on how testing is done in an organization and impact how these action items are performed.
How do you see this feature impacting day-to-day operations across organizations?
Milton:
More than anything, this feature provides convenience so that the user does not have to log in and manually check tests every time they need to. That can be a waste of time, especially over a longer period of time.
Kiwaun:
On top of that, there are configurations that can be made that will help focus on what kind of notifications you will receive from Qyrus. This means that this is a tool for everyone.
Notifications surround us in almost every aspect of our everyday lives. Furthermore, notifications, in the future, will surely play an even larger role, as we can see a shift in cellphone and smartphone usage amongst Americans alone. Regarding Qyrus, we seek to further expand our abilities to notify users of their testing efforts and landscape. This is just one way in which we seek to further our capabilities. Thanks for joining us this week for Feature Friday. We hope you join us next week for more information on our myriad of features!
A Gartner study has mentioned that by 2024, 75% of large enterprises will use AI-enabled test automation tools for continuous testing. Also, 80% of the participants intend to increase the number of AI-based trials and proofs of concept, as per the World Quality Report survey. Such reports on industry trends indicate that AI-based automated testing is on the rise and on track for more than just a passing grade.
We at Qyrus believe that an AI-led quality assurance testing solution should be based on an approach guided by a continuous cycle of Discover >Understand > Predict > Respond.
Read this e-book to know:
How Artificial Intelligence help software developers and testers across industries?
How can Qyrus help in shaping the QA & testing space using AI?
How can AI make test automation more productive?
Businesses that deliver and maintain high-quality outcomes for customers over a sustained period are the ones that tend to rule the roost. And to that effect, enterprise CIOs—from technology startups to multinational companies are going all out to include high-performance, feature-rich, and secure software systems in their tech stack. But achieving this hyper-performance, hyper-quality vision is easier said than done.
Even organizations that have streamlined software and application development processes expect their development teams to improve the testing speed for faster time-to-market. In this conflicting environment, CIOs increasingly look for quality assurance processes for testing automation that helps them address end-user expectations more effectively and stay responsive to testing standards changes.
Download this whitepaper to know:
How CIOs can benefit from test automation
Key steps to ensure quality at speed in continuous testing
How Qyrus can help businesses in any segment to make their tests faster, smarter, and more quality-oriented
