Key Highlights 26.7.0

Here’s a quick look at the most important updates in this release – v26.7.0. Explore the latest enhancements, new features, and important fixes included in this release to improve your overall experience and productivity.

• Enhanced Versioning Actions The Bitbucket or Azure DevOps Actions now provides the following enhancements for managing and comparing test artifact versions:

  • The Version History is renamed to Bitbucket or Azure DevOps Actions across the Element Repository, Test Case, Reusable Library, End-to-End (E2E), and Test Data Management modules.
  • Pull Window: This now supports the following actions for one or more selected test artifacts:

    • Restore test cases: Restores selected versions.
    • Restore to new testcase: Creates new test cases from selected versions.
    • Compare with current: Compares selected versions with the current versions and highlights the artifact name and position.
  • Push Window: This now supports Compare option for one or more selected test artifacts. The comparison view displays the Current View and Pushed Version side by side, with Added, Edited, and Removed changes highlighted. You can also navigate between multiple selected artifacts using the artifact name and position.

  Learn more
• Enhanced Multi Factor Authentication (MFA) Automation with Generate TOTP action You can now use the Generate TOTP action to generate a time-based one-time password (TOTP) for applications that use multi-factor authentication (MFA). The action accepts an encrypted 32 Base secret key generated using the Advanced Encryption Standard (AES) method, decrypts it in memory, and generates the OTP to use during test execution. This simplifies MFA automation by allowing TOTP-based authentication to be handled directly within your test cases. Learn more
• API Assertions for Response Validation

  API Assertions are now available for validating API responses. You can use the following supported Assertion types:

  • Status code: Validates that an API returns the expected HTTP status code.
  • JSONPath match: Extract and validate values from JSON responses using JSONPath expressions, with support for storing the extracted value for reuse in subsequent test steps.
  • Response time: Checks whether the API response time is within the expected limit.
  • Response body contains: Validates whether the API response body contains the expected text or value or matches the expected regex pattern.
  • Response body not contains: Validates whether the API response body does not contain the expected text or value.

  Learn more