{"id":18905,"date":"2026-03-19T05:45:08","date_gmt":"2026-03-19T05:45:08","guid":{"rendered":"http:\/\/localhost\/webcasata\/surbhi\/qyrus\/?p=18905"},"modified":"2026-03-19T09:23:24","modified_gmt":"2026-03-19T09:23:24","slug":"v6-16-0-march-2026-release","status":"publish","type":"post","link":"https:\/\/symmetricsolutionz.co.in\/qyrus\/v6-16-0-march-2026-release\/","title":{"rendered":"V6.16.0 (March 2026 Release)"},"content":{"rendered":"

Welcome to our\u00a0March\u00a0update!\u00a0\u00a0<\/p>\n

As we move forward into the last month of the\u00a0fiscal year, our focus at\u00a0Qyrus\u00a0is on creating a more connected, insightful, and responsive testing ecosystem. This month, we are breaking down silos between your tests, enhancing your visibility across projects, and giving you absolute control over your test executions.\u00a0<\/p>\n

In Test Orchestration, we are thrilled to introduce the ability to seamlessly extract and pass data across different platforms\u2014like moving a dynamic variable from a mobile app straight into a web script\u2014unlocking true, uninterrupted end-to-end workflows.\u00a0We\u2019ve\u00a0also revamped our Reports page, resolving stability issues and bringing you multi-project filtering for a unified view of your quality metrics.\u00a0<\/p>\n

For our API Testing users,\u00a0we’ve\u00a0fortified the foundation with\u00a0highly reliable\u00a0JSON Path extraction for pre-request variables, turbocharged the workflow canvas performance, and added an essential “stop” mechanism to halt live performance tests on demand. Furthermore,\u00a0we\u2019ve\u00a0closed the collaboration loop by enabling automated execution report attachments directly within our Jira integration.\u00a0<\/p>\n

Alongside these major enhancements, we have also deployed a variety of bug fixes and minor improvements across Mobile Testing, Desktop Testing, Device Farm,\u00a0QloudBridge, our AI algorithms, and other core services to keep your entire testing operation running smoothly.\u00a0<\/p>\n

Let\u2019s\u00a0explore the powerful new capabilities available on the\u00a0Qyrus\u00a0platform this March!\u00a0<\/p>\n

\n\n\t\t\t\t\t Test Orchestration
\n\t\t\t<\/path><\/svg>
\n\t\t\t<\/path><\/svg>
\n\t\t\t\t\t\t<\/summary>\n

Bridge the Gap: Seamlessly Pass Extracted Data Across Workflows!\u00a0<\/h2>\n

\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"Extract\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/p>\n

The Challenge:<\/b>\u00a0\u00a0<\/p>\n

Previously, if you extracted a specific piece of text during a test\u2014like grabbing an order ID or a dynamic OTP from a mobile app screen\u2014that valuable data was trapped within that individual script. If the next step in your Test Orchestration workflow\u00a0was\u00a0a web script that needed to input that exact ID for validation, the data\u00a0couldn’t\u00a0make the jump. This limitation broke the chain in cross-platform end-to-end testing, forcing users to rely on static data or complicated external workarounds.\u00a0<\/p>\n

\u00a0The Fix:<\/b>\u00a0\u00a0<\/p>\n

We have introduced the ability to extract words from one script and pass them dynamically as inputs to the next node in Test Orchestration. Now, when you use the “Extract word” feature and assign it to a variable (for instance, in a mobile script), you can configure that variable as an Output. You can then seamlessly map it directly to the Input of a dependent node (like a web script) downstream.\u00a0<\/p>\n

How will it help?<\/b>\u00a0\u00a0<\/p>\n

This update unlocks true, uninterrupted end-to-end testing across different platforms and script types.\u00a0<\/p>\n

    \n
  • True Cross-Platform Flows:<\/b>\u00a0Easily create workflows that span platforms, such as generating a code on a mobile device and automatically verifying it on a web portal.\u00a0<\/li>\n<\/ul>\n
      \n
    • Dynamic Validation:<\/b>\u00a0Your tests can now react to and\u00a0utilize\u00a0real-time, dynamically generated data on the fly, making your validations much more robust and realistic.\u00a0<\/li>\n<\/ul>\n
        \n
      • Simplified Orchestration:<\/b>\u00a0Eliminate\u00a0the need for messy API workarounds or external databases just to pass a simple string of text between your testing steps.\u00a0<\/li>\n<\/ul>\n

        Unified Insights & Stability: Multi-Project Filtering and Smoother Reporting!\u00a0<\/h2>\n

        \t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"project\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/p>\n

        The Challenge:<\/b>\u00a0\u00a0<\/p>\n

        Previously, the Reports page presented two distinct usability hurdles. First, analyzing test results across different projects was a disjointed experience because you could only select one project at a time in the filters, forcing managers to stitch data together manually. Second, managing bulk executions caused platform instability; if you triggered multiple workflows and then\u00a0attempted\u00a0to abort them from the Reports page, the UI would continuously fluctuate and refresh erratically, making it incredibly difficult to interact with the system.\u00a0<\/p>\n

        The Fix:<\/b>\u00a0\u00a0<\/p>\n

        We have implemented a comprehensive UI\/UX overhaul for the Reports page. We added full support for\u00a0Multi-Project Selection<\/b>\u00a0in the filters section, allowing you to view and aggregate data across various projects simultaneously. Furthermore, we completely resolved the UI fluctuation bug, ensuring the page\u00a0remains\u00a0rock-solid and responsive even when processing abort commands for massive, multi-workflow executions.\u00a0<\/p>\n

        \u00a0How will it help?<\/b>\u00a0\u00a0<\/p>\n

        This update transforms how you track, analyze, and manage quality across your organization.\u00a0<\/p>\n

          \n
        • Holistic Visibility:<\/b>\u00a0Instantly view aggregated test execution metrics, passing rates, and statuses across your entire portfolio in a single, unified dashboard.\u00a0<\/li>\n<\/ul>\n
            \n
          • Seamless Interaction:<\/b>\u00a0Enjoy a stable, glitch-free reporting interface, allowing you to confidently manage and abort bulk runs without frustrating UI disruptions.\u00a0<\/li>\n<\/ul>\n
              \n
            • Eliminate\u00a0Manual Work:<\/b>\u00a0Stop wasting time toggling between individual project dashboards or fighting with a jumpy screen to get the insights you need.\u00a0<\/li>\n<\/ul>\n<\/details>\n
              \n\n\t\t\t\t\t API Testing
              \n\t\t\t<\/path><\/svg>
              \n\t\t\t<\/path><\/svg>
              \n\t\t\t\t\t\t<\/summary>\n

              Halt the Load: On-Demand Stop for Performance Tests!\u00a0<\/h2>\n

              \t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"stop\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/p>\n

              The Challenge:<\/b>\u00a0\u00a0<\/h5>\n

              Previously, once an API performance test was\u00a0initiated, it had to run its predetermined course. If you realized moments after clicking “Run” that you were targeting the wrong environment, or if the system under test began failing\u00a0immediately, you were locked in. The test would continue generating massive, unnecessary load, wasting your execution\u00a0resources\u00a0and potentially causing severe disruptions or accidental outages on your backend services.\u00a0<\/p>\n

              The Fix:<\/b>\u00a0\u00a0<\/h5>\n

              We have introduced a dedicated\u00a0“STOP Execution”<\/b>\u00a0option specifically for active API performance tests, complete with precise state tracking.\u00a0<\/p>\n

                \n
              • Targeted Visibility:<\/b>\u00a0The stop option is exclusively visible when the test is actively in the “Running” status. It is hidden during the “Run Initiated” or “Generating Reports” phases to prevent interrupting essential setup or teardown processes.\u00a0<\/li>\n<\/ul>\n
                  \n
                • Clear State Transitions:<\/b>\u00a0The moment you click “STOP Execution,” the report status\u00a0immediately\u00a0transitions to\u00a0ABORTING. Once the underlying framework successfully spins down the virtual users and fully halts the process, the final status officially\u00a0updates to\u00a0Aborted.\u00a0<\/li>\n<\/ul>\n
                  How will it help?<\/b>\u00a0\u00a0<\/h5>\n

                  This update gives you an essential, transparent emergency brake for your high-volume testing.\u00a0<\/p>\n

                    \n
                  • Protect Your Systems:<\/b>\u00a0Instantly cut off the load if a test starts negatively\u00a0impacting\u00a0shared environments, databases, or third-party services.\u00a0<\/li>\n<\/ul>\n
                      \n
                    • Save Resources:<\/b>\u00a0Stop wasting valuable execution minutes and concurrency slots on tests that are already known to be failing or misconfigured.\u00a0<\/li>\n<\/ul>\n
                        \n
                      • Confident Control:<\/b>\u00a0The clear UI state changes\u00a0eliminate\u00a0guesswork, providing immediate visual confirmation that your stop command was received and successfully executed.\u00a0<\/li>\n<\/ul>\n

                        Closing the Loop: Automated Report Attachments for Jira!\u00a0<\/h2>\n

                        The Challenge:<\/b>\u00a0\u00a0<\/h5>\n

                        Previously, when an API test failed and a bug was logged in Jira, the resulting ticket often lacked immediate, actionable context. Developers would see that a test failed, but to understand\u00a0why<\/i>, they had to leave Jira, log into\u00a0Qyrus, navigate to the specific project, and dig up the execution report to view the payloads, headers, and error messages. This constant context-switching slowed down the debugging process and created friction between QA and Development teams.\u00a0<\/p>\n

                        The Fix:<\/b>\u00a0\u00a0<\/h5>\n

                        We have significantly enhanced our\u00a0Jira integration<\/b>\u00a0to support the automatic attachment of execution reports. Now, when a Jira issue is created directly from a failed API test in\u00a0Qyrus, the comprehensive test report is automatically generated and attached directly to the Jira ticket.\u00a0<\/p>\n

                        How will it help?<\/b>\u00a0\u00a0<\/h5>\n

                        This update centralizes your debugging information where your developers already work.\u00a0<\/p>\n

                          \n
                        • Context-Rich Tickets:<\/b>\u00a0Developers instantly receive all the necessary technical details\u2014requests, responses, and validation failures\u2014attached right to the bug report.\u00a0<\/li>\n<\/ul>\n
                            \n
                          • Faster Bug Resolution:<\/b>\u00a0By\u00a0eliminating\u00a0the need to switch platforms and hunt for test data, your team can start fixing issues\u00a0immediately.\u00a0<\/li>\n<\/ul>\n
                              \n
                            • Streamlined Collaboration:<\/b>\u00a0It creates a single, undeniable source of truth within Jira, making communication between testers and developers much more efficient.\u00a0<\/li>\n<\/ul>\n

                              Flawless Data Prep: Reliable JSON Path Extraction for Pre-Requests! <\/h2>\n

                              \t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"JSON\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/p>\n

                              The Challenge:<\/b><\/h5>\n

                              Setting up\u00a0dynamic API tests often requires fetching and defining data before the main request even runs. Previously, when users tried to use the JSON Path extractor to pull specific values into\u00a0Pre-Request\u00a0variables, the system would sometimes fail to parse the payload correctly, resulting in an “undefined” value. This broken extraction caused\u00a0subsequent\u00a0API calls to fail unexpectedly\u2014such as missing an authentication token or a critical ID\u2014forcing users to spend time debugging test setups instead of the APIs themselves.\u00a0<\/p>\n

                              \u00a0The Fix:<\/b>\u00a0\u00a0<\/h5>\n

                              We have fully resolved the bug and\u00a0enhanced the capabilities of the JSON path extractor\u00a0specifically for\u00a0Pre-Request\u00a0variables.\u00a0The parsing engine has been upgraded to accurately evaluate your JSON paths and correctly capture the intended data, completely eliminating the “undefined” variable issue.\u00a0<\/p>\n

                              \u00a0How will it help?<\/b>\u00a0\u00a0<\/h5>\n

                              This update ensures your API tests are built on a solid foundation from the very first step.\u00a0<\/p>\n

                                \n
                              • Reliable Test Setup:<\/b>\u00a0Guarantee that your API requests always have the correct prerequisite data before they execute,\u00a0eliminating\u00a0false negatives.\u00a0<\/li>\n<\/ul>\n
                                  \n
                                • Dynamic Workflows:<\/b>\u00a0Confidently chain processes together, knowing that data extracted in the pre-request phase will be passed accurately to the main request.\u00a0<\/li>\n<\/ul>\n
                                    \n
                                  • Reduced Troubleshooting:<\/b>\u00a0Stop wasting time investigating “undefined” variable errors and focus your energy on actual API validations.\u00a0<\/li>\n<\/ul>\n<\/details>\n

                                    Bridge the Gap: Seamlessly Pass Extracted Data Across Workflows!\u00a0<\/h2>\n

                                    \t\t\t\t\t\t\t\t\t\t\t\t\t\"Extract\t\t\t\t\t\t\t\t\t\t\t\t\t<\/p>\n

                                    The Challenge:<\/b>\u00a0\u00a0<\/p>\n

                                    Previously, if you extracted a specific piece of text during a test\u2014like grabbing an order ID or a dynamic OTP from a mobile app screen\u2014that valuable data was trapped within that individual script. If the next step in your Test Orchestration workflow\u00a0was\u00a0a web script that needed to input that exact ID for validation, the data\u00a0couldn’t\u00a0make the jump. This limitation broke the chain in cross-platform end-to-end testing, forcing users to rely on static data or complicated external workarounds.\u00a0<\/p>\n

                                    \u00a0The Fix:<\/b>\u00a0\u00a0<\/p>\n

                                    We have introduced the ability to extract words from one script and pass them dynamically as inputs to the next node in Test Orchestration. Now, when you use the “Extract word” feature and assign it to a variable (for instance, in a mobile script), you can configure that variable as an Output. You can then seamlessly map it directly to the Input of a dependent node (like a web script) downstream.\u00a0<\/p>\n

                                    How will it help?<\/b>\u00a0\u00a0<\/p>\n

                                    This update unlocks true, uninterrupted end-to-end testing across different platforms and script types.\u00a0<\/p>\n