New Feature

Take Control of Your Pipeline: Stop Executions on Demand!

The Challenge:

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

The Fix:

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

How will it help?

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

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

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

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

Improvement

Set It Once: Unified Environment Selection for Test Orchestration!

The Challenge:

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

The Fix:

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

How will it help?

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

Improvement

Recorder Now Intelligently Fixes and Completes Your Tests!

The Challenge:

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

The Fix:

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

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

How will it help?

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

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

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

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

Improvement

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

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

The Fix:

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

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

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

How will it help?

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

Improvement

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

The Challenge:

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

The Fix:

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

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

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

How will it help?

These enhancements provide you with richer, more actionable reports.

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

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

New Feature

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

The Challenge:

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

The Fix:

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

How will it help?

This feature significantly improves collaboration and understanding within your workspace.

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

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

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

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

New Feature

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

The Challenge:

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

How will it help?

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

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

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