Web Testing<\/p>\n<\/summary>\nFlawless Connections: Enhanced iOS Device Streaming!<\/h2>\n
The Challenge:<\/b><\/p>\n
When using Test Generator v2 to automatically build test scenarios via integrations, any friction in the generation flow ruins the speed advantage of using AI. Previously, users faced two major hurdles: the\u00a0initial\u00a0streaming API could experience a bottleneck\u2014taking up to two minutes just to return a \u201cGenerating\u201d status\u2014and auto-generated variable actions lacked structural logic. If a script required multiple variables (e.g., Var 1 through Var 5), the AI\u00a0didn\u2019t\u00a0automatically cross-reference its memory to intelligently link those variables to\u00a0subsequent\u00a0data handler steps, forcing testers to manually patch the logic. Additionally, path values for generated steps were buried, making it tedious to audit the AI\u2019s structural paths.<\/p>\n
The Fix:<\/b><\/p>\n
We have rolled out critical enhancements to\u00a0Test Generator v2\u00a0<\/b>to\u00a0optimize\u00a0both backend performance and AI logic. We dramatically accelerated the\u00a0initial\u00a0stream\u00a0API response time, slashing the latency required to\u00a0initiate\u00a0a generation job. On the intelligence front, the AI now automatically names variables inside the \u201cCreate Variable\u201d action and intelligently maps those identical variable names to corresponding downstream data handler actions (such as Dynamic Set steps) by referencing its historical memory. Finally, we have explicitly included the exact path values right inside the info section of every step TG generates.<\/p>\n
How will it help?<\/b><\/p>\n
These intelligence and speed optimizations turn AI generation into a fluid, hands-off experience.<\/p>\n
\n- Instant Generation:<\/b>\u00a0No more waiting on spinning wheels. The optimized streaming API kicks off your AI generation jobs\u00a0almost instantly, accelerating your overall testing velocity.<\/li>\n<\/ul>\n
\n- Flawless End-to-End Variable Logic:<\/b>\u00a0The AI now handles multi-variable data mapping seamlessly. If your test scenario creates five variables, the system automatically tracks them in its memory and binds the correct variable to\u00a0subsequent\u00a0dynamic steps without manual intervention.<\/li>\n<\/ul>\n
\n- Transparent Step Auditing:<\/b>\u00a0With path values clearly visible in the info section of each generated step, you can\u00a0immediately\u00a0inspect, verify, and debug the exact navigation paths the AI mapped out.<\/li>\n<\/ul>\n
Seamless SAP Scripting: Real-Time Locator Access!<\/h2>\n
The Challenge:<\/b><\/p>\n
Building automated tests for complex SAP web interfaces (like SAP Fiori) requires highly specific, often intricate element locators. Previously, gathering these unique SAP locators meant testers had to\u00a0frequently\u00a0break their workflow\u2014jumping between separate recording sessions, external inspection tools, or complex documentation just to copy and paste the correct identifiers into their test steps. This context-switching drastically slowed down the test creation process and increased the risk of manual errors.<\/p>\n
The Fix:<\/b><\/p>\n
We have fully integrated\u00a0SAP Recorded Locators<\/b>\u00a0directly into the Web Testing builder. Now, while you are actively constructing your test steps on the canvas, you have immediate, real-time access to the specialized SAP locators you need without ever having to leave the test building interface.<\/p>\n
How will it help?<\/b><\/p>\n
This workflow enhancement removes the friction of testing complex SAP environments.<\/p>\n
\n- Accelerated Test Building:<\/b>\u00a0Say goodbye to context-switching. You can now design, configure, and assign the correct SAP locators fluidly within a single, unified workspace.<\/li>\n<\/ul>\n
\n- Pinpoint Accuracy:<\/b>\u00a0By pulling recorded locators directly into your builder, you significantly reduce the risk of typos or incorrect element identification, ensuring your tests are robust from the start.<\/li>\n<\/ul>\n
\n- Developer-Friendly Experience:<\/b>\u00a0This seamless integration makes building complex SAP web tests faster, more intuitive, and far less tedious for your automation engineers.<\/li>\n<\/ul>\n<\/details>\n\n
Desktop Testing<\/p>\n<\/summary>\nSeamless CI\/CD Integration: Jenkins & Azure Plugins for Desktop Testing!<\/h2>\n![\"Jenkins](\"https:\/\/symmetricsolutionz.co.in\/qyrus\/wp-content\/uploads\/2026\/05\/Jenkins-Azure-Plugins-for-Desktop-Testing.png\")
<\/h2>\n
The Challenge:<\/b><\/p>\n
As organizations modernize their deployment pipelines, manual testing interventions create significant bottlenecks. Previously, triggering automated scripts for Desktop applications required users to step outside of their primary CI\/CD workflows. Without native plugins for popular orchestration tools, teams had to rely on cumbersome manual triggers or complex, custom-built scripts to\u00a0initiate\u00a0their Desktop Testing suites, resulting in disjointed\u00a0delivery\u00a0pipelines and slower release cycles.<\/p>\n
The Fix:<\/b><\/p>\n
We have officially introduced dedicated\u00a0Jenkins and Azure DevOps plugins<\/b>\u00a0specifically for the Desktop Testing Service. These new plugins empower you to seamlessly trigger and manage your automated desktop application scripts directly from your existing CI\/CD pipelines, bringing the service up to parity with our Web, API, and Mobile testing offerings.<\/p>\n
How will it help?<\/b><\/p>\n
This integration bridges the gap between your desktop application builds and your automated testing ecosystem.<\/p>\n
\n- Unified Workflows:<\/b>\u00a0Manage your entire testing strategy\u2014across\u00a0Web, Mobile, API, and now Desktop\u2014from a centralized CI\/CD control plane.<\/li>\n<\/ul>\n
\n- Frictionless Automation:<\/b>\u00a0Automatically execute robust desktop automation scripts the moment a new build is deployed,\u00a0eliminating\u00a0manual handoffs and accelerating your time-to-market.<\/li>\n<\/ul>\n
\n- Developer Flexibility:<\/b>\u00a0Empower your engineering teams to seamlessly embed desktop quality gates into the familiar Jenkins or Azure environments they already use every day.<\/li>\n<\/ul>\n
Continuous Execution: Connect to Existing SAP Windows!<\/h2>\n
![\"Connect](\"https:\/\/symmetricsolutionz.co.in\/qyrus\/wp-content\/uploads\/2026\/05\/Connect-to-Existing-SAP-Windows.png\")
<\/p>\n
The Challenge:<\/b><\/p>\n
When automating complex desktop workflows within SAP GUI, test scripts traditionally\u00a0forced\u00a0a brand-new application instance to launch for every execution. If a test failed midway or if an engineer wanted to resume a specific sequence after manual intervention, they were forced to restart the entire SAP login and navigation flow from scratch. This rigid behavior created duplicate windows, consumed unnecessary system resources, and drastically slowed down test debugging and multi-step process validations.<\/p>\n
The Fix:<\/b><\/p>\n
We have implemented powerful session persistence capabilities within the Desktop Testing Service. Using a robust \u201cattach-to-window\u201d mechanism for Windows environments,\u00a0we\u2019ve\u00a0introduced a dedicated \u2018Connect\u00a0To\u00a0Existing SAP Window\u2019 action. This allows your desktop\u00a0automation\u00a0to intelligently detect and hook into an already-open SAP session instead of triggering a fresh launch.<\/p>\n
How will it help?<\/b><\/p>\n
This workflow upgrade brings true continuity to your desktop SAP automation.<\/p>\n
\n- Resume Without Restarting:<\/b>\u00a0Easily continue an automation flow exactly where it left\u00a0off, or\u00a0seamlessly transition between manual steps and automated executions without losing your session state.<\/li>\n<\/ul>\n
\n- Optimize\u00a0System Resources:<\/b>\u00a0Prevent your desktop environment from being cluttered with redundant, duplicate SAP application instances during iterative testing and debugging.<\/li>\n<\/ul>\n
\n- Accelerate Debugging:<\/b>\u00a0By bypassing the\u00a0initial\u00a0login and navigation sequences, automation engineers can rapidly test and refine specific downstream actions directly within an active SAP window.<\/li>\n<\/ul>\n
Secure & Streamlined: QloudBridge\u00a0Encryption & Login Upgrades!<\/h2>\n
The Challenge:<\/b><\/p>\n
QloudBridge\u00a0acts as the vital tunnel connecting your local desktop environments to the\u00a0Qyrus\u00a0cloud platform. Any weakness in how this data is encrypted during transit poses a significant security risk for enterprise teams handling sensitive test data. Additionally, a clunky or unstable login flow creates unnecessary friction when engineers are trying to spin up local testing sessions. When underlying build issues cause these connections to drop unexpectedly, it disrupts automated runs and delays the entire testing cycle.<\/p>\n
The Fix:<\/b><\/p>\n
We have significantly enhanced the\u00a0QloudBridge\u00a0security architecture\u00a0by rolling out updated, enterprise-grade encryption protocols alongside a completely refined, smoother login flow. In tandem with these security hardening measures, we have successfully resolved underlying infrastructure and\u00a0build\u00a0bottlenecks that were previously causing minor connection instability. These updates have been fully verified on our staging environments and are\u00a0operating\u00a0exactly as expected.<\/p>\n
How will it help?<\/b><\/p>\n
This underlying infrastructure update provides a more resilient and secure testing foundation.<\/p>\n
\n- Hardened Data Security:<\/b>\u00a0Your local test data and application traffic are now protected by even stronger encryption during transit, satisfying the most rigorous enterprise compliance standards.<\/li>\n<\/ul>\n
\n- Seamless Authentication:<\/b>\u00a0The improved login flow makes it faster and significantly more intuitive to authenticate and connect your local machine to the platform, removing friction from your daily workflow.<\/li>\n<\/ul>\n
\n- Unshakeable Stability:<\/b>\u00a0By resolving the core infrastructure issues,\u00a0we\u2019ve\u00a0ensured\u00a0a highly reliable, persistent connection that\u00a0won\u2019t\u00a0unexpectedly drop during your long-running desktop automation suites.<\/li>\n<\/ul>\n<\/details>\n\n
Device Farm<\/p>\n<\/summary>\nFlawless Connections: Enhanced iOS Device Streaming!<\/h2>\n
The Challenge:<\/b><\/p>\n
Interacting with cloud-hosted iOS devices could sometimes suffer from slight video latency, dropped frames, or momentary disconnections during intense manual testing sessions or heavy automated runs. This streaming instability caused frustration, making it difficult to test UI responsiveness accurately or to confidently debug complex touch interactions on Apple hardware.<\/p>\n
The Fix:<\/b><\/p>\n
We have implemented major infrastructure upgrades to the device streaming protocol specifically for iOS device sessions. This includes optimized video encoding and a much more resilient connection architecture to ensure a rock-solid, high-definition stream between the physical iPhones and iPads in our data center and your local browser.<\/p>\n
How will it help?<\/b><\/p>\n
This underlying upgrade makes remote iOS testing feel like the device is sitting right on your desk.<\/p>\n
\n- Silky Smooth Manual Testing:<\/b>\u00a0Experience near-zero latency when interacting with remote iOS devices, allowing for precise gestures, swipes, and taps without frustrating delays.<\/li>\n<\/ul>\n
\n- Rock-Solid Stability:<\/b>\u00a0Say goodbye to\u00a0dropped\u00a0sessions and frozen screens. The hardened connection ensures uninterrupted testing, even during extended, deep-dive debugging workflows.<\/li>\n<\/ul>\n
\n- Accurate UI Validation:<\/b>\u00a0A crystal-clear, lag-free stream means you can confidently\u00a0validate\u00a0animations, transitions, and overall application responsiveness without the interference of network jitter.<\/li>\n<\/ul>\n<\/details>\n\n
Test Orchestration<\/p>\n<\/summary>\nIndependent Orchestration: Decoupled Licensing!<\/h2>\n
The Challenge:<\/b><\/p>\n
Previously, using Test Orchestration (TO) was strictly tied to your active module licenses for Web, Mobile, API, or Desktop testing. If one of those underlying service licenses expired or became inactive, it created a hard functional blocker within TO\u2014even for users whose primary role was just to build and manage orchestrated workflows. This rigid dependency disrupted continuous testing strategies and unnecessarily complicated license management across large QA teams.<\/p>\n
The Fix:<\/b><\/p>\n
We have completely decoupled Test Orchestration from these underlying service-module dependencies. TO now\u00a0operates\u00a0as a fully independent orchestration layer. You can seamlessly build, manage, and execute orchestration scripts without requiring active Web, Mobile, API, or Desktop module licenses. Crucially, the platform still securely respects your existing role-based access controls (RBAC) and accurately governs execution capacity based purely on your available Browser and Mobile execution inventory.<\/p>\n
How will it help?<\/b><\/p>\n
This licensing update provides greater flexibility and removes arbitrary administrative blockers from your orchestration workflows.<\/p>\n
\n- Uninterrupted Orchestration:<\/b>\u00a0Continue building, managing, and executing your complex test flows without unexpected access blocks caused by individual module license expirations.<\/li>\n<\/ul>\n
\n- Streamlined Team Access:<\/b>\u00a0QA managers and orchestration engineers can now freely\u00a0utilize\u00a0the TO workspace to coordinate overarching test strategies without consuming individual service-module licenses.<\/li>\n<\/ul>\n
\n- Resource-Based Scaling:<\/b>\u00a0Scale your\u00a0orchestrations naturally\u00a0based on your actual execution capacity (Browser\/Mobile slots) rather than being restricted by module-level licensing.<\/li>\n<\/ul>\n
Batch Execution: Folder-Level Scheduling!<\/h2>\n
The Challenge:<\/b><\/p>\n
Managing and scheduling large test suites can quickly become an administrative burden. Previously, if you wanted to schedule a group of related workflows to run at the same time, you had to configure the scheduling parameters for each workflow individually. This repetitive process was not only tedious and time-consuming but also increased the risk of manual configuration errors across your test batches.<\/p>\n
The Fix:<\/b><\/p>\n
We have introduced a powerful new\u00a0Folder-level Scheduler<\/b>\u00a0within Test Orchestration. Instead of managing individual scripts one by one, you can now apply a single scheduling configuration to an entire folder. This instantly schedules multiple workflows contained within that folder to execute using the exact same parameters.<\/p>\n
How will it help?<\/b><\/p>\n
This enhancement dramatically simplifies the administration of massive test suites.<\/p>\n
\n- Massive Time Savings:<\/b>\u00a0Eliminate\u00a0repetitive setup tasks by configuring the schedule once at the folder level, instantly applying it to dozens of underlying workflows.<\/li>\n<\/ul>\n
\n- Guaranteed Consistency:<\/b>\u00a0Ensure that all related tests in a specific batch run with the exact same configurations, environments, and timing rules,\u00a0eliminating\u00a0configuration drift.<\/li>\n<\/ul>\n
\n- Effortless Scalability:<\/b>\u00a0As your test suites grow, managing execution schedules\u00a0remains\u00a0simple and organized by\u00a0leveraging\u00a0your existing folder hierarchies.<\/li>\n<\/ul>\n<\/details>\n\n
qAPI Product Release Update<\/p>\n<\/summary>\nEnterprise-Ready\u00a0Execution: Node CLI Plugin Upgrades for\u00a0qAPI!<\/h2>\n
The Challenge:<\/b><\/p>\n
Managing API performance and functional testing via command-line interfaces across large, enterprise-level teams can get complicated. Previously, fetching project details via the CLI relied on user email addresses, which\u00a0didn\u2019t\u00a0scale well within complex enterprise structures where team-based access is the standard. Furthermore, sharing the results of CLI-triggered test runs often\u00a0involved\u00a0manual data extraction or wrestling with clunky file sharing, creating friction for teams trying to review execution reports quickly.<\/p>\n
The Fix:<\/b><\/p>\n
We have significantly upgraded the\u00a0Node CLI Plugin<\/b>\u00a0for\u00a0qAPI\u00a0to better support enterprise workflows. First, we transitioned project fetching from user emails to team IDs (\/projects?teamId), perfectly aligning the CLI with robust, enterprise-grade project management structures. We also introduced a new feature (\/get-reports-url) that automatically generates a secure CDN link for your execution reports\u2014valid for seven days\u2014directly from the command line.<\/p>\n
How will it help?<\/b><\/p>\n
These CLI enhancements streamline headless API testing for large-scale engineering teams.<\/p>\n
\n- Enterprise-Scale Management:<\/b>\u00a0Fetching project data based on Team ID ensures the CLI integrates flawlessly with complex organizational structures and role-based access configurations.<\/li>\n<\/ul>\n
\n- Instant Report Sharing:<\/b>\u00a0Automatically generate secure, temporary CDN URLs for your test reports straight from the CLI, making it incredibly simple to share results with your team or attach them to build logs.<\/li>\n<\/ul>\n
\n- Streamlined Automation:<\/b>\u00a0With a dedicated CLI plugin type and x-api-key support for URL generation, building secure, automated\u00a0qAPI\u00a0testing pipelines into your CI\/CD processes is smoother than ever.<\/li>\n<\/ul>\n
Seamless Navigation: Enhanced Project Listing!<\/h2>\n
![\"Enhanced](\"https:\/\/symmetricsolutionz.co.in\/qyrus\/wp-content\/uploads\/2026\/05\/Enhanced-Project-Listing-1024x497.png\")
<\/p>\n
The Challenge:<\/b><\/p>\n
As enterprise teams scale their API testing footprints, the number of active projects can grow rapidly into\u00a0the dozens\u00a0or hundreds. Previously, the\u00a0qAPI\u00a0dashboard restricted the project view\u2014only loading the first page of 15 projects and preventing users from scrolling or navigating to see the rest of their portfolio. This forced teams to rely on direct links or search workarounds just to access older or lower-priority projects.<\/p>\n
The Fix:<\/b><\/p>\n
We have resolved this limitation by overhauling the data-fetching and pagination logic within the\u00a0qAPI\u00a0project dashboard. Following successful validation in our staging environments, the fix is fully deployed, ensuring that your complete catalog of projects now loads fluidly and accurately across all pages.<\/p>\n
How will it help?<\/b><\/p>\n
This fix restores complete visibility and smooth navigation to your workspace.<\/p>\n
\n- Full Portfolio Visibility:<\/b>\u00a0Effortlessly browse through your entire history of API testing projects without arbitrary UI cutoffs or missing entries.<\/li>\n<\/ul>\n
\n- Frictionless Browsing:<\/b>\u00a0Experience smooth, reliable page loading as you scroll through large collections of enterprise projects.<\/li>\n<\/ul>\n
\n- Better Team Coordination:<\/b>\u00a0Large testing teams can now confidently organize and\u00a0locate\u00a0their respective projects from a single, uncompromised dashboard view.<\/li>\n<\/ul>\n
Enhanced Traceability: Script-Level Xray Visibility within Suites!<\/h2>\n
The Challenge:<\/b><\/p>\n
When managing large API test suites integrated with Jira Xray, it can be difficult to track which individual scripts are properly linked to your test management tools. Since Xray\u00a0determines\u00a0suite execution status based on its underlying linked scripts rather than a standalone suite-level configuration, testers previously had to open each script individually to verify its Xray integration details. This lack of centralized visibility made auditing large test suites time-consuming and\u00a0error-prone.<\/p>\n
The Fix:<\/b><\/p>\n
We have enhanced the visibility of Xray integration configurations directly within the\u00a0qAPI\u00a0test suite view. While direct suite-level configuration\u00a0isn\u2019t\u00a0native to Xray, you can now click the integration icon at the suite level to\u00a0immediately\u00a0view a clear breakdown of the linked scripts alongside their respective Xray integration details and script names.<\/p>\n
How will it help?<\/b><\/p>\n
This update centralizes your integration tracking, making test management much more transparent.<\/p>\n
\n- Centralized Integration Audits:<\/b>\u00a0Instantly verify which scripts within a suite are correctly mapped to Xray without toggling back and forth between individual script configurations.<\/li>\n<\/ul>\n
\n- Clear Execution Mapping:<\/b>\u00a0Easily understand how your suite-level execution status will flow back to Jira based on a clear visual summary of its underlying scripts.<\/li>\n<\/ul>\n
\n- Streamlined Troubleshooting:<\/b>\u00a0Quickly\u00a0identify\u00a0unlinked or misconfigured scripts directly from the high-level suite overview, keeping your test management system perfectly synchronized.<\/li>\n<\/ul>\n<\/details>\n
Flawless Connections: Enhanced iOS Device Streaming!<\/h2>\n
The Challenge:<\/b><\/p>\n
When using Test Generator v2 to automatically build test scenarios via integrations, any friction in the generation flow ruins the speed advantage of using AI. Previously, users faced two major hurdles: the\u00a0initial\u00a0streaming API could experience a bottleneck\u2014taking up to two minutes just to return a “Generating” status\u2014and auto-generated variable actions lacked structural logic. If a script required multiple variables (e.g., Var 1 through Var 5), the AI\u00a0didn’t\u00a0automatically cross-reference its memory to intelligently link those variables to\u00a0subsequent\u00a0data handler steps, forcing testers to manually patch the logic. Additionally, path values for generated steps were buried, making it tedious to audit the AI’s structural paths.<\/p>\n
The Fix:<\/b><\/p>\n
We have rolled out critical enhancements to\u00a0Test Generator v2\u00a0<\/b>to\u00a0optimize\u00a0both backend performance and AI logic. We dramatically accelerated the\u00a0initial\u00a0stream\u00a0API response time, slashing the latency required to\u00a0initiate\u00a0a generation job. On the intelligence front, the AI now automatically names variables inside the “Create Variable” action and intelligently maps those identical variable names to corresponding downstream data handler actions (such as Dynamic Set steps) by referencing its historical memory. Finally, we have explicitly included the exact path values right inside the info section of every step TG generates.<\/p>\n
How will it help?<\/b><\/p>\n
These intelligence and speed optimizations turn AI generation into a fluid, hands-off experience.<\/p>\n
\n- Instant Generation:<\/b>\u00a0No more waiting on spinning wheels. The optimized streaming API kicks off your AI generation jobs\u00a0almost instantly, accelerating your overall testing velocity.<\/li>\n<\/ul>\n
\n- Flawless End-to-End Variable Logic:<\/b>\u00a0The AI now handles multi-variable data mapping seamlessly. If your test scenario creates five variables, the system automatically tracks them in its memory and binds the correct variable to\u00a0subsequent\u00a0dynamic steps without manual intervention.<\/li>\n<\/ul>\n
\n- Transparent Step Auditing:<\/b>\u00a0With path values clearly visible in the info section of each generated step, you can\u00a0immediately\u00a0inspect, verify, and debug the exact navigation paths the AI mapped out.<\/li>\n<\/ul>\n
Seamless SAP Scripting: Real-Time Locator Access!<\/h2>\n
The Challenge:<\/b><\/p>\n
Building automated tests for complex SAP web interfaces (like SAP Fiori) requires highly specific, often intricate element locators. Previously, gathering these unique SAP locators meant testers had to\u00a0frequently\u00a0break their workflow\u2014jumping between separate recording sessions, external inspection tools, or complex documentation just to copy and paste the correct identifiers into their test steps. This context-switching drastically slowed down the test creation process and increased the risk of manual errors.<\/p>\n
The Fix:<\/b><\/p>\n
We have fully integrated\u00a0SAP Recorded Locators<\/b>\u00a0directly into the Web Testing builder. Now, while you are actively constructing your test steps on the canvas, you have immediate, real-time access to the specialized SAP locators you need without ever having to leave the test building interface.<\/p>\n
How will it help?<\/b><\/p>\n
This workflow enhancement removes the friction of testing complex SAP environments.<\/p>\n
\n- Accelerated Test Building:<\/b>\u00a0Say goodbye to context-switching. You can now design, configure, and assign the correct SAP locators fluidly within a single, unified workspace.<\/li>\n<\/ul>\n
\n- Pinpoint Accuracy:<\/b>\u00a0By pulling recorded locators directly into your builder, you significantly reduce the risk of typos or incorrect element identification, ensuring your tests are robust from the start.<\/li>\n<\/ul>\n
\n- Developer-Friendly Experience:<\/b>\u00a0This seamless integration makes building complex SAP web tests faster, more intuitive, and far less tedious for your automation engineers.<\/li>\n<\/ul>\n
Seamless CI\/CD Integration: Jenkins & Azure Plugins for Desktop Testing!<\/h2>\n<\/h2>\n
The Challenge:<\/b><\/p>\n
As organizations modernize their deployment pipelines, manual testing interventions create significant bottlenecks. Previously, triggering automated scripts for Desktop applications required users to step outside of their primary CI\/CD workflows. Without native plugins for popular orchestration tools, teams had to rely on cumbersome manual triggers or complex, custom-built scripts to\u00a0initiate\u00a0their Desktop Testing suites, resulting in disjointed\u00a0delivery\u00a0pipelines and slower release cycles.<\/p>\n
The Fix:<\/b><\/p>\n
We have officially introduced dedicated\u00a0Jenkins and Azure DevOps plugins<\/b>\u00a0specifically for the Desktop Testing Service. These new plugins empower you to seamlessly trigger and manage your automated desktop application scripts directly from your existing CI\/CD pipelines, bringing the service up to parity with our Web, API, and Mobile testing offerings.<\/p>\n
How will it help?<\/b><\/p>\n
This integration bridges the gap between your desktop application builds and your automated testing ecosystem.<\/p>\n
\n- Unified Workflows:<\/b>\u00a0Manage your entire testing strategy\u2014across\u00a0Web, Mobile, API, and now Desktop\u2014from a centralized CI\/CD control plane.<\/li>\n<\/ul>\n
\n- Frictionless Automation:<\/b>\u00a0Automatically execute robust desktop automation scripts the moment a new build is deployed,\u00a0eliminating\u00a0manual handoffs and accelerating your time-to-market.<\/li>\n<\/ul>\n
\n- Developer Flexibility:<\/b>\u00a0Empower your engineering teams to seamlessly embed desktop quality gates into the familiar Jenkins or Azure environments they already use every day.<\/li>\n<\/ul>\n
Continuous Execution: Connect to Existing SAP Windows!<\/h2>\n
<\/p>\n
The Challenge:<\/b><\/p>\n
When automating complex desktop workflows within SAP GUI, test scripts traditionally\u00a0forced\u00a0a brand-new application instance to launch for every execution. If a test failed midway or if an engineer wanted to resume a specific sequence after manual intervention, they were forced to restart the entire SAP login and navigation flow from scratch. This rigid behavior created duplicate windows, consumed unnecessary system resources, and drastically slowed down test debugging and multi-step process validations.<\/p>\n
The Fix:<\/b><\/p>\n
We have implemented powerful session persistence capabilities within the Desktop Testing Service. Using a robust “attach-to-window” mechanism for Windows environments,\u00a0we’ve\u00a0introduced a dedicated \u2018Connect\u00a0To\u00a0Existing SAP Window\u2019 action. This allows your desktop\u00a0automation\u00a0to intelligently detect and hook into an already-open SAP session instead of triggering a fresh launch.<\/p>\n
How will it help?<\/b><\/p>\n
This workflow upgrade brings true continuity to your desktop SAP automation.<\/p>\n
\n- Resume Without Restarting:<\/b>\u00a0Easily continue an automation flow exactly where it left\u00a0off, or\u00a0seamlessly transition between manual steps and automated executions without losing your session state.<\/li>\n<\/ul>\n
\n- Optimize\u00a0System Resources:<\/b>\u00a0Prevent your desktop environment from being cluttered with redundant, duplicate SAP application instances during iterative testing and debugging.<\/li>\n<\/ul>\n
\n- Accelerate Debugging:<\/b>\u00a0By bypassing the\u00a0initial\u00a0login and navigation sequences, automation engineers can rapidly test and refine specific downstream actions directly within an active SAP window.<\/li>\n<\/ul>\n
Secure & Streamlined: QloudBridge\u00a0Encryption & Login Upgrades!<\/h2>\n
The Challenge:<\/b><\/p>\n
QloudBridge\u00a0acts as the vital tunnel connecting your local desktop environments to the\u00a0Qyrus\u00a0cloud platform. Any weakness in how this data is encrypted during transit poses a significant security risk for enterprise teams handling sensitive test data. Additionally, a clunky or unstable login flow creates unnecessary friction when engineers are trying to spin up local testing sessions. When underlying build issues cause these connections to drop unexpectedly, it disrupts automated runs and delays the entire testing cycle.<\/p>\n
The Fix:<\/b><\/p>\n
We have significantly enhanced the\u00a0QloudBridge\u00a0security architecture\u00a0by rolling out updated, enterprise-grade encryption protocols alongside a completely refined, smoother login flow. In tandem with these security hardening measures, we have successfully resolved underlying infrastructure and\u00a0build\u00a0bottlenecks that were previously causing minor connection instability. These updates have been fully verified on our staging environments and are\u00a0operating\u00a0exactly as expected.<\/p>\n
How will it help?<\/b><\/p>\n
This underlying infrastructure update provides a more resilient and secure testing foundation.<\/p>\n
\n- Hardened Data Security:<\/b>\u00a0Your local test data and application traffic are now protected by even stronger encryption during transit, satisfying the most rigorous enterprise compliance standards.<\/li>\n<\/ul>\n
\n- Seamless Authentication:<\/b>\u00a0The improved login flow makes it faster and significantly more intuitive to authenticate and connect your local machine to the platform, removing friction from your daily workflow.<\/li>\n<\/ul>\n
\n- Unshakeable Stability:<\/b>\u00a0By resolving the core infrastructure issues,\u00a0we\u2019ve\u00a0ensured\u00a0a highly reliable, persistent connection that\u00a0won’t\u00a0unexpectedly drop during your long-running desktop automation suites.<\/li>\n<\/ul>\n
Flawless Connections: Enhanced iOS Device Streaming!<\/h2>\n
The Challenge:<\/b><\/p>\n
Interacting with cloud-hosted iOS devices could sometimes suffer from slight video latency, dropped frames, or momentary disconnections during intense manual testing sessions or heavy automated runs. This streaming instability caused frustration, making it difficult to test UI responsiveness accurately or to confidently debug complex touch interactions on Apple hardware.<\/p>\n
The Fix:<\/b><\/p>\n
We have implemented major infrastructure upgrades to the device streaming protocol specifically for iOS device sessions. This includes optimized video encoding and a much more resilient connection architecture to ensure a rock-solid, high-definition stream between the physical iPhones and iPads in our data center and your local browser.<\/p>\n
How will it help?<\/b><\/p>\n
This underlying upgrade makes remote iOS testing feel like the device is sitting right on your desk.<\/p>\n
\n- Silky Smooth Manual Testing:<\/b>\u00a0Experience near-zero latency when interacting with remote iOS devices, allowing for precise gestures, swipes, and taps without frustrating delays.<\/li>\n<\/ul>\n
\n- Rock-Solid Stability:<\/b>\u00a0Say goodbye to\u00a0dropped\u00a0sessions and frozen screens. The hardened connection ensures uninterrupted testing, even during extended, deep-dive debugging workflows.<\/li>\n<\/ul>\n
\n- Accurate UI Validation:<\/b>\u00a0A crystal-clear, lag-free stream means you can confidently\u00a0validate\u00a0animations, transitions, and overall application responsiveness without the interference of network jitter.<\/li>\n<\/ul>\n
Independent Orchestration: Decoupled Licensing!<\/h2>\n
The Challenge:<\/b><\/p>\n
Previously, using Test Orchestration (TO) was strictly tied to your active module licenses for Web, Mobile, API, or Desktop testing. If one of those underlying service licenses expired or became inactive, it created a hard functional blocker within TO\u2014even for users whose primary role was just to build and manage orchestrated workflows. This rigid dependency disrupted continuous testing strategies and unnecessarily complicated license management across large QA teams.<\/p>\n
The Fix:<\/b><\/p>\n
We have completely decoupled Test Orchestration from these underlying service-module dependencies. TO now\u00a0operates\u00a0as a fully independent orchestration layer. You can seamlessly build, manage, and execute orchestration scripts without requiring active Web, Mobile, API, or Desktop module licenses. Crucially, the platform still securely respects your existing role-based access controls (RBAC) and accurately governs execution capacity based purely on your available Browser and Mobile execution inventory.<\/p>\n
How will it help?<\/b><\/p>\n
This licensing update provides greater flexibility and removes arbitrary administrative blockers from your orchestration workflows.<\/p>\n
\n- Uninterrupted Orchestration:<\/b>\u00a0Continue building, managing, and executing your complex test flows without unexpected access blocks caused by individual module license expirations.<\/li>\n<\/ul>\n
\n- Streamlined Team Access:<\/b>\u00a0QA managers and orchestration engineers can now freely\u00a0utilize\u00a0the TO workspace to coordinate overarching test strategies without consuming individual service-module licenses.<\/li>\n<\/ul>\n
\n- Resource-Based Scaling:<\/b>\u00a0Scale your\u00a0orchestrations naturally\u00a0based on your actual execution capacity (Browser\/Mobile slots) rather than being restricted by module-level licensing.<\/li>\n<\/ul>\n
Batch Execution: Folder-Level Scheduling!<\/h2>\n
The Challenge:<\/b><\/p>\n
Managing and scheduling large test suites can quickly become an administrative burden. Previously, if you wanted to schedule a group of related workflows to run at the same time, you had to configure the scheduling parameters for each workflow individually. This repetitive process was not only tedious and time-consuming but also increased the risk of manual configuration errors across your test batches.<\/p>\n
The Fix:<\/b><\/p>\n
We have introduced a powerful new\u00a0Folder-level Scheduler<\/b>\u00a0within Test Orchestration. Instead of managing individual scripts one by one, you can now apply a single scheduling configuration to an entire folder. This instantly schedules multiple workflows contained within that folder to execute using the exact same parameters.<\/p>\n
How will it help?<\/b><\/p>\n
This enhancement dramatically simplifies the administration of massive test suites.<\/p>\n
\n- Massive Time Savings:<\/b>\u00a0Eliminate\u00a0repetitive setup tasks by configuring the schedule once at the folder level, instantly applying it to dozens of underlying workflows.<\/li>\n<\/ul>\n
\n- Guaranteed Consistency:<\/b>\u00a0Ensure that all related tests in a specific batch run with the exact same configurations, environments, and timing rules,\u00a0eliminating\u00a0configuration drift.<\/li>\n<\/ul>\n
\n- Effortless Scalability:<\/b>\u00a0As your test suites grow, managing execution schedules\u00a0remains\u00a0simple and organized by\u00a0leveraging\u00a0your existing folder hierarchies.<\/li>\n<\/ul>\n
Enterprise-Ready\u00a0Execution: Node CLI Plugin Upgrades for\u00a0qAPI!<\/h2>\n
The Challenge:<\/b><\/p>\n
Managing API performance and functional testing via command-line interfaces across large, enterprise-level teams can get complicated. Previously, fetching project details via the CLI relied on user email addresses, which\u00a0didn’t\u00a0scale well within complex enterprise structures where team-based access is the standard. Furthermore, sharing the results of CLI-triggered test runs often\u00a0involved\u00a0manual data extraction or wrestling with clunky file sharing, creating friction for teams trying to review execution reports quickly.<\/p>\n
The Fix:<\/b><\/p>\n
We have significantly upgraded the\u00a0Node CLI Plugin<\/b>\u00a0for\u00a0qAPI\u00a0to better support enterprise workflows. First, we transitioned project fetching from user emails to team IDs (\/projects?teamId), perfectly aligning the CLI with robust, enterprise-grade project management structures. We also introduced a new feature (\/get-reports-url) that automatically generates a secure CDN link for your execution reports\u2014valid for seven days\u2014directly from the command line.<\/p>\n
How will it help?<\/b><\/p>\n
These CLI enhancements streamline headless API testing for large-scale engineering teams.<\/p>\n
\n- Enterprise-Scale Management:<\/b>\u00a0Fetching project data based on Team ID ensures the CLI integrates flawlessly with complex organizational structures and role-based access configurations.<\/li>\n<\/ul>\n
\n- Instant Report Sharing:<\/b>\u00a0Automatically generate secure, temporary CDN URLs for your test reports straight from the CLI, making it incredibly simple to share results with your team or attach them to build logs.<\/li>\n<\/ul>\n
\n- Streamlined Automation:<\/b>\u00a0With a dedicated CLI plugin type and x-api-key support for URL generation, building secure, automated\u00a0qAPI\u00a0testing pipelines into your CI\/CD processes is smoother than ever.<\/li>\n<\/ul>\n
Seamless Navigation: Enhanced Project Listing!<\/h2>\n
<\/p>\n
The Challenge:<\/b><\/p>\n
As enterprise teams scale their API testing footprints, the number of active projects can grow rapidly into\u00a0the dozens\u00a0or hundreds. Previously, the\u00a0qAPI\u00a0dashboard restricted the project view\u2014only loading the first page of 15 projects and preventing users from scrolling or navigating to see the rest of their portfolio. This forced teams to rely on direct links or search workarounds just to access older or lower-priority projects.<\/p>\n
The Fix:<\/b><\/p>\n
We have resolved this limitation by overhauling the data-fetching and pagination logic within the\u00a0qAPI\u00a0project dashboard. Following successful validation in our staging environments, the fix is fully deployed, ensuring that your complete catalog of projects now loads fluidly and accurately across all pages.<\/p>\n
How will it help?<\/b><\/p>\n
This fix restores complete visibility and smooth navigation to your workspace.<\/p>\n
\n- Full Portfolio Visibility:<\/b>\u00a0Effortlessly browse through your entire history of API testing projects without arbitrary UI cutoffs or missing entries.<\/li>\n<\/ul>\n
\n- Frictionless Browsing:<\/b>\u00a0Experience smooth, reliable page loading as you scroll through large collections of enterprise projects.<\/li>\n<\/ul>\n
\n- Better Team Coordination:<\/b>\u00a0Large testing teams can now confidently organize and\u00a0locate\u00a0their respective projects from a single, uncompromised dashboard view.<\/li>\n<\/ul>\n
Enhanced Traceability: Script-Level Xray Visibility within Suites!<\/h2>\n
The Challenge:<\/b><\/p>\n
When managing large API test suites integrated with Jira Xray, it can be difficult to track which individual scripts are properly linked to your test management tools. Since Xray\u00a0determines\u00a0suite execution status based on its underlying linked scripts rather than a standalone suite-level configuration, testers previously had to open each script individually to verify its Xray integration details. This lack of centralized visibility made auditing large test suites time-consuming and\u00a0error-prone.<\/p>\n
The Fix:<\/b><\/p>\n
We have enhanced the visibility of Xray integration configurations directly within the\u00a0qAPI\u00a0test suite view. While direct suite-level configuration\u00a0isn’t\u00a0native to Xray, you can now click the integration icon at the suite level to\u00a0immediately\u00a0view a clear breakdown of the linked scripts alongside their respective Xray integration details and script names.<\/p>\n
How will it help?<\/b><\/p>\n
This update centralizes your integration tracking, making test management much more transparent.<\/p>\n
\n- Centralized Integration Audits:<\/b>\u00a0Instantly verify which scripts within a suite are correctly mapped to Xray without toggling back and forth between individual script configurations.<\/li>\n<\/ul>\n
\n- Clear Execution Mapping:<\/b>\u00a0Easily understand how your suite-level execution status will flow back to Jira based on a clear visual summary of its underlying scripts.<\/li>\n<\/ul>\n
\n- Streamlined Troubleshooting:<\/b>\u00a0Quickly\u00a0identify\u00a0unlinked or misconfigured scripts directly from the high-level suite overview, keeping your test management system perfectly synchronized.<\/li>\n<\/ul>\n
Ready to Leverage May’s Innovations?<\/h2>\n
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.<\/p>\n
Eager to explore how these advancements can transform your testing efforts? The best way to appreciate the\u00a0Qyrus\u00a0difference is to experience these new capabilities directly.<\/p>\n
Ready to dive deeper or get started?<\/b><\/p>\n
- \n
- Flawless End-to-End Variable Logic:<\/b>\u00a0The AI now handles multi-variable data mapping seamlessly. If your test scenario creates five variables, the system automatically tracks them in its memory and binds the correct variable to\u00a0subsequent\u00a0dynamic steps without manual intervention.<\/li>\n<\/ul>\n
- \n
- Transparent Step Auditing:<\/b>\u00a0With path values clearly visible in the info section of each generated step, you can\u00a0immediately\u00a0inspect, verify, and debug the exact navigation paths the AI mapped out.<\/li>\n<\/ul>\n
Seamless SAP Scripting: Real-Time Locator Access!<\/h2>\n
The Challenge:<\/b><\/p>\n
Building automated tests for complex SAP web interfaces (like SAP Fiori) requires highly specific, often intricate element locators. Previously, gathering these unique SAP locators meant testers had to\u00a0frequently\u00a0break their workflow\u2014jumping between separate recording sessions, external inspection tools, or complex documentation just to copy and paste the correct identifiers into their test steps. This context-switching drastically slowed down the test creation process and increased the risk of manual errors.<\/p>\n
The Fix:<\/b><\/p>\n
We have fully integrated\u00a0SAP Recorded Locators<\/b>\u00a0directly into the Web Testing builder. Now, while you are actively constructing your test steps on the canvas, you have immediate, real-time access to the specialized SAP locators you need without ever having to leave the test building interface.<\/p>\n
How will it help?<\/b><\/p>\n
This workflow enhancement removes the friction of testing complex SAP environments.<\/p>\n
- \n
- Accelerated Test Building:<\/b>\u00a0Say goodbye to context-switching. You can now design, configure, and assign the correct SAP locators fluidly within a single, unified workspace.<\/li>\n<\/ul>\n
- \n
- Pinpoint Accuracy:<\/b>\u00a0By pulling recorded locators directly into your builder, you significantly reduce the risk of typos or incorrect element identification, ensuring your tests are robust from the start.<\/li>\n<\/ul>\n
- \n
- Developer-Friendly Experience:<\/b>\u00a0This seamless integration makes building complex SAP web tests faster, more intuitive, and far less tedious for your automation engineers.<\/li>\n<\/ul>\n<\/details>\n\n
Desktop Testing<\/p>\n<\/summary>\n
Seamless CI\/CD Integration: Jenkins & Azure Plugins for Desktop Testing!<\/h2>\n
<\/h2>\nThe Challenge:<\/b><\/p>\n
As organizations modernize their deployment pipelines, manual testing interventions create significant bottlenecks. Previously, triggering automated scripts for Desktop applications required users to step outside of their primary CI\/CD workflows. Without native plugins for popular orchestration tools, teams had to rely on cumbersome manual triggers or complex, custom-built scripts to\u00a0initiate\u00a0their Desktop Testing suites, resulting in disjointed\u00a0delivery\u00a0pipelines and slower release cycles.<\/p>\n
The Fix:<\/b><\/p>\n
We have officially introduced dedicated\u00a0Jenkins and Azure DevOps plugins<\/b>\u00a0specifically for the Desktop Testing Service. These new plugins empower you to seamlessly trigger and manage your automated desktop application scripts directly from your existing CI\/CD pipelines, bringing the service up to parity with our Web, API, and Mobile testing offerings.<\/p>\n
How will it help?<\/b><\/p>\n
This integration bridges the gap between your desktop application builds and your automated testing ecosystem.<\/p>\n
- \n
- Unified Workflows:<\/b>\u00a0Manage your entire testing strategy\u2014across\u00a0Web, Mobile, API, and now Desktop\u2014from a centralized CI\/CD control plane.<\/li>\n<\/ul>\n
- \n
- Frictionless Automation:<\/b>\u00a0Automatically execute robust desktop automation scripts the moment a new build is deployed,\u00a0eliminating\u00a0manual handoffs and accelerating your time-to-market.<\/li>\n<\/ul>\n
- \n
- Developer Flexibility:<\/b>\u00a0Empower your engineering teams to seamlessly embed desktop quality gates into the familiar Jenkins or Azure environments they already use every day.<\/li>\n<\/ul>\n
Continuous Execution: Connect to Existing SAP Windows!<\/h2>\n
<\/p>\nThe Challenge:<\/b><\/p>\n
When automating complex desktop workflows within SAP GUI, test scripts traditionally\u00a0forced\u00a0a brand-new application instance to launch for every execution. If a test failed midway or if an engineer wanted to resume a specific sequence after manual intervention, they were forced to restart the entire SAP login and navigation flow from scratch. This rigid behavior created duplicate windows, consumed unnecessary system resources, and drastically slowed down test debugging and multi-step process validations.<\/p>\n
The Fix:<\/b><\/p>\n
We have implemented powerful session persistence capabilities within the Desktop Testing Service. Using a robust \u201cattach-to-window\u201d mechanism for Windows environments,\u00a0we\u2019ve\u00a0introduced a dedicated \u2018Connect\u00a0To\u00a0Existing SAP Window\u2019 action. This allows your desktop\u00a0automation\u00a0to intelligently detect and hook into an already-open SAP session instead of triggering a fresh launch.<\/p>\n
How will it help?<\/b><\/p>\n
This workflow upgrade brings true continuity to your desktop SAP automation.<\/p>\n
- \n
- Resume Without Restarting:<\/b>\u00a0Easily continue an automation flow exactly where it left\u00a0off, or\u00a0seamlessly transition between manual steps and automated executions without losing your session state.<\/li>\n<\/ul>\n
- \n
- Optimize\u00a0System Resources:<\/b>\u00a0Prevent your desktop environment from being cluttered with redundant, duplicate SAP application instances during iterative testing and debugging.<\/li>\n<\/ul>\n
- \n
- Accelerate Debugging:<\/b>\u00a0By bypassing the\u00a0initial\u00a0login and navigation sequences, automation engineers can rapidly test and refine specific downstream actions directly within an active SAP window.<\/li>\n<\/ul>\n
Secure & Streamlined: QloudBridge\u00a0Encryption & Login Upgrades!<\/h2>\n
The Challenge:<\/b><\/p>\n
QloudBridge\u00a0acts as the vital tunnel connecting your local desktop environments to the\u00a0Qyrus\u00a0cloud platform. Any weakness in how this data is encrypted during transit poses a significant security risk for enterprise teams handling sensitive test data. Additionally, a clunky or unstable login flow creates unnecessary friction when engineers are trying to spin up local testing sessions. When underlying build issues cause these connections to drop unexpectedly, it disrupts automated runs and delays the entire testing cycle.<\/p>\n
The Fix:<\/b><\/p>\n
We have significantly enhanced the\u00a0QloudBridge\u00a0security architecture\u00a0by rolling out updated, enterprise-grade encryption protocols alongside a completely refined, smoother login flow. In tandem with these security hardening measures, we have successfully resolved underlying infrastructure and\u00a0build\u00a0bottlenecks that were previously causing minor connection instability. These updates have been fully verified on our staging environments and are\u00a0operating\u00a0exactly as expected.<\/p>\n
How will it help?<\/b><\/p>\n
This underlying infrastructure update provides a more resilient and secure testing foundation.<\/p>\n
- \n
- Hardened Data Security:<\/b>\u00a0Your local test data and application traffic are now protected by even stronger encryption during transit, satisfying the most rigorous enterprise compliance standards.<\/li>\n<\/ul>\n
- \n
- Seamless Authentication:<\/b>\u00a0The improved login flow makes it faster and significantly more intuitive to authenticate and connect your local machine to the platform, removing friction from your daily workflow.<\/li>\n<\/ul>\n
- \n
- Unshakeable Stability:<\/b>\u00a0By resolving the core infrastructure issues,\u00a0we\u2019ve\u00a0ensured\u00a0a highly reliable, persistent connection that\u00a0won\u2019t\u00a0unexpectedly drop during your long-running desktop automation suites.<\/li>\n<\/ul>\n<\/details>\n\n
Device Farm<\/p>\n<\/summary>\n
Flawless Connections: Enhanced iOS Device Streaming!<\/h2>\n
The Challenge:<\/b><\/p>\n
Interacting with cloud-hosted iOS devices could sometimes suffer from slight video latency, dropped frames, or momentary disconnections during intense manual testing sessions or heavy automated runs. This streaming instability caused frustration, making it difficult to test UI responsiveness accurately or to confidently debug complex touch interactions on Apple hardware.<\/p>\n
The Fix:<\/b><\/p>\n
We have implemented major infrastructure upgrades to the device streaming protocol specifically for iOS device sessions. This includes optimized video encoding and a much more resilient connection architecture to ensure a rock-solid, high-definition stream between the physical iPhones and iPads in our data center and your local browser.<\/p>\n
How will it help?<\/b><\/p>\n
This underlying upgrade makes remote iOS testing feel like the device is sitting right on your desk.<\/p>\n
- \n
- Silky Smooth Manual Testing:<\/b>\u00a0Experience near-zero latency when interacting with remote iOS devices, allowing for precise gestures, swipes, and taps without frustrating delays.<\/li>\n<\/ul>\n
- \n
- Rock-Solid Stability:<\/b>\u00a0Say goodbye to\u00a0dropped\u00a0sessions and frozen screens. The hardened connection ensures uninterrupted testing, even during extended, deep-dive debugging workflows.<\/li>\n<\/ul>\n
- \n
- Accurate UI Validation:<\/b>\u00a0A crystal-clear, lag-free stream means you can confidently\u00a0validate\u00a0animations, transitions, and overall application responsiveness without the interference of network jitter.<\/li>\n<\/ul>\n<\/details>\n\n
Test Orchestration<\/p>\n<\/summary>\n
Independent Orchestration: Decoupled Licensing!<\/h2>\n
The Challenge:<\/b><\/p>\n
Previously, using Test Orchestration (TO) was strictly tied to your active module licenses for Web, Mobile, API, or Desktop testing. If one of those underlying service licenses expired or became inactive, it created a hard functional blocker within TO\u2014even for users whose primary role was just to build and manage orchestrated workflows. This rigid dependency disrupted continuous testing strategies and unnecessarily complicated license management across large QA teams.<\/p>\n
The Fix:<\/b><\/p>\n
We have completely decoupled Test Orchestration from these underlying service-module dependencies. TO now\u00a0operates\u00a0as a fully independent orchestration layer. You can seamlessly build, manage, and execute orchestration scripts without requiring active Web, Mobile, API, or Desktop module licenses. Crucially, the platform still securely respects your existing role-based access controls (RBAC) and accurately governs execution capacity based purely on your available Browser and Mobile execution inventory.<\/p>\n
How will it help?<\/b><\/p>\n
This licensing update provides greater flexibility and removes arbitrary administrative blockers from your orchestration workflows.<\/p>\n
- \n
- Uninterrupted Orchestration:<\/b>\u00a0Continue building, managing, and executing your complex test flows without unexpected access blocks caused by individual module license expirations.<\/li>\n<\/ul>\n
- \n
- Streamlined Team Access:<\/b>\u00a0QA managers and orchestration engineers can now freely\u00a0utilize\u00a0the TO workspace to coordinate overarching test strategies without consuming individual service-module licenses.<\/li>\n<\/ul>\n
- \n
- Resource-Based Scaling:<\/b>\u00a0Scale your\u00a0orchestrations naturally\u00a0based on your actual execution capacity (Browser\/Mobile slots) rather than being restricted by module-level licensing.<\/li>\n<\/ul>\n
Batch Execution: Folder-Level Scheduling!<\/h2>\n
The Challenge:<\/b><\/p>\n
Managing and scheduling large test suites can quickly become an administrative burden. Previously, if you wanted to schedule a group of related workflows to run at the same time, you had to configure the scheduling parameters for each workflow individually. This repetitive process was not only tedious and time-consuming but also increased the risk of manual configuration errors across your test batches.<\/p>\n
The Fix:<\/b><\/p>\n
We have introduced a powerful new\u00a0Folder-level Scheduler<\/b>\u00a0within Test Orchestration. Instead of managing individual scripts one by one, you can now apply a single scheduling configuration to an entire folder. This instantly schedules multiple workflows contained within that folder to execute using the exact same parameters.<\/p>\n
How will it help?<\/b><\/p>\n
This enhancement dramatically simplifies the administration of massive test suites.<\/p>\n
- \n
- Massive Time Savings:<\/b>\u00a0Eliminate\u00a0repetitive setup tasks by configuring the schedule once at the folder level, instantly applying it to dozens of underlying workflows.<\/li>\n<\/ul>\n
- \n
- Guaranteed Consistency:<\/b>\u00a0Ensure that all related tests in a specific batch run with the exact same configurations, environments, and timing rules,\u00a0eliminating\u00a0configuration drift.<\/li>\n<\/ul>\n
- \n
- Effortless Scalability:<\/b>\u00a0As your test suites grow, managing execution schedules\u00a0remains\u00a0simple and organized by\u00a0leveraging\u00a0your existing folder hierarchies.<\/li>\n<\/ul>\n<\/details>\n\n
qAPI Product Release Update<\/p>\n<\/summary>\n
Enterprise-Ready\u00a0Execution: Node CLI Plugin Upgrades for\u00a0qAPI!<\/h2>\n
The Challenge:<\/b><\/p>\n
Managing API performance and functional testing via command-line interfaces across large, enterprise-level teams can get complicated. Previously, fetching project details via the CLI relied on user email addresses, which\u00a0didn\u2019t\u00a0scale well within complex enterprise structures where team-based access is the standard. Furthermore, sharing the results of CLI-triggered test runs often\u00a0involved\u00a0manual data extraction or wrestling with clunky file sharing, creating friction for teams trying to review execution reports quickly.<\/p>\n
The Fix:<\/b><\/p>\n
We have significantly upgraded the\u00a0Node CLI Plugin<\/b>\u00a0for\u00a0qAPI\u00a0to better support enterprise workflows. First, we transitioned project fetching from user emails to team IDs (\/projects?teamId), perfectly aligning the CLI with robust, enterprise-grade project management structures. We also introduced a new feature (\/get-reports-url) that automatically generates a secure CDN link for your execution reports\u2014valid for seven days\u2014directly from the command line.<\/p>\n
How will it help?<\/b><\/p>\n
These CLI enhancements streamline headless API testing for large-scale engineering teams.<\/p>\n
- \n
- Enterprise-Scale Management:<\/b>\u00a0Fetching project data based on Team ID ensures the CLI integrates flawlessly with complex organizational structures and role-based access configurations.<\/li>\n<\/ul>\n
- \n
- Instant Report Sharing:<\/b>\u00a0Automatically generate secure, temporary CDN URLs for your test reports straight from the CLI, making it incredibly simple to share results with your team or attach them to build logs.<\/li>\n<\/ul>\n
- \n
- Streamlined Automation:<\/b>\u00a0With a dedicated CLI plugin type and x-api-key support for URL generation, building secure, automated\u00a0qAPI\u00a0testing pipelines into your CI\/CD processes is smoother than ever.<\/li>\n<\/ul>\n
Seamless Navigation: Enhanced Project Listing!<\/h2>\n
<\/p>\nThe Challenge:<\/b><\/p>\n
As enterprise teams scale their API testing footprints, the number of active projects can grow rapidly into\u00a0the dozens\u00a0or hundreds. Previously, the\u00a0qAPI\u00a0dashboard restricted the project view\u2014only loading the first page of 15 projects and preventing users from scrolling or navigating to see the rest of their portfolio. This forced teams to rely on direct links or search workarounds just to access older or lower-priority projects.<\/p>\n
The Fix:<\/b><\/p>\n
We have resolved this limitation by overhauling the data-fetching and pagination logic within the\u00a0qAPI\u00a0project dashboard. Following successful validation in our staging environments, the fix is fully deployed, ensuring that your complete catalog of projects now loads fluidly and accurately across all pages.<\/p>\n
How will it help?<\/b><\/p>\n
This fix restores complete visibility and smooth navigation to your workspace.<\/p>\n
- \n
- Full Portfolio Visibility:<\/b>\u00a0Effortlessly browse through your entire history of API testing projects without arbitrary UI cutoffs or missing entries.<\/li>\n<\/ul>\n
- \n
- Frictionless Browsing:<\/b>\u00a0Experience smooth, reliable page loading as you scroll through large collections of enterprise projects.<\/li>\n<\/ul>\n
- \n
- Better Team Coordination:<\/b>\u00a0Large testing teams can now confidently organize and\u00a0locate\u00a0their respective projects from a single, uncompromised dashboard view.<\/li>\n<\/ul>\n
Enhanced Traceability: Script-Level Xray Visibility within Suites!<\/h2>\n
The Challenge:<\/b><\/p>\n
When managing large API test suites integrated with Jira Xray, it can be difficult to track which individual scripts are properly linked to your test management tools. Since Xray\u00a0determines\u00a0suite execution status based on its underlying linked scripts rather than a standalone suite-level configuration, testers previously had to open each script individually to verify its Xray integration details. This lack of centralized visibility made auditing large test suites time-consuming and\u00a0error-prone.<\/p>\n
The Fix:<\/b><\/p>\n
We have enhanced the visibility of Xray integration configurations directly within the\u00a0qAPI\u00a0test suite view. While direct suite-level configuration\u00a0isn\u2019t\u00a0native to Xray, you can now click the integration icon at the suite level to\u00a0immediately\u00a0view a clear breakdown of the linked scripts alongside their respective Xray integration details and script names.<\/p>\n
How will it help?<\/b><\/p>\n
This update centralizes your integration tracking, making test management much more transparent.<\/p>\n
- \n
- Centralized Integration Audits:<\/b>\u00a0Instantly verify which scripts within a suite are correctly mapped to Xray without toggling back and forth between individual script configurations.<\/li>\n<\/ul>\n
- \n
- Clear Execution Mapping:<\/b>\u00a0Easily understand how your suite-level execution status will flow back to Jira based on a clear visual summary of its underlying scripts.<\/li>\n<\/ul>\n
- \n
- Streamlined Troubleshooting:<\/b>\u00a0Quickly\u00a0identify\u00a0unlinked or misconfigured scripts directly from the high-level suite overview, keeping your test management system perfectly synchronized.<\/li>\n<\/ul>\n<\/details>\n
Flawless Connections: Enhanced iOS Device Streaming!<\/h2>\n
The Challenge:<\/b><\/p>\n
When using Test Generator v2 to automatically build test scenarios via integrations, any friction in the generation flow ruins the speed advantage of using AI. Previously, users faced two major hurdles: the\u00a0initial\u00a0streaming API could experience a bottleneck\u2014taking up to two minutes just to return a “Generating” status\u2014and auto-generated variable actions lacked structural logic. If a script required multiple variables (e.g., Var 1 through Var 5), the AI\u00a0didn’t\u00a0automatically cross-reference its memory to intelligently link those variables to\u00a0subsequent\u00a0data handler steps, forcing testers to manually patch the logic. Additionally, path values for generated steps were buried, making it tedious to audit the AI’s structural paths.<\/p>\n
The Fix:<\/b><\/p>\n
We have rolled out critical enhancements to\u00a0Test Generator v2\u00a0<\/b>to\u00a0optimize\u00a0both backend performance and AI logic. We dramatically accelerated the\u00a0initial\u00a0stream\u00a0API response time, slashing the latency required to\u00a0initiate\u00a0a generation job. On the intelligence front, the AI now automatically names variables inside the “Create Variable” action and intelligently maps those identical variable names to corresponding downstream data handler actions (such as Dynamic Set steps) by referencing its historical memory. Finally, we have explicitly included the exact path values right inside the info section of every step TG generates.<\/p>\n
How will it help?<\/b><\/p>\n
These intelligence and speed optimizations turn AI generation into a fluid, hands-off experience.<\/p>\n
- \n
- Instant Generation:<\/b>\u00a0No more waiting on spinning wheels. The optimized streaming API kicks off your AI generation jobs\u00a0almost instantly, accelerating your overall testing velocity.<\/li>\n<\/ul>\n
- \n
- Flawless End-to-End Variable Logic:<\/b>\u00a0The AI now handles multi-variable data mapping seamlessly. If your test scenario creates five variables, the system automatically tracks them in its memory and binds the correct variable to\u00a0subsequent\u00a0dynamic steps without manual intervention.<\/li>\n<\/ul>\n
- \n
- Transparent Step Auditing:<\/b>\u00a0With path values clearly visible in the info section of each generated step, you can\u00a0immediately\u00a0inspect, verify, and debug the exact navigation paths the AI mapped out.<\/li>\n<\/ul>\n
Seamless SAP Scripting: Real-Time Locator Access!<\/h2>\n
The Challenge:<\/b><\/p>\n
Building automated tests for complex SAP web interfaces (like SAP Fiori) requires highly specific, often intricate element locators. Previously, gathering these unique SAP locators meant testers had to\u00a0frequently\u00a0break their workflow\u2014jumping between separate recording sessions, external inspection tools, or complex documentation just to copy and paste the correct identifiers into their test steps. This context-switching drastically slowed down the test creation process and increased the risk of manual errors.<\/p>\n
The Fix:<\/b><\/p>\n
We have fully integrated\u00a0SAP Recorded Locators<\/b>\u00a0directly into the Web Testing builder. Now, while you are actively constructing your test steps on the canvas, you have immediate, real-time access to the specialized SAP locators you need without ever having to leave the test building interface.<\/p>\n
How will it help?<\/b><\/p>\n
This workflow enhancement removes the friction of testing complex SAP environments.<\/p>\n
- \n
- Accelerated Test Building:<\/b>\u00a0Say goodbye to context-switching. You can now design, configure, and assign the correct SAP locators fluidly within a single, unified workspace.<\/li>\n<\/ul>\n
- \n
- Pinpoint Accuracy:<\/b>\u00a0By pulling recorded locators directly into your builder, you significantly reduce the risk of typos or incorrect element identification, ensuring your tests are robust from the start.<\/li>\n<\/ul>\n
- \n
- Developer-Friendly Experience:<\/b>\u00a0This seamless integration makes building complex SAP web tests faster, more intuitive, and far less tedious for your automation engineers.<\/li>\n<\/ul>\n
Seamless CI\/CD Integration: Jenkins & Azure Plugins for Desktop Testing!<\/h2>\n
<\/h2>\nThe Challenge:<\/b><\/p>\n
As organizations modernize their deployment pipelines, manual testing interventions create significant bottlenecks. Previously, triggering automated scripts for Desktop applications required users to step outside of their primary CI\/CD workflows. Without native plugins for popular orchestration tools, teams had to rely on cumbersome manual triggers or complex, custom-built scripts to\u00a0initiate\u00a0their Desktop Testing suites, resulting in disjointed\u00a0delivery\u00a0pipelines and slower release cycles.<\/p>\n
The Fix:<\/b><\/p>\n
We have officially introduced dedicated\u00a0Jenkins and Azure DevOps plugins<\/b>\u00a0specifically for the Desktop Testing Service. These new plugins empower you to seamlessly trigger and manage your automated desktop application scripts directly from your existing CI\/CD pipelines, bringing the service up to parity with our Web, API, and Mobile testing offerings.<\/p>\n
How will it help?<\/b><\/p>\n
This integration bridges the gap between your desktop application builds and your automated testing ecosystem.<\/p>\n
- \n
- Unified Workflows:<\/b>\u00a0Manage your entire testing strategy\u2014across\u00a0Web, Mobile, API, and now Desktop\u2014from a centralized CI\/CD control plane.<\/li>\n<\/ul>\n
- \n
- Frictionless Automation:<\/b>\u00a0Automatically execute robust desktop automation scripts the moment a new build is deployed,\u00a0eliminating\u00a0manual handoffs and accelerating your time-to-market.<\/li>\n<\/ul>\n
- \n
- Developer Flexibility:<\/b>\u00a0Empower your engineering teams to seamlessly embed desktop quality gates into the familiar Jenkins or Azure environments they already use every day.<\/li>\n<\/ul>\n
Continuous Execution: Connect to Existing SAP Windows!<\/h2>\n
<\/p>\nThe Challenge:<\/b><\/p>\n
When automating complex desktop workflows within SAP GUI, test scripts traditionally\u00a0forced\u00a0a brand-new application instance to launch for every execution. If a test failed midway or if an engineer wanted to resume a specific sequence after manual intervention, they were forced to restart the entire SAP login and navigation flow from scratch. This rigid behavior created duplicate windows, consumed unnecessary system resources, and drastically slowed down test debugging and multi-step process validations.<\/p>\n
The Fix:<\/b><\/p>\n
We have implemented powerful session persistence capabilities within the Desktop Testing Service. Using a robust “attach-to-window” mechanism for Windows environments,\u00a0we’ve\u00a0introduced a dedicated \u2018Connect\u00a0To\u00a0Existing SAP Window\u2019 action. This allows your desktop\u00a0automation\u00a0to intelligently detect and hook into an already-open SAP session instead of triggering a fresh launch.<\/p>\n
How will it help?<\/b><\/p>\n
This workflow upgrade brings true continuity to your desktop SAP automation.<\/p>\n
- \n
- Resume Without Restarting:<\/b>\u00a0Easily continue an automation flow exactly where it left\u00a0off, or\u00a0seamlessly transition between manual steps and automated executions without losing your session state.<\/li>\n<\/ul>\n
- \n
- Optimize\u00a0System Resources:<\/b>\u00a0Prevent your desktop environment from being cluttered with redundant, duplicate SAP application instances during iterative testing and debugging.<\/li>\n<\/ul>\n
- \n
- Accelerate Debugging:<\/b>\u00a0By bypassing the\u00a0initial\u00a0login and navigation sequences, automation engineers can rapidly test and refine specific downstream actions directly within an active SAP window.<\/li>\n<\/ul>\n
Secure & Streamlined: QloudBridge\u00a0Encryption & Login Upgrades!<\/h2>\n
The Challenge:<\/b><\/p>\n
QloudBridge\u00a0acts as the vital tunnel connecting your local desktop environments to the\u00a0Qyrus\u00a0cloud platform. Any weakness in how this data is encrypted during transit poses a significant security risk for enterprise teams handling sensitive test data. Additionally, a clunky or unstable login flow creates unnecessary friction when engineers are trying to spin up local testing sessions. When underlying build issues cause these connections to drop unexpectedly, it disrupts automated runs and delays the entire testing cycle.<\/p>\n
The Fix:<\/b><\/p>\n
We have significantly enhanced the\u00a0QloudBridge\u00a0security architecture\u00a0by rolling out updated, enterprise-grade encryption protocols alongside a completely refined, smoother login flow. In tandem with these security hardening measures, we have successfully resolved underlying infrastructure and\u00a0build\u00a0bottlenecks that were previously causing minor connection instability. These updates have been fully verified on our staging environments and are\u00a0operating\u00a0exactly as expected.<\/p>\n
How will it help?<\/b><\/p>\n
This underlying infrastructure update provides a more resilient and secure testing foundation.<\/p>\n
- \n
- Hardened Data Security:<\/b>\u00a0Your local test data and application traffic are now protected by even stronger encryption during transit, satisfying the most rigorous enterprise compliance standards.<\/li>\n<\/ul>\n
- \n
- Seamless Authentication:<\/b>\u00a0The improved login flow makes it faster and significantly more intuitive to authenticate and connect your local machine to the platform, removing friction from your daily workflow.<\/li>\n<\/ul>\n
- \n
- Unshakeable Stability:<\/b>\u00a0By resolving the core infrastructure issues,\u00a0we\u2019ve\u00a0ensured\u00a0a highly reliable, persistent connection that\u00a0won’t\u00a0unexpectedly drop during your long-running desktop automation suites.<\/li>\n<\/ul>\n
Flawless Connections: Enhanced iOS Device Streaming!<\/h2>\n
The Challenge:<\/b><\/p>\n
Interacting with cloud-hosted iOS devices could sometimes suffer from slight video latency, dropped frames, or momentary disconnections during intense manual testing sessions or heavy automated runs. This streaming instability caused frustration, making it difficult to test UI responsiveness accurately or to confidently debug complex touch interactions on Apple hardware.<\/p>\n
The Fix:<\/b><\/p>\n
We have implemented major infrastructure upgrades to the device streaming protocol specifically for iOS device sessions. This includes optimized video encoding and a much more resilient connection architecture to ensure a rock-solid, high-definition stream between the physical iPhones and iPads in our data center and your local browser.<\/p>\n
How will it help?<\/b><\/p>\n
This underlying upgrade makes remote iOS testing feel like the device is sitting right on your desk.<\/p>\n
- \n
- Silky Smooth Manual Testing:<\/b>\u00a0Experience near-zero latency when interacting with remote iOS devices, allowing for precise gestures, swipes, and taps without frustrating delays.<\/li>\n<\/ul>\n
- \n
- Rock-Solid Stability:<\/b>\u00a0Say goodbye to\u00a0dropped\u00a0sessions and frozen screens. The hardened connection ensures uninterrupted testing, even during extended, deep-dive debugging workflows.<\/li>\n<\/ul>\n
- \n
- Accurate UI Validation:<\/b>\u00a0A crystal-clear, lag-free stream means you can confidently\u00a0validate\u00a0animations, transitions, and overall application responsiveness without the interference of network jitter.<\/li>\n<\/ul>\n
Independent Orchestration: Decoupled Licensing!<\/h2>\n
The Challenge:<\/b><\/p>\n
Previously, using Test Orchestration (TO) was strictly tied to your active module licenses for Web, Mobile, API, or Desktop testing. If one of those underlying service licenses expired or became inactive, it created a hard functional blocker within TO\u2014even for users whose primary role was just to build and manage orchestrated workflows. This rigid dependency disrupted continuous testing strategies and unnecessarily complicated license management across large QA teams.<\/p>\n
The Fix:<\/b><\/p>\n
We have completely decoupled Test Orchestration from these underlying service-module dependencies. TO now\u00a0operates\u00a0as a fully independent orchestration layer. You can seamlessly build, manage, and execute orchestration scripts without requiring active Web, Mobile, API, or Desktop module licenses. Crucially, the platform still securely respects your existing role-based access controls (RBAC) and accurately governs execution capacity based purely on your available Browser and Mobile execution inventory.<\/p>\n
How will it help?<\/b><\/p>\n
This licensing update provides greater flexibility and removes arbitrary administrative blockers from your orchestration workflows.<\/p>\n
- \n
- Uninterrupted Orchestration:<\/b>\u00a0Continue building, managing, and executing your complex test flows without unexpected access blocks caused by individual module license expirations.<\/li>\n<\/ul>\n
- \n
- Streamlined Team Access:<\/b>\u00a0QA managers and orchestration engineers can now freely\u00a0utilize\u00a0the TO workspace to coordinate overarching test strategies without consuming individual service-module licenses.<\/li>\n<\/ul>\n
- \n
- Resource-Based Scaling:<\/b>\u00a0Scale your\u00a0orchestrations naturally\u00a0based on your actual execution capacity (Browser\/Mobile slots) rather than being restricted by module-level licensing.<\/li>\n<\/ul>\n
Batch Execution: Folder-Level Scheduling!<\/h2>\n
The Challenge:<\/b><\/p>\n
Managing and scheduling large test suites can quickly become an administrative burden. Previously, if you wanted to schedule a group of related workflows to run at the same time, you had to configure the scheduling parameters for each workflow individually. This repetitive process was not only tedious and time-consuming but also increased the risk of manual configuration errors across your test batches.<\/p>\n
The Fix:<\/b><\/p>\n
We have introduced a powerful new\u00a0Folder-level Scheduler<\/b>\u00a0within Test Orchestration. Instead of managing individual scripts one by one, you can now apply a single scheduling configuration to an entire folder. This instantly schedules multiple workflows contained within that folder to execute using the exact same parameters.<\/p>\n
How will it help?<\/b><\/p>\n
This enhancement dramatically simplifies the administration of massive test suites.<\/p>\n
- \n
- Massive Time Savings:<\/b>\u00a0Eliminate\u00a0repetitive setup tasks by configuring the schedule once at the folder level, instantly applying it to dozens of underlying workflows.<\/li>\n<\/ul>\n
- \n
- Guaranteed Consistency:<\/b>\u00a0Ensure that all related tests in a specific batch run with the exact same configurations, environments, and timing rules,\u00a0eliminating\u00a0configuration drift.<\/li>\n<\/ul>\n
- \n
- Effortless Scalability:<\/b>\u00a0As your test suites grow, managing execution schedules\u00a0remains\u00a0simple and organized by\u00a0leveraging\u00a0your existing folder hierarchies.<\/li>\n<\/ul>\n
Enterprise-Ready\u00a0Execution: Node CLI Plugin Upgrades for\u00a0qAPI!<\/h2>\n
The Challenge:<\/b><\/p>\n
Managing API performance and functional testing via command-line interfaces across large, enterprise-level teams can get complicated. Previously, fetching project details via the CLI relied on user email addresses, which\u00a0didn’t\u00a0scale well within complex enterprise structures where team-based access is the standard. Furthermore, sharing the results of CLI-triggered test runs often\u00a0involved\u00a0manual data extraction or wrestling with clunky file sharing, creating friction for teams trying to review execution reports quickly.<\/p>\n
The Fix:<\/b><\/p>\n
We have significantly upgraded the\u00a0Node CLI Plugin<\/b>\u00a0for\u00a0qAPI\u00a0to better support enterprise workflows. First, we transitioned project fetching from user emails to team IDs (\/projects?teamId), perfectly aligning the CLI with robust, enterprise-grade project management structures. We also introduced a new feature (\/get-reports-url) that automatically generates a secure CDN link for your execution reports\u2014valid for seven days\u2014directly from the command line.<\/p>\n
How will it help?<\/b><\/p>\n
These CLI enhancements streamline headless API testing for large-scale engineering teams.<\/p>\n
- \n
- Enterprise-Scale Management:<\/b>\u00a0Fetching project data based on Team ID ensures the CLI integrates flawlessly with complex organizational structures and role-based access configurations.<\/li>\n<\/ul>\n
- \n
- Instant Report Sharing:<\/b>\u00a0Automatically generate secure, temporary CDN URLs for your test reports straight from the CLI, making it incredibly simple to share results with your team or attach them to build logs.<\/li>\n<\/ul>\n
- \n
- Streamlined Automation:<\/b>\u00a0With a dedicated CLI plugin type and x-api-key support for URL generation, building secure, automated\u00a0qAPI\u00a0testing pipelines into your CI\/CD processes is smoother than ever.<\/li>\n<\/ul>\n
Seamless Navigation: Enhanced Project Listing!<\/h2>\n
<\/p>\nThe Challenge:<\/b><\/p>\n
As enterprise teams scale their API testing footprints, the number of active projects can grow rapidly into\u00a0the dozens\u00a0or hundreds. Previously, the\u00a0qAPI\u00a0dashboard restricted the project view\u2014only loading the first page of 15 projects and preventing users from scrolling or navigating to see the rest of their portfolio. This forced teams to rely on direct links or search workarounds just to access older or lower-priority projects.<\/p>\n
The Fix:<\/b><\/p>\n
We have resolved this limitation by overhauling the data-fetching and pagination logic within the\u00a0qAPI\u00a0project dashboard. Following successful validation in our staging environments, the fix is fully deployed, ensuring that your complete catalog of projects now loads fluidly and accurately across all pages.<\/p>\n
How will it help?<\/b><\/p>\n
This fix restores complete visibility and smooth navigation to your workspace.<\/p>\n
- \n
- Full Portfolio Visibility:<\/b>\u00a0Effortlessly browse through your entire history of API testing projects without arbitrary UI cutoffs or missing entries.<\/li>\n<\/ul>\n
- \n
- Frictionless Browsing:<\/b>\u00a0Experience smooth, reliable page loading as you scroll through large collections of enterprise projects.<\/li>\n<\/ul>\n
- \n
- Better Team Coordination:<\/b>\u00a0Large testing teams can now confidently organize and\u00a0locate\u00a0their respective projects from a single, uncompromised dashboard view.<\/li>\n<\/ul>\n
Enhanced Traceability: Script-Level Xray Visibility within Suites!<\/h2>\n
The Challenge:<\/b><\/p>\n
When managing large API test suites integrated with Jira Xray, it can be difficult to track which individual scripts are properly linked to your test management tools. Since Xray\u00a0determines\u00a0suite execution status based on its underlying linked scripts rather than a standalone suite-level configuration, testers previously had to open each script individually to verify its Xray integration details. This lack of centralized visibility made auditing large test suites time-consuming and\u00a0error-prone.<\/p>\n
The Fix:<\/b><\/p>\n
We have enhanced the visibility of Xray integration configurations directly within the\u00a0qAPI\u00a0test suite view. While direct suite-level configuration\u00a0isn’t\u00a0native to Xray, you can now click the integration icon at the suite level to\u00a0immediately\u00a0view a clear breakdown of the linked scripts alongside their respective Xray integration details and script names.<\/p>\n
How will it help?<\/b><\/p>\n
This update centralizes your integration tracking, making test management much more transparent.<\/p>\n
- \n
- Centralized Integration Audits:<\/b>\u00a0Instantly verify which scripts within a suite are correctly mapped to Xray without toggling back and forth between individual script configurations.<\/li>\n<\/ul>\n
- \n
- Clear Execution Mapping:<\/b>\u00a0Easily understand how your suite-level execution status will flow back to Jira based on a clear visual summary of its underlying scripts.<\/li>\n<\/ul>\n
- \n
- Streamlined Troubleshooting:<\/b>\u00a0Quickly\u00a0identify\u00a0unlinked or misconfigured scripts directly from the high-level suite overview, keeping your test management system perfectly synchronized.<\/li>\n<\/ul>\n
Ready to Leverage May’s Innovations?<\/h2>\n
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.<\/p>\n
Eager to explore how these advancements can transform your testing efforts? The best way to appreciate the\u00a0Qyrus\u00a0difference is to experience these new capabilities directly.<\/p>\n
Ready to dive deeper or get started?<\/b><\/p>\n
- Streamlined Troubleshooting:<\/b>\u00a0Quickly\u00a0identify\u00a0unlinked or misconfigured scripts directly from the high-level suite overview, keeping your test management system perfectly synchronized.<\/li>\n<\/ul>\n
- Clear Execution Mapping:<\/b>\u00a0Easily understand how your suite-level execution status will flow back to Jira based on a clear visual summary of its underlying scripts.<\/li>\n<\/ul>\n
- Centralized Integration Audits:<\/b>\u00a0Instantly verify which scripts within a suite are correctly mapped to Xray without toggling back and forth between individual script configurations.<\/li>\n<\/ul>\n
- Better Team Coordination:<\/b>\u00a0Large testing teams can now confidently organize and\u00a0locate\u00a0their respective projects from a single, uncompromised dashboard view.<\/li>\n<\/ul>\n
- Frictionless Browsing:<\/b>\u00a0Experience smooth, reliable page loading as you scroll through large collections of enterprise projects.<\/li>\n<\/ul>\n
- Full Portfolio Visibility:<\/b>\u00a0Effortlessly browse through your entire history of API testing projects without arbitrary UI cutoffs or missing entries.<\/li>\n<\/ul>\n
- Streamlined Automation:<\/b>\u00a0With a dedicated CLI plugin type and x-api-key support for URL generation, building secure, automated\u00a0qAPI\u00a0testing pipelines into your CI\/CD processes is smoother than ever.<\/li>\n<\/ul>\n
- Instant Report Sharing:<\/b>\u00a0Automatically generate secure, temporary CDN URLs for your test reports straight from the CLI, making it incredibly simple to share results with your team or attach them to build logs.<\/li>\n<\/ul>\n
- Enterprise-Scale Management:<\/b>\u00a0Fetching project data based on Team ID ensures the CLI integrates flawlessly with complex organizational structures and role-based access configurations.<\/li>\n<\/ul>\n
- Effortless Scalability:<\/b>\u00a0As your test suites grow, managing execution schedules\u00a0remains\u00a0simple and organized by\u00a0leveraging\u00a0your existing folder hierarchies.<\/li>\n<\/ul>\n
- Guaranteed Consistency:<\/b>\u00a0Ensure that all related tests in a specific batch run with the exact same configurations, environments, and timing rules,\u00a0eliminating\u00a0configuration drift.<\/li>\n<\/ul>\n
- Massive Time Savings:<\/b>\u00a0Eliminate\u00a0repetitive setup tasks by configuring the schedule once at the folder level, instantly applying it to dozens of underlying workflows.<\/li>\n<\/ul>\n
- Resource-Based Scaling:<\/b>\u00a0Scale your\u00a0orchestrations naturally\u00a0based on your actual execution capacity (Browser\/Mobile slots) rather than being restricted by module-level licensing.<\/li>\n<\/ul>\n
- Streamlined Team Access:<\/b>\u00a0QA managers and orchestration engineers can now freely\u00a0utilize\u00a0the TO workspace to coordinate overarching test strategies without consuming individual service-module licenses.<\/li>\n<\/ul>\n
- Uninterrupted Orchestration:<\/b>\u00a0Continue building, managing, and executing your complex test flows without unexpected access blocks caused by individual module license expirations.<\/li>\n<\/ul>\n
- Accurate UI Validation:<\/b>\u00a0A crystal-clear, lag-free stream means you can confidently\u00a0validate\u00a0animations, transitions, and overall application responsiveness without the interference of network jitter.<\/li>\n<\/ul>\n
- Rock-Solid Stability:<\/b>\u00a0Say goodbye to\u00a0dropped\u00a0sessions and frozen screens. The hardened connection ensures uninterrupted testing, even during extended, deep-dive debugging workflows.<\/li>\n<\/ul>\n
- Silky Smooth Manual Testing:<\/b>\u00a0Experience near-zero latency when interacting with remote iOS devices, allowing for precise gestures, swipes, and taps without frustrating delays.<\/li>\n<\/ul>\n
- Unshakeable Stability:<\/b>\u00a0By resolving the core infrastructure issues,\u00a0we\u2019ve\u00a0ensured\u00a0a highly reliable, persistent connection that\u00a0won’t\u00a0unexpectedly drop during your long-running desktop automation suites.<\/li>\n<\/ul>\n
- Seamless Authentication:<\/b>\u00a0The improved login flow makes it faster and significantly more intuitive to authenticate and connect your local machine to the platform, removing friction from your daily workflow.<\/li>\n<\/ul>\n
- Hardened Data Security:<\/b>\u00a0Your local test data and application traffic are now protected by even stronger encryption during transit, satisfying the most rigorous enterprise compliance standards.<\/li>\n<\/ul>\n
- Accelerate Debugging:<\/b>\u00a0By bypassing the\u00a0initial\u00a0login and navigation sequences, automation engineers can rapidly test and refine specific downstream actions directly within an active SAP window.<\/li>\n<\/ul>\n
- Optimize\u00a0System Resources:<\/b>\u00a0Prevent your desktop environment from being cluttered with redundant, duplicate SAP application instances during iterative testing and debugging.<\/li>\n<\/ul>\n
- Resume Without Restarting:<\/b>\u00a0Easily continue an automation flow exactly where it left\u00a0off, or\u00a0seamlessly transition between manual steps and automated executions without losing your session state.<\/li>\n<\/ul>\n
- Developer Flexibility:<\/b>\u00a0Empower your engineering teams to seamlessly embed desktop quality gates into the familiar Jenkins or Azure environments they already use every day.<\/li>\n<\/ul>\n
- Frictionless Automation:<\/b>\u00a0Automatically execute robust desktop automation scripts the moment a new build is deployed,\u00a0eliminating\u00a0manual handoffs and accelerating your time-to-market.<\/li>\n<\/ul>\n
- Unified Workflows:<\/b>\u00a0Manage your entire testing strategy\u2014across\u00a0Web, Mobile, API, and now Desktop\u2014from a centralized CI\/CD control plane.<\/li>\n<\/ul>\n
- Developer-Friendly Experience:<\/b>\u00a0This seamless integration makes building complex SAP web tests faster, more intuitive, and far less tedious for your automation engineers.<\/li>\n<\/ul>\n
- Pinpoint Accuracy:<\/b>\u00a0By pulling recorded locators directly into your builder, you significantly reduce the risk of typos or incorrect element identification, ensuring your tests are robust from the start.<\/li>\n<\/ul>\n
- Accelerated Test Building:<\/b>\u00a0Say goodbye to context-switching. You can now design, configure, and assign the correct SAP locators fluidly within a single, unified workspace.<\/li>\n<\/ul>\n
- Transparent Step Auditing:<\/b>\u00a0With path values clearly visible in the info section of each generated step, you can\u00a0immediately\u00a0inspect, verify, and debug the exact navigation paths the AI mapped out.<\/li>\n<\/ul>\n
- Flawless End-to-End Variable Logic:<\/b>\u00a0The AI now handles multi-variable data mapping seamlessly. If your test scenario creates five variables, the system automatically tracks them in its memory and binds the correct variable to\u00a0subsequent\u00a0dynamic steps without manual intervention.<\/li>\n<\/ul>\n
- Instant Generation:<\/b>\u00a0No more waiting on spinning wheels. The optimized streaming API kicks off your AI generation jobs\u00a0almost instantly, accelerating your overall testing velocity.<\/li>\n<\/ul>\n
- Streamlined Troubleshooting:<\/b>\u00a0Quickly\u00a0identify\u00a0unlinked or misconfigured scripts directly from the high-level suite overview, keeping your test management system perfectly synchronized.<\/li>\n<\/ul>\n<\/details>\n
- Clear Execution Mapping:<\/b>\u00a0Easily understand how your suite-level execution status will flow back to Jira based on a clear visual summary of its underlying scripts.<\/li>\n<\/ul>\n
- Centralized Integration Audits:<\/b>\u00a0Instantly verify which scripts within a suite are correctly mapped to Xray without toggling back and forth between individual script configurations.<\/li>\n<\/ul>\n
- Better Team Coordination:<\/b>\u00a0Large testing teams can now confidently organize and\u00a0locate\u00a0their respective projects from a single, uncompromised dashboard view.<\/li>\n<\/ul>\n
- Frictionless Browsing:<\/b>\u00a0Experience smooth, reliable page loading as you scroll through large collections of enterprise projects.<\/li>\n<\/ul>\n
- Full Portfolio Visibility:<\/b>\u00a0Effortlessly browse through your entire history of API testing projects without arbitrary UI cutoffs or missing entries.<\/li>\n<\/ul>\n
- Streamlined Automation:<\/b>\u00a0With a dedicated CLI plugin type and x-api-key support for URL generation, building secure, automated\u00a0qAPI\u00a0testing pipelines into your CI\/CD processes is smoother than ever.<\/li>\n<\/ul>\n
- Instant Report Sharing:<\/b>\u00a0Automatically generate secure, temporary CDN URLs for your test reports straight from the CLI, making it incredibly simple to share results with your team or attach them to build logs.<\/li>\n<\/ul>\n
- Enterprise-Scale Management:<\/b>\u00a0Fetching project data based on Team ID ensures the CLI integrates flawlessly with complex organizational structures and role-based access configurations.<\/li>\n<\/ul>\n
- Effortless Scalability:<\/b>\u00a0As your test suites grow, managing execution schedules\u00a0remains\u00a0simple and organized by\u00a0leveraging\u00a0your existing folder hierarchies.<\/li>\n<\/ul>\n<\/details>\n
- Guaranteed Consistency:<\/b>\u00a0Ensure that all related tests in a specific batch run with the exact same configurations, environments, and timing rules,\u00a0eliminating\u00a0configuration drift.<\/li>\n<\/ul>\n
- Massive Time Savings:<\/b>\u00a0Eliminate\u00a0repetitive setup tasks by configuring the schedule once at the folder level, instantly applying it to dozens of underlying workflows.<\/li>\n<\/ul>\n
- Resource-Based Scaling:<\/b>\u00a0Scale your\u00a0orchestrations naturally\u00a0based on your actual execution capacity (Browser\/Mobile slots) rather than being restricted by module-level licensing.<\/li>\n<\/ul>\n
- Streamlined Team Access:<\/b>\u00a0QA managers and orchestration engineers can now freely\u00a0utilize\u00a0the TO workspace to coordinate overarching test strategies without consuming individual service-module licenses.<\/li>\n<\/ul>\n
- Uninterrupted Orchestration:<\/b>\u00a0Continue building, managing, and executing your complex test flows without unexpected access blocks caused by individual module license expirations.<\/li>\n<\/ul>\n
- Accurate UI Validation:<\/b>\u00a0A crystal-clear, lag-free stream means you can confidently\u00a0validate\u00a0animations, transitions, and overall application responsiveness without the interference of network jitter.<\/li>\n<\/ul>\n<\/details>\n
- Rock-Solid Stability:<\/b>\u00a0Say goodbye to\u00a0dropped\u00a0sessions and frozen screens. The hardened connection ensures uninterrupted testing, even during extended, deep-dive debugging workflows.<\/li>\n<\/ul>\n
- Silky Smooth Manual Testing:<\/b>\u00a0Experience near-zero latency when interacting with remote iOS devices, allowing for precise gestures, swipes, and taps without frustrating delays.<\/li>\n<\/ul>\n
- Unshakeable Stability:<\/b>\u00a0By resolving the core infrastructure issues,\u00a0we\u2019ve\u00a0ensured\u00a0a highly reliable, persistent connection that\u00a0won\u2019t\u00a0unexpectedly drop during your long-running desktop automation suites.<\/li>\n<\/ul>\n<\/details>\n
- Seamless Authentication:<\/b>\u00a0The improved login flow makes it faster and significantly more intuitive to authenticate and connect your local machine to the platform, removing friction from your daily workflow.<\/li>\n<\/ul>\n
- Hardened Data Security:<\/b>\u00a0Your local test data and application traffic are now protected by even stronger encryption during transit, satisfying the most rigorous enterprise compliance standards.<\/li>\n<\/ul>\n
- Accelerate Debugging:<\/b>\u00a0By bypassing the\u00a0initial\u00a0login and navigation sequences, automation engineers can rapidly test and refine specific downstream actions directly within an active SAP window.<\/li>\n<\/ul>\n
- Optimize\u00a0System Resources:<\/b>\u00a0Prevent your desktop environment from being cluttered with redundant, duplicate SAP application instances during iterative testing and debugging.<\/li>\n<\/ul>\n
- Resume Without Restarting:<\/b>\u00a0Easily continue an automation flow exactly where it left\u00a0off, or\u00a0seamlessly transition between manual steps and automated executions without losing your session state.<\/li>\n<\/ul>\n
- Developer Flexibility:<\/b>\u00a0Empower your engineering teams to seamlessly embed desktop quality gates into the familiar Jenkins or Azure environments they already use every day.<\/li>\n<\/ul>\n
- Frictionless Automation:<\/b>\u00a0Automatically execute robust desktop automation scripts the moment a new build is deployed,\u00a0eliminating\u00a0manual handoffs and accelerating your time-to-market.<\/li>\n<\/ul>\n
- Unified Workflows:<\/b>\u00a0Manage your entire testing strategy\u2014across\u00a0Web, Mobile, API, and now Desktop\u2014from a centralized CI\/CD control plane.<\/li>\n<\/ul>\n
- Developer-Friendly Experience:<\/b>\u00a0This seamless integration makes building complex SAP web tests faster, more intuitive, and far less tedious for your automation engineers.<\/li>\n<\/ul>\n<\/details>\n
- Pinpoint Accuracy:<\/b>\u00a0By pulling recorded locators directly into your builder, you significantly reduce the risk of typos or incorrect element identification, ensuring your tests are robust from the start.<\/li>\n<\/ul>\n
- Accelerated Test Building:<\/b>\u00a0Say goodbye to context-switching. You can now design, configure, and assign the correct SAP locators fluidly within a single, unified workspace.<\/li>\n<\/ul>\n
- Transparent Step Auditing:<\/b>\u00a0With path values clearly visible in the info section of each generated step, you can\u00a0immediately\u00a0inspect, verify, and debug the exact navigation paths the AI mapped out.<\/li>\n<\/ul>\n