V6.12.0 (October 2025 Release)

Improvement

At-a-Glance Clarity: Longer Suite Names in Mobile Test Reports!

The Challenge:

Previously, on the execution results page for Mobile Testing, long test suite names were often truncated to fit in the designated space. This made it difficult for users to quickly identify which suite a report belonged to without hovering their mouse over the text to reveal the full name, creating a minor but persistent usability issue.

The Fix:

We have adjusted the user interface to increase the length of text displayed for the suite name in the execution report. This change allows for longer, more descriptive suite names to be shown without being cut off.

How will it help?

This is a straightforward quality-of-life improvement that enhances readability and usability. You can now identify your test suites at a glance without needing to hover, making it faster and easier to navigate and find the specific mobile execution report you are looking for.

New Feature

The Unviewable, Now Viewable: True Offline Simulation for iOS Devices!

The Challenge:

Accurately simulating a complete loss of internet connectivity on iOS devices presents a major technical hurdle: how do you continue to view and interact with a device’s video stream after you’ve taken its network offline? This made it incredibly difficult to test the real-time behavior of an app at the exact moment it loses connection.

The Fix:

We have implemented a sophisticated solution for offline network throttling on iOS devices. We’ve created a new “Offline” network profile that effectively simulates zero network speed. To overcome the viewing challenge, our system now seamlessly switches the video stream in the background: it uses low-latency WebRTC when the device is online and intelligently switches to a different stream (via FFmpeg/Ant Media) the moment you go offline, ensuring you never lose sight of the device screen.

How will it help?

This powerful new feature allows you to reliably and accurately test how your iOS application behaves in a true “no internet” scenario, while still being able to watch the app’s response in real-time. You can now easily validate:

• Offline functionality and data caching.

• Graceful error handling and user messaging during connection loss.

• The application’s behavior when transitioning between online and offline states.

This makes a previously difficult-to-test condition simple and accessible, enabling you to build more resilient and robust iOS applications.

New Feature

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

The Challenge:

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

The Fix:

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

How will it help?

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

Improvement

Consistent Clarity: Key Diagnostics Now in All qAPI Report Views

The Challenge:

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

The Fix:

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

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

How will it help?

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

New Feature

Retry with Confidence: Improved Interactions with Local Agents!

The Challenge:

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

The Fix:

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

How will it help?

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