Welcome to our October update! As we move into the final quarter of the year, our focus sharpens on refining the details that make a world of difference in your daily workflows. At Qyrus, we are continually committed to evolving our platform not just with big new features, but with smart enhancements that make your testing processes faster, simpler, and more powerful.

This month, we are excited to roll out a series of updates centered on intelligent workflow automation, enhanced user control, and advanced mobile testing capabilities. We’ve streamlined how you import, export, and manage test assets, unlocked a powerful new way to simulate offline conditions for iOS, and expanded our AI-driven analytics to cover your core API test suites. These improvements are all designed to give you more time back in your day and greater confidence in your results.

Let’s explore the latest enhancements now available on the Qyrus platform!

Improvement

Your Scenarios, Your Way: New Controls for TestGenerator Imports

Test Generator Imports

The Challenge:

Previously, when importing scenarios from TestGenerator, the system would import assets in a predefined way. This lacked the flexibility for users who might only want high-level scenario titles for test planning. Additionally, creating these test assets in both the Qyrus platform and a management tool like Rally requires two separate, repetitive actions.

The Fix:

We have introduced significant enhancements to the TestGenerator import process to give you more control and improve efficiency. You now have the option to choose whether to import “Only the scenarios” or the complete “Scenarios along with their test steps.” You can now choose to import your generated test assets into both the Qyrus platform and Rally at the same time, in a single action.

How will it help?

These updates provide you with more precise control and a more streamlined workflow:

You can now choose the level of detail you want, whether it’s just high-level scenarios for creating a test plan or the full, detailed steps for immediate automation.

The simultaneous import to Qyrus and Rally eliminates a repetitive step, saves you valuable time, and ensures your test cases are perfectly synchronized with your project management tool from the moment they are created.

Improvement

Swiftly Edit Your Scenarios: Delete One Step or Delete Them All!

Delete Steps

The Challenge:

Previously, managing steps within the Test Steps Editor could be inefficient. Deleting a single, unwanted step might have been a cumbersome process, and clearing an entire test scenario to start fresh required the tedious task of removing each step one by one, which was especially frustrating for long test cases.

The Fix:

We have significantly improved the Test Steps Editor with new, highly requested features:

Per-Step Delete: Each test step now has its own dedicated delete option.
Delete All: A new “Delete All” feature has been added to instantly clear all steps from a scenario with a single click.

How will it help?

These updates make managing and refining your test scenarios much faster and more intuitive. The per-step delete option allows for quick, precise edits, while the “Delete All” feature is a massive time-saver when you need to reset a test case. This gives you more efficient control over your test steps and improves your overall workflow within the editor

Improvement

One Selection, Two Destinations: Streamlined Exports to Rally and Qyrus!

The Challenge:

Previously, the workflow for exporting scripts to both Rally and the Qyrus platform was tedious. After a user carefully selected a group of scripts and exported them to Rally, the selection would reset. To then import those exact same scripts into Qyrus, the user was forced to manually re-select all of them, which we found out was inefficient and nearly impossible to do accurately from memory with a large number of scripts.

The Fix:

We have refactored this export process to be more intelligent and user-friendly. Now, after you select a set of scenarios and export them to Rally, your script selection will be maintained. You can then immediately proceed to import that same selected group into the Qyrus module without having to re-select anything.

How will it help?

This enhancement creates a seamless, logical, and efficient workflow for managing test assets across platforms. It eliminates the frustrating and time-consuming task of re-selecting scripts, saving you significant manual effort. This ensures consistency between what is exported to Rally and what is imported to Qyrus, removing the risk of human error and dramatically speeding up the entire process.

New Feature

From Suite to Sequence: AI Now Auto-Builds Workflows From Your APIs!

Auto Builds Workflows From Your APIs

The Challenge:

Previously, a user might have a Test Suite containing all the necessary APIs for a complete end-to-end test, but they existed as a simple, unordered list. To turn this list into a functional workflow, the user had to manually drag and drop each API into the correct sequence and painstakingly map the data dependencies between them (e.g., passing an auth token from a login API to subsequent requests). This manual process was time-consuming and prone to errors.

The Fix:

We have introduced a powerful new AI capability for Test Suites. Users can now use an “auto-map” or “build workflow” feature on their existing Test Suites. The AI will analyze all the APIs within the suite, intelligently identify their relationships and dependencies, and automatically construct a complete, ordered workflow with the data mappings already configured.

How will it help?

This feature dramatically accelerates the creation of complex API workflows. It saves a significant amount of time and effort by automating the most tedious parts of the process—sequencing the steps and mapping the data. This not only reduces the chance of manual errors but also empowers users to instantly convert their existing collections of APIs into powerful, executable end-to-end tests with a single click.

Improvement

Consistent Clarity: Key Diagnostics Now in All qAPI Report Views

qAPI Report Views

The Challenge:

Users needed a consistent and immediate way to diagnose API test results across different reporting interfaces. Key information like the HTTP Status Code was often hidden within detailed views, and tests that ran without any actual assertions could be ambiguously reported, making it difficult to get a quick, clear picture of the test outcomes.

The Fix:

We have rolled out a comprehensive reporting enhancement that is now consistently applied across all qAPI report views (including the Reports Table, Reports Summary, and Quick Summary). This update introduces:

A new “Status Code” column for at-a-glance diagnostics of the API response.
A new, explicit status to clearly identify any execution that was run without assertions (test cases).

How will it help?

This update provides a unified and much richer reporting experience. You can now instantly see crucial diagnostic information, like HTTP status codes, no matter which report view you are using, dramatically speeding up your analysis. The new status for tests without assertions eliminates ambiguity and encourages better testing practices, ensuring you have a clear and consistent understanding of your test results across the entire platform.

New Feature

Retry with Confidence: Improved Interactions with Local Agents!

The Challenge:

Previously, the “retry” functionality for functional test executions could sometimes be inconsistent, particularly when those tests were running on a local agent. The interaction between the platform and the agent during a retry attempt was not as smooth as it could be, occasionally leading to unreliable or clunky re-executions.

The Fix:

We have refactored and improved the logic behind our retry options for functional reports. These enhancements specifically optimize the communication protocol between the Qyrus platform and your local agents, ensuring that retry commands are handled more efficiently and reliably.

How will it help?

This update provides a significantly smoother and more dependable experience when re-running failed tests on a local agent. You can now retry with confidence, knowing that the re-execution will be triggered smoothly and reliably. This is crucial for an efficient debugging workflow, allowing you to quickly distinguish between transient environment issues and genuine application bugs.

New Feature

Test Smarter, Not Harder: Impact Analyzer Now Supports Your qAPI Suites!

The Challenge:

Previously, our powerful Java and Python Impact Analyzers were limited in scope and could only analyze tests generated through DeepAPITesting. This meant that users could not leverage this smart, targeted testing capability for their primary, user-created functional test suites within the qAPI Workspace, missing out on the opportunity to optimize their regression cycles.

The Fix:

We have now fully integrated our Impact Analyzers (both Java and Python) with the tests you create and manage in the qAPI Workspace and Test Suites. The analyzer can now scan your codebase for changes and intelligently map those changes to the specific qAPI tests that cover the affected areas.

How will it help?

This integration unlocks a much smarter and more efficient way to run your regression tests. Instead of executing an entire qAPI test suite after every small code change, the Impact Analyzer will now tell you exactly which specific tests you need to run. This enables:

Targeted Test Execution: Dramatically reduce the scope of your regression runs.

Massive Time & Resource Savings: Get faster feedback by running only the necessary tests.

Smarter Regression Analysis: Confidently validate your changes without the overhead of a full regression cycle.

Ready to Accelerate Your Testing with October’s Upgrades?

We are dedicated to evolving Qyrus into a platform that not only anticipates your needs but also provides practical, powerful solutions that help you release top-quality software with greater speed and confidence.

Curious to see how these October enhancements can benefit your team? There’s no better way to understand the impact of Qyrus than to see it for yourself.

Ready to dive deeper or get started?

Book a Personalized Demo Today Start Your Free Qyrus Trial

The world of software testing moves fast, and staying ahead requires tools that not only keep pace but actively drive innovation. At Qyrus, we’re relentlessly focused on evolving our platform to empower your teams, streamline your workflows, and make achieving quality more intuitive than ever before. May was a busy month behind the scenes, packed with exciting new features and significant enhancements designed to give you even more power and flexibility in your testing journey.

Get ready to explore the latest advancements we’ve rolled out across the Qyrus platform!

Complex Web Tests, Now Powered by AI Genius!

Manual coding for complex calculations in web tests? Consider it a thing of the past! We’re thrilled to introduce a game-changing AI feature that lets you generate custom Java and JS code using simple, natural language descriptions. Just tell Qyrus what you need the code to do, and our AI gets to work, even understanding the variables you’ve already set up in your test. This AI Text-to-Code conversion is seamlessly integrated with our Execute JS, Execute JavaScript, and Execute Java actions, designed to produce accurate, executable snippets right when you need them. You maintain control, of course – easily review, modify, or copy the generated code before using it.

A quick note: This powerful AI code generation is currently a Beta feature, and we’re actively refining it based on your feedback!

Enhanced Run Visibility for Web Tests

But that’s not all for Web Testing this month. For our valued enterprise clients, managing your test runs just got clearer. You now have enhanced visibility into your test execution queues, allowing you to see detailed information, including the exact position of your test run in the queue. Gain better insight, plan more effectively, and stay informed every step of the way.

Sharper Focus for Your Mobile Visuals

Visual testing on mobile is crucial, but sometimes you need to tell your comparison tools to look past dynamic elements or irrelevant areas. This month, we’ve enhanced our Mobile Testing Mobile Testing capabilities to give you more granular control. You can now easily ignore specific areas within your mobile application screens, excluding those regions entirely from visual comparisons.

Additionally, you can ignore the header or footer of the screen meaning that you can easily compare different execution results and not run into issues due to differences in the notification bar or in a footer.

This means cleaner, more relevant results and less noise when you’re ensuring your app looks exactly as it should across devices. Focus on what truly matters for your app’s user interface integrity.

Device Farm: Smoother Streaming, Better Guidance

We know your time on the Device Farm Device Farm streaming screen is valuable, and a smooth experience is key. This month, we’ve rolled out several user experience improvements to make your interactions even more intuitive. The tour guide text has been refined to be more informative, guiding you clearly through the features.

We’ve also added a Global Navbar directly inside the device streaming page, providing consistent navigation right where you need it. Plus, for those times you’re working with a higher zoom percentage, we’ve included a handy scroll bar to make navigating the page much easier. Small changes, big impact on your workflow!

Desktop Testing: Schedule Your Success

We’re excited to announce that test scheduling is now available in Qyrus Desktop Testing. This highly requested feature, already familiar from other modules, brings a new level of automation to your desktop workflows. It’s particularly powerful for those complex end-to-end test cases that span across different modules, perhaps starting in a web portal, moving through a back office, and ending in servicing.

Now, you can schedule these crucial test flows, ensuring your regression suites run automatically, even aligning with deployment schedules. This means no more worrying about desktop availability at the exact moment of execution – Qyrus handles it for you. With this feature, efficiently managing tests for workflows impacting dozens of test cases becomes significantly simpler.

Smarter AI for Broader Test Coverage

Our commitment to leveraging AI to make testing more intelligent continues this month with key improvements to both TestGenerator and TestGenerator+. We’ve been refining these powerful features under the hood, and the result is simple but significant: you should now see more tests built by the AI compared to previous versions.

Remember, TestGenerator is designed to transform your JIRA tickets directly into actionable test scenarios, bridging the gap between development tasks and testing needs. TestGenerator+ takes it a step further, actively exploring untested areas of your application, intelligently identifying gaps, and helping you increase your overall test coverage. These enhancements mean our AI is working even harder to help you achieve comprehensive and efficient testing with less manual effort.

Ready to Experience the May Power-Ups?

This month’s Qyrus updates are all about putting more power, intelligence, and efficiency directly into your hands. From harnessing AI to generate complex web code to gaining sharper insights from mobile visual tests, scheduling your desktop workflows, and boosting the output of our AI test generators – every enhancement is designed with your success in mind. We’re dedicated to providing a platform that adapts to your needs, streamlines your processes, and helps you deliver quality software faster than ever before.

Excited to see these May power-ups in action? There’s no better way to understand the impact Qyrus can have on your testing journey than by experiencing it firsthand.

Ready to learn more or get started?

Book a Personalized Demo Today | Start Your Free Qyrus Trial

And don’t forget to explore our documentation for more details on these new features!

Explore Qyrus Documentation

We’re constantly building, innovating, and looking for ways to make your testing life easier. Stay tuned for more exciting updates from Qyrus!

Welcome to our September update! As we continue to evolve the Qyrus platform, our focus remains squarely on enhancing your productivity and empowering your team to achieve more, faster. We believe in removing friction from the testing lifecycle, and this month’s updates are a direct reflection of that commitment.

We are excited to introduce powerful new capabilities centered around dramatic workflow acceleration, intelligent AI-driven assistance, and seamless CI/CD integration. From features that eliminate repetitive tasks to an AI co-pilot that can fix your scripts on the fly, every enhancement is designed to save you valuable time and make your testing efforts more intuitive and powerful.

New Feature

Build Faster, Not from Scratch: Now Clone Your Web Testing Functions!

Clone Your Web Testing Functions

The Challenge:

Users often need to create functions (e.g. File Uploads, Global Software Quality Assurance) that are very similar to ones they have already built. Previously, this required repetitive manual effort to recreate these similar functions from scratch, step by step, which was inefficient and time-consuming.

The Fix:

We have now introduced a “Clone” option for functions for project set-up in Web Testing. With a single click, users can create an exact copy of any existing function, which they can then rename and modify as needed.

How will it help?

This feature directly addresses the need for efficiency in test creation. It saves significant time and effort by allowing you to quickly duplicate complex, existing functions instead of recreating them. This allows you to build out your function library much faster and focus on tweaking the logic for new scenarios rather than on repetitive setup.

Improvement

Fix It Right the First Time: Introducing Detailed Error Handling!

Detailed Error Handling

The Challenge:

Previously, when users encountered an error during a test, the error messages could sometimes be generic. This lack of specific guidance increased the chances of making mistakes again when re-entering information, leading to a frustrating trial-and-error process.

The Fix:

We have implemented a more detailed and intelligent error handling system within Web Testing. Now, when the system detects an error, it will provide a clear, specific, and actionable message (e.g. “Test Scrip 3, No data table for parameterization step”) that pinpoints exactly what is wrong and often suggests how to correct it.

How will it help?

This enhancement provides immediate, clear guidance that helps you fix issues faster. It ensures consistency in your configurations and reduces manual errors by preventing guesswork. This ultimately speeds up project setup and improves your overall workflow efficiency, allowing you to build tests with greater confidence and speed.

New Feature

Take Control of Your Pipeline: Stop Executions on Demand!

Stop Executions on Demand

The Challenge:

Previously, once a test execution was triggered in Test Orchestration, there was no way to stop it before it got completed. This lack of control meant that if a long-running suite was started by mistake, or if a low-priority job was tying up resources when a critical test needed to run, users had no choice but to wait.

The Fix:

We have now introduced a “Stop Execution” feature in Test Orchestration. Users will now see an option on any in-progress execution that allows them to immediately terminate the test run.

How will it help?

This feature gives you crucial, real-time control over your testing pipeline. You can now instantly:

Correct Mistakes: Immediately stop an execution that was triggered with the wrong configuration or data.

Prioritize with Agility: Free up valuable execution resources from a lower-priority task to run a more urgent, high-priority test.

This leads to more efficient use of your resources, prevents wasted time on incorrect runs, and provides the flexibility needed to manage a dynamic testing schedule.

Improvement

Set It Once: Unified Environment Selection for Test Orchestration!

Unified Environment Selection

The Challenge:

In the Service TO (Test Orchestration) section, users were required to select the environment individually for each script within a test. This process was time-consuming and repetitive, especially for tests containing a large number of scripts that all needed to run on the same environment. This also created an inconsistent experience, as other parts of the platform already offered a more efficient, test-level selection method.

The Fix:

We have updated the behavior in Service TO to align with user expectations and improve efficiency. You can now make a single environment selection at the test level, and this choice will automatically apply to all scripts contained within that test.

How will it help?

This enhancement significantly streamlines the test setup process. It eliminates unnecessary manual work by removing the need to select the same environment repeatedly for each script. This not only saves you a considerable amount of time, especially with large tests, but also provides a more consistent, intuitive, and user-friendly experience across the entire Test Orchestration module.

Improvement

Recorder Now Intelligently Fixes and Completes Your Tests!

The Challenge:

Test scripts, whether created manually or generated by AI, can sometimes be imperfect. They might contain incorrect or outdated locators, or they might be missing crucial steps needed to achieve the test’s objective. When these scripts were executed, they would simply fail, forcing the user into a difficult and time-consuming manual process of debugging, finding the broken locators, and identifying the missing logic.

The Fix:

We have introduced Context Based Execution, a powerful new AI-driven capability in Qyrus Recorder. Now, you can provide your high-level objective along with a potentially flawed test script. The AI engine (QTP) will then intelligently:

Heal incorrect locators by finding the correct elements on the page.
Add relevant missing steps by understanding the logical gaps in your test flow.
Proceed to complete the execution successfully using the corrected and completed script.

How will it help?

This feature acts as an AI co-pilot, dramatically accelerating your test creation and maintenance efforts.

Massively Reduce Maintenance: It goes beyond simple self-healing by fixing entire test flows, saving countless hours you would have spent debugging.

Create Tests Faster: You can start with an imperfect or incomplete script and let the AI intelligently correct and complete it, turning rough drafts into robust tests.

Increase Test Reliability: By fixing issues on the fly, it makes your test executions far more resilient to minor application changes or script errors.
Empower Your Team: It lowers the technical barrier for creating successful automated tests, allowing every team member to be more productive.

Improvement

Record Like a Human: Copy/Paste, TAB & ENTER Now Captured!

The Challenge: Previously, the Qyrus Recorder did not capture several common user actions when filling out web forms. Pasting text into a field was not recorded as a clean input, and crucial keyboard navigation like pressing TAB to move between fields or ENTER to submit a form was ignored. This forced users to manually add these steps after the recording was finished, which was time-consuming and made the recording process less intuitive.

The Fix:

We have significantly enhanced the Qyrus Recorder to make the recording experience more natural and complete. The recorder now automatically captures:

Copy & Paste: When you paste text into an input field, it is now recorded as a clean SET operation.

Keyboard Actions: Pressing the TAB and ENTER keys are now recognized and recorded as distinct steps in your script.

How will it help?

This update will save you a tremendous amount of time, especially when recording interactions with login pages or other large forms. You can now record the workflow exactly as you would perform it manually—pasting long values, tabbing between fields, and hitting enter to submit. This eliminates the need for numerous manual clicks and post-recording edits, creating a more accurate and complete test script from the very beginning and streamlining your entire automation workflow.

Improvement

At-a-Glance Clarity: qAPI Functional Reports Get a Major Upgrade!

The Challenge:

Previously, our qAPI functional reports had two main areas for improvement. First, an API test executed without any assertions could be ambiguously reported, not clearly indicating that no actual validation occurred. Second, users had to click into a detailed report to see the crucial HTTP status code of an API response, making it difficult to quickly assess results from the main overview page.

The Fix:

We have introduced two significant improvements to the functional reports page:

New “No Test Cases” Status: A new status, “No Test Cases,” will now be displayed for any API test that is run without any assertions.

New “Status Code” Column: We’ve added a “Status Code” column that provides an at-a-glance view of the API response. It includes a tooltip explaining the code’s meaning and uses a smart icon to indicate when an execution contains multiple APIs with the same or different status codes.

How will it help?

These enhancements provide you with richer, more actionable reports.

The “No Test Cases” status encourages better testing practices by clearly highlighting tests that need validation criteria to be meaningful.

The “Status Code” column saves you valuable time by providing critical response information directly on the main reports page, allowing for faster analysis and quicker identification of potential issues without needing to dig into detailed reports.

New Feature

From Complex to Clear: AI-Generated Summaries for Your API Workflows!

AI-Generated Summaries for Your API Workflows

The Challenge:

Complex, multi-step API workflows, especially those created by automated features like Automap, can be difficult to understand at a glance. When a team member creates a new workflow, others in the workspace might have to manually analyze each step to grasp its overall purpose and logic, which can hinder collaboration and slow down reviews.

The Fix:

We have introduced a new AI Summary feature for qAPI workflows. This powerful feature automatically generates a concise, human-readable summary that explains the purpose and flow of the operations within a workflow. This summary provides an immediate, high-level overview of the test asset.

How will it help?

This feature significantly improves collaboration and understanding within your workspace.

Instant Clarity: It makes it easy for any team member to quickly understand what a workflow does without dissecting it.

AI Transparency: It works perfectly with features like Automap, providing a clear explanation of what the AI has built.

Faster Reviews: Peer reviews are more efficient, as the context is clear from the start.

Auto-Documentation: The summary acts as instant documentation, ensuring the purpose of your test assets is always well-understood.

New Feature

Power Up Your Pipeline: Trigger qAPI Functional Tests Directly from Jenkins!

The Challenge:

Previously, users who rely on Jenkins for their CI/CD pipelines lacked a simple, native way to trigger their qAPI functional tests. Integrating these tests required complex workarounds like custom API scripts, creating a disconnect between the build/deployment process in Jenkins and the API testing process in Qyrus, and hindering true end-to-end automation.
The Fix:
We have now released a dedicated Jenkins plugin for qAPI. This plugin provides a simple and configurable build step that allows users to easily select and trigger their qAPI functional tests directly from within any Jenkins pipeline job.

How will it help?

This plugin provides seamless CI/CD integration, enabling true Continuous Testing. You can now:

Fully Automate Testing: Automatically trigger your API functional tests as a standard part of your build and deployment process.

Get Faster Feedback: Immediately validate your services post-deployment to catch issues earlier in the development cycle.
Eliminate Manual Work: Remove the need for brittle, custom scripts, saving significant time for your DevOps and development teams.

Ready to Accelerate Your Testing with August’s Upgrades?

Curious to see how these August enhancements can benefit your team? There’s no better way to understand the impact of Qyrus than to see it for yourself.

Ready to dive deeper or get started?

Book a Personalized Demo Today

Start Your Free Qyrus Trial

Welcome to our August update! At Qyrus, we are driven by the goal of making every aspect of your testing journey more efficient, powerful, and intuitive. This August, we’ve delivered a host of significant upgrades with a special focus on overhauling the entire API testing experience, creating more powerful and resilient test automation, and enhancing overall platform reliability. From simplifying how you create and preview APIs to making your automated tests smarter and more robust, these updates are designed to remove friction and accelerate your path to delivering quality.

New Feature

Power Up Your Iterations: Introducing Nested Loops for Web Testing!

Nested Loops 1

The Challenge:

Previously, users could not place one loop inside another, which made it difficult to automate complex scenarios requiring nested iterations. For example, testing every available size (inner loop) for every T-shirt style in a list (outer loop) would require complicated test structures or manual duplication of steps, which was inefficient and hard to maintain.

The Fix:

We have now introduced support for one-level nested loops in Web Testing. This allows users to place one loop directly inside another loop, enabling a more powerful and intuitive way to structure tests that need to iterate through multiple, related data sets.

How will it help?

This feature significantly enhances your ability to automate complex test scenarios. It helps you:

Automate Complex Scenarios: Easily handle tests that involve multiple, dependent data sets, like checking all links within each section of a webpage.

Save Time: Avoid duplicating test steps by creating elegant, nested loop structures that are more efficient to build and maintain.

Ensure Better Test Coverage: Systematically test all combinations between two sets of data, leading to more thorough and comprehensive test coverage with less effort.

Improvement

Resilient Loops: Gather All Results, Even with Failures!

Resilient Loops

The Challenge:

Previously, if a single step failed within a loop iteration, the entire loop would stop executing. This was problematic for data-driven tests where the goal is to process an entire dataset and see results for every item, as a single failure would prevent subsequent iterations from running and leave you with an incomplete report.

The Fix:

We have introduced a “Continue on Failure” option for loops in Web Testing. When this setting is enabled, a failure in one iteration will be logged in the report, but it will not halt the execution. The loop will proceed to the next iteration until all have been attempted.

How will it help?

This feature makes your automated tests more resilient and your results more comprehensive. It ensures that all iterations of your loop will run even if some fail, which is crucial for testing with dynamic data sets. This allows for complete, uninterrupted automation and provides a full execution report detailing the success or failure of every single iteration, giving you a complete picture of your test outcomes.

New Feature

Rock-Solid iOS Recordings: Video Service Upgraded for High-Volume Testing!

The Challenge:

Our iOS video recording service could become unstable under sustained, high usage. When a large number of parallel sessions were run (e.g., 500+ recordings over a few days), the service would sometimes stop accepting new recording requests. This resulted in situations where test reports were generated without the crucial corresponding video recording, hindering debugging and analysis.

The Fix:

Instead of relying on temporary server restarts, we have permanently addressed the root cause by re-architecting and optimizing the iOS video recording service. This enhancement ensures the service can now robustly handle a high volume of concurrent recording requests without degrading.

How will it help?

This update delivers significantly improved reliability and stability for iOS video recordings in Device Farm. You can now run numerous parallel test sessions with the confidence that a video recording will be successfully generated for each one, even during periods of peak usage. This ensures you always have the complete visual artifacts you need for thorough debugging and analysis.

Improvement

Reliable iOS Manual Sessions with Improved Connectivity

The Challenge:

Users attempting to start a manual testing session with an iOS device would sometimes encounter errors that prevented the session from launching successfully. These failures were often caused by underlying connectivity issues between our servers and the physical iOS devices in our device farm.

The Fix:

We have implemented and deployed key configuration changes on our backend servers to specifically address and resolve these connectivity problems. These adjustments create a more stable and robust connection pathway to our iOS devices.

How will it help?

This fix significantly improves the reliability of initiating manual sessions for iOS devices. You should now experience fewer session creation failures, allowing you to start your manual testing sessions more quickly and dependably, leading to a smoother and more efficient testing experience.

New Feature

Effortless API Setup: Introducing the New, Intuitive qAPI Form!

Introducing the New Intuitive qAPI Form

The Challenge:

The previous form for manually entering API details could sometimes be complex or less than intuitive, especially for users who were not deeply technical. This could slow down the process of adding new APIs to the platform and might have presented a barrier for team members like manual testers or business analysts.

The Fix:

We have completely redesigned the form where users enter API details in qAPI. The new design streamlines the entire process from start to finish, with a strong focus on making it more intuitive and user-friendly for everyone.

How will it help?

This revamp significantly improves the user experience for manually creating APIs. The new, intuitive layout guides users through the process more clearly, making it faster and easier to add and configure APIs. This is especially beneficial for non-technical users, as it lowers the barrier to entry and empowers more team members to participate in setting up API tests, reducing errors and saving time.

Improvement

Enhanced API Versatility: Full Support for x-www-form-urlencoded

The Challenge:

Previously, our API testing capabilities did not include native support for the x-www-form-urlencoded body type. This is a common data format used by web applications, especially for submitting form data. Users who needed to test APIs that required this specific content type had to rely on custom workarounds or external tools, creating an efficiency gap in their workflow.

The Fix:

We have now added native support for the application/x-www-form-urlencoded body type within our API testing service. Users can now select this option and easily build their request using key-value pairs, just as they would with a standard web form.

How will it help?

This enhancement significantly expands the range of APIs you can test directly on our platform. It simplifies the process of testing endpoints that mimic web form submissions, eliminating the need for complex workarounds. This makes our API testing tool more versatile and ensures you can cover a broader spectrum of your application’s endpoints with ease and efficiency.

New Feature

From API to IDE: C# HttpClient Code Snippets Now Available!

C# HttpClient Code Snippets

The Challenge:

Previously, while our code snippet feature supported various languages, it lacked an option for C# developers using the standard HttpClient library. This meant C# developers had to manually translate the API requests they designed or tested on our platform into the necessary C# code, a process that could be time-consuming and prone to manual error.

The Fix:

We are expanding our code snippet generation capabilities with the addition of a new target: C# (HttpClient). Now, with a single click, users can instantly generate the C# code required to execute their configured API request using this popular library.

How will it help?

This feature provides a significant productivity boost for C# and .NET developers. It eliminates the need to write boilerplate HttpClient code for API requests, saving time and reducing the chance of transcription errors. Developers can now quickly generate and integrate tested API calls directly into their applications, streamlining the workflow from API design and testing to implementation.

Improvement

QAPI – under— Your Test Results, Delivered: Email Reports for Scheduled Executions!

The Challenge:

Previously, after scheduling a test execution, users had to manually return to the platform to check its status and retrieve the report once it was finished. There was no automated notification system to inform them of a successful completion or, more critically, if a test failed to start due to issues like an insufficient Virtual User Balance (VUB).

The Fix:

We have implemented an automated email notification system for all scheduled test executions. Now, when a scheduled test completes successfully, users will automatically receive an email with a downloadable report attached. Additionally, if a test fails to run because of an insufficient Virtual user balance, a specific alert email will be sent to notify the user of the issue.

How will it help?

This feature makes monitoring your scheduled tests effortless and proactive. You no longer need to manually check on test progress; results are delivered directly to your inbox for easy access and sharing. The immediate failure alerts for VUB issues are crucial for quickly resolving resource problems and ensuring your testing schedule proceeds without interruption, saving time and preventing missed test runs.

Ready to Accelerate Your Testing with August’s Upgrades?

Curious to see how these August enhancements can benefit your team? There’s no better way to understand the impact of Qyrus than to see it for yourself.

Ready to dive deeper or get started?

Book a Personalized Demo Today Start Your Free Qyrus Trial

Welcome to the July edition of our platform updates! At Qyrus, our mission is to constantly evolve our platform, providing your teams with powerful, intuitive tools that streamline every phase of the quality lifecycle. This July, we’ve been laser-focused on delivering enhancements that bring you deeper workflow integrations, next-level AI automation, and foundational improvements to security and performance. These updates are designed to connect your existing tools seamlessly, accelerate test creation like never before, and give you even greater confidence in your testing environment.

Let’s explore the powerful new features we’ve rolled out across the Qyrus platform this July!

New Feature

Unleash Iterative Power: Now Create Loops Inside Your Functions!

The Problem:

Previously, users could not place a loop inside a function. This meant that any reusable logic requiring iteration over data or web elements could not be encapsulated within a single, self-contained function. Users would have to build the loop structure outside the function, making the test less modular and harder to read.

The Fix:

Support for loops within functions has been introduced for Web Testing. Users can now create loops directly inside a function’s logic, allowing them to perform iterative actions within the function’s context. However, to prevent potential infinite loops or overly complex structures, a function that contains a loop cannot itself be placed inside another loop.

How does it help?

This enhancement significantly improves the power and modularity of functions. Users can now create more complex and self-contained reusable components that handle their own iterative logic (e.g., a function to process all rows in a specific table). This leads to cleaner, more organized test scripts, reduces code duplication, and makes sophisticated, repeatable actions easier to build and maintain.

Loop

New Feature

Stay Logged In: Introducing Session Persistence in Test Orchestration!

TO - Session persistence

The Problem:

Previously, when running a sequence of test cases in Test Orchestration, each test would typically start with a fresh session. This made it challenging to execute true end-to-end (E2E) test scenarios that required a continuous, logged-in state or maintained context to flow from one test case to the next, often forcing users to repeat login or setup steps in every script.

The Fix: Test Orchestration now supports session persistence for both web and mobile nodes. This feature can maintain a continuous session for up to 24 hours across multiple test cases within a single workflow.

How does it help?

This is a game-changer for end-to-end testing. Users can now build and run complex workflows where the application state and user session are seamlessly carried over from one test case to the next. This eliminates redundant login steps, simplifies the creation of sophisticated E2E scenarios (like adding an item to a cart in one test and checking out in another), and makes your testing more efficient and powerful.

Improvement

Your Reports, Anywhere: Introducing Portable Offline HTML Reports!

TO-Download HTML Report

The Problem: Previously, reviewing or sharing detailed test results from Test Orchestration could require an active internet connection to access the platform. There was a need for a simple, comprehensive reporting format that could be easily saved, shared, and reviewed offline without losing crucial visual context like screenshots.

The Fix: We have introduced a new report generation feature in Test Orchestration. This feature creates a comprehensive, standalone HTML report for your test executions. Crucially, this single HTML file automatically includes all relevant screenshots from the test run embedded directly within it.

How does it help? This provides a highly portable and convenient way to manage test results. Users can now download a single file that can be easily shared via email or saved for archival purposes. Since the report is self-contained and includes all screenshots, it can be viewed offline at any time, making it much easier to analyze results, debug issues, and share detailed findings with team members regardless of their internet access.

Improvement

Your Key, Your Way: Define Project Keys Instantly When Cloning!

The Problem: Previously, when cloning a project in Test Orchestration, the system would likely assign a default, auto-generated key to the new project (e.g., “COPY_OF_PROJECT_KEY”). This forced users to perform an extra, manual step after the cloning process to go into the project settings and edit the key to match their desired naming conventions.

The Fix: We have enhanced the project cloning workflow in Test Orchestration. Users are now presented with an option to input a new, custom Project Key of their choice directly during the cloning process.

How does it help? This update streamlines the project setup and duplication process, making it more efficient. Users can now immediately assign a meaningful and compliant Project Key to a cloned project without any follow-up steps. This saves time, reduces administrative overhead, and ensures that projects are organized with the correct identifiers from the moment they are created.

Improvement

Smarter Self-Healing: Healer 2.0 Gets a Major Accuracy Boost!

The Problem: Previously, the Healer 2.0 functionality might have had difficulty healing locators for elements that were not clearly associated with a traditional anchor element. Furthermore, its healing algorithm sometimes relied more heavily on the natural language step description than the locator itself, which could occasionally lead to less accurate suggestions, especially on pages with multiple similar-looking elements.

The Fix: We have significantly improved the Healer 2.0 engine for Web Testing with two key enhancements:

Broader Element Recognition: The Healer can now identify and heal locators for elements using common, unique attributes like id, name, and data-testid, even if they aren’t surrounded by a traditional anchor.

More Precise Healing Logic: The algorithm has been updated to lean more heavily on the attributes of the original failed locator as the primary source of truth. The step description is now used as a powerful secondary tool to pinpoint the correct element, especially in ambiguous cases where multiple potential matches exist.

How does it help? This makes our self-healing capability much more powerful, accurate, and reliable. By better understanding modern web attributes like data-testid and prioritizing the locator’s original intent, Healer 2.0 can now fix a wider range of broken locators with greater precision. This leads to more resilient automated tests that can better withstand minor UI changes, ultimately reducing test flakiness and saving you significant time on maintenance.

Improvement

From Story to Scenario, Instantly: TestGenerator Integrates with Azure DevOps & Rally!

The Problem: Previously, users who manage their development lifecycle with tools like Azure DevOps or Rally had a manual gap in their workflow. They could not directly use our AI-powered TestGenerator to create test scenarios from their user stories, tasks, or bug reports residing in those platforms, requiring them to copy-paste or manually recreate context to generate tests.

The Fix: We have expanded the capabilities of TestGenerator on Web to now support direct integration with Azure DevOps and Rally. This allows users to connect to their accounts on these platforms and select work items (like user stories, tasks, bugs, etc.) as the source for test generation.

How does it help? This integration creates a seamless and powerful bridge between your requirements management and test creation processes. You can now save significant time and effort by automatically generating relevant test scenarios directly from your existing work items in Azure DevOps and Rally. This eliminates manual data transfer, reduces the risk of errors, improves traceability from requirement to test, and dramatically accelerates your workflow from user story to executable test case.

AI - Test Generator Rally

Improvement

From Scenario to Script, Instantly: TestGenerator Now Creates Manual Steps!

The Problem:

Previously, when TestGenerator generated a test scenario (e.g., “Verify user can log in”), it provided the high-level test idea. However, users still had to manually interpret that scenario and write out all the individual, sequential steps required to execute it (e.g., 1. Navigate to URL, 2. Enter username, 3. Enter password, 4. Click login). This manual translation from a test idea to an actionable script was a time-consuming step in the test creation process.

The Fix:

We have significantly enhanced TestGenerator’s capabilities. For every test scenario it generates, it now also automatically creates a complete, logical sequence of Manual Test steps that outlines the flow of the test.

How does it help?

This is a massive workflow accelerator. Instead of just giving you a test idea, TestGenerator now provides an entire, ready-to-use test script blueprint. Your task is simplified from writing steps from scratch to simply validating the generated flow and adding your locators. This dramatically reduces manual effort, speeds up the time it takes to create a runnable automated test, and bridges the gap between a high-level test concept and a concrete, actionable test case.

AI - Manual Steps

Ready to Accelerate Your Testing with July’s Upgrades?

This July, we’re bringing you deeper workflow integrations, more powerful AI automation, and significant security and performance enhancements designed to streamline your entire testing process. From automatically generating detailed manual test steps with TestGenerator and enabling seamless end-to-end tests with session persistence, to connecting directly with Azure Data Lake and integrating with Azure DevOps and Rally, these updates are built to boost your team’s productivity. We are dedicated to evolving Qyrus into a platform that not only anticipates your needs but also provides practical, powerful solutions that help you release top-quality software with greater speed and confidence.

Curious to see how these July enhancements can benefit your team? There’s no better way to understand the impact of Qyrus than to see it for yourself.

Ready to dive deeper or get started?

Book a Personalized Demo Today Start Your Free Qyrus Trial

At Qyrus, our commitment is to continuously advance our platform, equipping your teams with cutting-edge tools, simplifying complex testing processes, and making the path to quality clearer and more accessible. June has been another month of dedicated development, bringing forth a wave of innovative features and critical enhancements designed to offer you expanded data connectivity, deeper AI-driven insights, and more refined control across your entire testing journey. These updates are crafted to significantly boost your efficiency and provide unparalleled visibility into your applications.

Let’s dive into the latest capabilities we’ve integrated into the Qyrus platform this June!

Improvement

Loop Smarter: Combine Static & Dynamic Data in Your Web Locators!

The Problem:
Previously, users encountered difficulties when trying to automate interactions with dynamic web elements, like tables or lists, within a loop. Crafting locators that could adapt to changing element attributes or indices during each iteration was cumbersome, often requiring users to code complex workarounds or limiting the ability to create truly flexible, data-driven tests for these common web structures.

The Fix:
We have enhanced our web testing capabilities by enabling the combination of both dynamic (variable data, e.g., from a loop’s iteration or a data source) and static (user-defined text) input within the locator field for steps inside a loop. This allows for the construction of adaptive locators on the fly.

How does it help:
This provides significantly more flexibility in web test automation. Users can now easily iterate over dynamic elements such as rows in a table or items in a list where part of the locator remains constant while another part changes with each iteration. This enables the creation of more robust, data-driven locators, simplifying the automation of complex web scenarios and making tests easier to maintain.

Improvement

Enhanced Run Visibility for Web Tests

The Problem:
Previously, when automating repetitive sequences of actions within a loop for web testing, users might have had to duplicate those steps for each iteration or for similar loops. This could lead to longer, more complex test scripts that were harder to maintain and less efficient, especially when a common set of operations needed to be performed repeatedly within the loop’s context.

The Fix:
We have enhanced our Web Testing capabilities by introducing support for executing functions within a loop. Users can now incorporate the “Execute Function” action type directly inside a loop, allowing them to call pre-defined, reusable functions during each iteration of the loop.

How does it help:
This significantly boosts the modularity, reusability, and maintainability of web test scripts. Users can encapsulate common or complex sequences of actions into a single function and then call this function repeatedly within a loop, or across different loops. This leads to cleaner, more concise test scripts, reduces redundancy, simplifies updates, and ultimately makes automated web tests more efficient and easier to manage.

New Feature

New MongoDB Connector: Unlocking NoSQL & Semi-Structured Data Testing

The Problem:
The data testing platform previously lacked direct support for semi-structured and NoSQL data sources like MongoDB. This meant users could not easily ingest, compare, or evaluate data from MongoDB instances, nor could they readily perform structured and nested validations on real-world JSON-like datasets within the platform.

The Fix:
A MongoDB Connector is being introduced to the data testing platform. This connector will allow users to connect to MongoDB instances and ingest data specifically for use in Compare and Evaluate jobs.

How does it help:
This new connector enables users to work with semi-structured data from MongoDB, allowing for structured and nested validations on JSON-like datasets. It serves as a foundation for testing nested documents and supports advanced use cases such as comparing MongoDB documents against other data sources (like flat files or relational tables), evaluating fields using various assertion types, and integrating with an upcoming nested comparison framework.

Improvement

Dry Run Delight: SQL Connectors Enhanced with LIMIT & OFFSET!

The Problem:

Previously, when configuring SQL connectors for tables or queries, users might not have had a direct way to restrict the number of rows fetched for initial testing or validation purposes. This meant that to test data mappings, transformations, or query logic, they might have had to process entire datasets, which could be slow and resource-intensive, especially during the development and dry run phases.

The Fix:

We have improved our SQL connectors to now support the use of LIMIT and OFFSET clauses directly within the table and query configuration settings. This allows users to specify the maximum number of rows to retrieve (LIMIT) and the starting point for data retrieval (OFFSET) when setting up their data connections.

How does it help:

This enhancement significantly improves efficiency, particularly for testing and validation. Users can now easily configure “Dry Run” setups to fetch and process only a small, manageable portion of their data. This enables them to quickly validate their data mappings, transformations, and query logic without the overhead of processing full datasets, leading to faster iteration cycles, reduced resource consumption during development, and more agile data pipeline testing.

Improvement

Unified Workflow Playback: Single Video for Web & Mobile Executions!

The Problem:
Previously, when reviewing test executions for workflows in Test Orchestration that involved both Web and Mobile services, users might have had to access and manage separate video recordings for each service. This fragmented approach could make it cumbersome to get a holistic, end-to-end report of the entire workflow.

The Fix:
We’ve introduced a significant enhancement to our consolidated reporting in Test Orchestration: a single video per workflow execution. This means that for workflows involving both Web and Mobile services, a single, consolidated video recording will be generated, seamlessly combining the visual recordings from both service interactions into one comprehensive playback.

How does it help:
This feature provides users with a unified and complete visual record of their entire workflow execution from start to finish, all in one place. It greatly simplifies the review process, making it easier to understand the full user journey across different platforms (Web and Mobile).

Improvement

Streamlined Test Setup: Run All Nodes in a Global Environment

Run All Nodes in a Global Environment

The Problem:

Previously, users were required to select an environment for each individual node within their test configurations. While this offers granular control for complex multi-environment testing scenarios, it proved to be an inconvenience and time-consuming for users who primarily operate with a single, consistent environment (like a global or default one) across all nodes, or those who simply wanted a quick way to run everything against a standard setup.

The Fix:

To address this, we have added a Global Environment toggle. When activated, this option will allow users to run all nodes in their test configuration using the respective “Global Environment” defined for each service, bypassing the need for individual environment selection for each node.

How does it help:

This enhancement will significantly simplify and speed up the test configuration process for many users. It offers a convenient one-click solution for those who wish to execute all their test nodes against a pre-defined global or default environment, reducing repetitive manual setup and saving valuable time. This leads to a more streamlined user experience, especially for large test suites or when a uniform environment strategy is applied.

Improvement

Branch Hub Gets Literal: Compare Directly with Static String Values!

The Problem:

Previously, when defining conditional rules within the Branch Hub, users might have faced limitations or complexities if they needed to compare a variable directly against a specific, fixed string value (a string literal). This could require workarounds, such as pre-defining the static string as another variable, making the rule creation process less intuitive or direct for common scenarios like checking if a status variable equals “Completed” or a type field matches “Urgent.”

The Fix:

We have enhanced Branch Hub to directly support the use of static string literals in comparison operations. This means users can now easily define rules by comparing a variable with a fixed string value directly entered into the condition, for example, Variable_Name == “Your Static Text”.

How does it help:

This update significantly simplifies the process of creating and managing rules in Branch Hub. Users can now more intuitively and directly define conditions based on specific text values without needing intermediate steps. This enhances the flexibility and clarity of rule definitions, making it easier to implement precise conditional logic for workflows.

Improvement

Enhanced Control: Skip Support Added for Parameterized Mobility Tests

The Problem:

Clients were unable to skip individual test cases within their parameterized Mobility test executions when running them through Test Orchestration. This lack of control meant all defined iterations of a parameterized test would execute, even if some were not relevant for a specific test run.

The Fix:

A validation has been added to the Mobility Framework specifically for Test Orchestration executions. This validation checks for the presence of a tilde (‘~’) character in parameterized test cases. If this character is detected, that particular parameterized step (test case or iteration) is skipped during execution and is also excluded from the test report.

How does it help:

This feature allows clients to customize their parameterized test executions more effectively within Test Orchestration. They can now selectively exclude specific test cases or iterations from a run, leading to more focused testing, faster execution times for relevant scenarios, and cleaner reports that only reflect the desired test scope.

Heads Up! In-App Alerts for Deployments & New Feature Highlights

Improvement

The Problem:

Keeping users promptly informed about important events like ongoing system deployments (which might temporarily affect service) or the release of exciting new features could be challenging using traditional communication methods alone. Users might miss external announcements, leading to potential confusion during maintenance periods or slower adoption of newly added functionalities.

The Fix:

We have integrated a tool that enables us to display timely popups or snippets directly to users within the application. These in-app notifications will be used to proactively inform users about ongoing deployments and to highlight when new features have been added to the platform.

How will it help?

This new communication channel ensures users receive critical information and exciting news directly where they are working – within the application itself. It will improve awareness of ongoing deployments, potentially reducing confusion or support queries during maintenance windows.

Other Enhancements

We have resolved underlying issues concerning the lifecycle management of dedicated browser frameworks. This involves ensuring these frameworks are now correctly and reliably allocated when needed, properly deallocated after use to free up resources, and effectively renewed when required, leading to a more robust management process.

We have identified and resolved the problem that was hindering the system user re-invitation process. The fix ensures that when a system user is reinvited, they now properly receive the new invitation and can respond to it as expected, allowing them to join or re-access the system.

We have corrected the functionality responsible for displaying the assigned team list in the user profile section. The system now accurately fetches and presents the user-to-team mappings, ensuring that the teams listed in a user’s profile are a true representation of their current assignments.

We have now added the download options for Qloud-Bridge and Q-Spy (for various operating systems) to the new navbar. These essential links are now correctly integrated and visible within the main navigation structure.

We have standardized the “view password” option across all relevant password set and password reset pages. This ensures that the functionality to toggle password visibility is consistently present and functions uniformly wherever users are required to create or update their passwords.

Virtual User Balance (VUB) – Test Your APIs Like Real Users

The Problem:

Traditional API testing often focuses on a single interaction or low-volume scenarios. But real-world usage rarely works that way. When hundreds or thousands of users interact with your system at once, you need to know whether your API will hold up—or fall apart. Until now, simulating realistic traffic patterns and usage concurrency required custom setups or third-party integrations.

The Fix:

With the new Virtual User Balance (VUB) system, qAPI now allows you to simulate up to 1,000 virtual users interacting with your API simultaneously—no external tools or custom load scripts required. Each project receives a monthly allocation of “virtual user credits” that can be used across all your test suites and environments.

Whether you’re stress testing for scale or validating business workflows under pressure, you can now launch realistic, high-volume test scenarios with a single click.

How will it help?

Test Like It’s Production: Simulate real-world concurrency and see how your API behaves under pressure.

One Click, No Setup: No need to build custom load test infrastructure—just launch and go.

Shared Monthly Credits: Use your virtual user balance across all projects and teams efficiently.

Collaboration – Work Together on API Projects

The Problem:

Previously, API testing in qAPI was a solo experience. Users couldn’t easily collaborate or share resources, which created silos and duplicated work. Teams working on the same API had to manage separate environments, data sets, and test runs—slowing down delivery and increasing friction.

The Fix:

With the new Shared Workspaces feature, qAPI users can now invite teammates to collaborate on API projects in real time. Projects can still remain private, but when shared, everyone in the workspace can access the same collections, tests, environments, and virtual user credits.

It’s a seamless way to go from individual testing to true team collaboration—similar to switching from emailing files to working together in Google Docs.

How will it help?

Faster Collaboration: Multiple users can contribute to the same project, in the same environment.

Shared Resources: Pool test credits and environments across the team for better efficiency.

Flexible Privacy: Keep projects private when needed or open them up for collaboration.

cURL Code Snippet – Copy and Paste Ready Code

The Problem:

Even after testing an API successfully, developers often had to manually recreate the same request logic in their application code—copying headers, payloads, and endpoints by hand. This was time-consuming and error-prone, especially for more complex APIs.

The Fix:

qAPI now lets you instantly generate a copy-paste-ready cURL snippet for any API request you’ve built and tested. This allows developers to take working API calls and drop them directly into scripts, documentation, or terminals—without having to rewrite a single line.

Support for additional languages and code frameworks is coming soon.

How will it help?

Save Developer Time: No more recreating tested calls—just copy and go.

Reduce Errors: Eliminate the risk of typos or config mismatches in code.

Boost Developer Velocity: Get working API logic into your application faster.

Beautify – Make Messy Code Look Clean

The Problem:

APIs return data in formats like JSON, XML, or GraphQL—but the output is often compressed, unformatted, and hard to read. Manually formatting these responses takes time and increases the risk of missing bugs or misinterpreting structure.

The Fix:

qAPI now includes a Beautify feature that automatically reformats messy API request or response bodies into clean, readable, indented formats. It detects the content type (JSON, XML, GraphQL), and only activates when there’s something to format. If you’re working with plain text or already clean content, it stays out of the way.

How will it help?

Readability First: Instantly make complex API responses human readable.

Smarter Formatting: Only runs when needed and adapts to the data type.

Ready to Leverage June’s Innovations?

This June, Qyrus is putting enhanced connectivity, deeper AI intelligence, refined user control, and greater operational efficiency directly at your fingertips. From seamlessly integrating with NoSQL databases like MongoDB and generating complex test code from natural language with our advanced AI, to gaining precise control over visual comparisons with new ignore-region capabilities, every new feature is engineered to elevate your testing strategy. We are committed to providing a unified platform that not only adapts to your evolving needs but also streamlines your critical processes, empowering you to release high-quality software with greater speed and confidence.

Eager to explore how these June advancements can transform your testing efforts? The best way to appreciate the Qyrus difference is to experience these new capabilities directly.

Ready to dive deeper or get started?

Book a Personalized Demo Today Start Your Free Qyrus Trial

At Qyrus, we’re relentlessly focused on evolving our platform to empower your teams, streamline your workflows, and make achieving quality more intuitive than ever before. May was a busy month behind the scenes, packed with exciting new features and significant enhancements designed to give you even more power and flexibility in your testing journey. Here’ re the latest advancements we’ve rolled out across the Qyrus platform!

Excited to see these May power-ups in action? There’s no better way to understand the impact Qyrus can have on your testing journey than by experiencing it firsthand.

New Feature

Complex Web Tests, Now Powered by AI Genius!

The Problem:
Users had to manually write Java and JavaScript code for complex calculations within their web tests. This could be time-consuming, error-prone, and potentially require deep coding expertise.

The Fix:
A new AI feature has been introduced that can generate custom Java and JavaScript code snippets from natural language descriptions. This AI recognizes variables already set up in the test and integrates with existing “Execute JS,” “Execute JavaScript,” and “Execute Java” actions.

How does it help:
This feature eliminates the need for manual coding of complex calculations, saving time and effort. It makes creating these code snippets faster (“instantly”) and more accessible, even for users who might not be expert coders. Users still retain control as they can review, modify, or copy the generated code.

A quick note: This powerful AI code generation is currently a Beta feature, and we’re actively refining it based on your feedback!

Improvement

Enhanced Run Visibility for Web Tests

The Problem:
Enterprise clients lacked clear visibility into their test execution queues. They couldn’t see detailed information about their test runs, such as their exact position in the queue. This made it difficult to gain insights, plan effectively, and stay informed about the status of their tests.

The Fix:
Enhanced visibility into test execution queues has been introduced for enterprise clients. This allows them to see detailed information, including the exact position of their test run in the queue.

How does it help:
This feature provides enterprise clients with better insight into their test execution process. It enables them to plan more effectively by knowing when their tests are likely to run and helps them stay informed about the progress every step of the way.

Ready to Experience the May Power-Ups?

Excited to see these May power-ups in action? There’s no better way to understand the impact Qyrus can have on your testing journey than by experiencing it firsthand.

Ready to learn more or get started?

Book a Personalized Demo Today Start Your Free Qyrus Trial

QA Test Page

Tutorial Test Page

Buttons

Click Me Right Click Me Dbl Click Me Click Me – Then wait

Favorite Color:

Red

Yellow

Blue

Types of Tests:

Smoke Test

Functional Test

Integration Test

Unit Test

Acceptance Test

Nickname Pet’s Name Select Favorite Animal

Below this text is an iFrame with a True Random Number Generator.

Swap to the iFrame in order to click the "Generate" button!

Web Testing

Mobile Testing

Device Farm

qAPI Product Release Updates

AI Enhancements

Test Smarter, Not Harder: Impact Analyzer Now Supports Your qAPI Suites!

Ready to Accelerate Your Testing with October’s Upgrades?

Ready to dive deeper or get started?

Complex Web Tests, Now Powered by AI Genius!

Enhanced Run Visibility for Web Tests

Sharper Focus for Your Mobile Visuals

Device Farm: Smoother Streaming, Better Guidance

Desktop Testing: Schedule Your Success

Smarter AI for Broader Test Coverage

Ready to Experience the May Power-Ups?

Web Testing

Test Orchestration

Qyrus Recorder

qAPI Product Release Updates

Ready to Accelerate Your Testing with August’s Upgrades?

Ready to dive deeper or get started?

Web Testing

Device Farm

API Testing

qAPI Product Release Updates

Ready to Accelerate Your Testing with August’s Upgrades?

Ready to dive deeper or get started?

Web Testing

Desktop Testing

Test Orchestration

Device Farm

UM and Subscription

AI Enhancements

Data Testing

qAPI Product Release Updates

Ready to Accelerate Your Testing with July’s Upgrades?

Ready to dive deeper or get started?

Web Testing

Data Testing

Test Orchestration

Mobile Testing

Device Farm

AI Enhancements

User Management and Subscription

qAPI Product Release Updates

Ready to Leverage June’s Innovations?

Ready to dive deeper or get started?

Web Testing

Mobile Testing

Device Farm

Desktop Testing

AI Enhancements

Ready to Experience the May Power-Ups?

Ready to learn more or get started?

Tutorial Test Page

Favorite Color:

Types of Tests: