Release Notes: Version Control, Rerun Failed, Team Folders
 |
Version Control for Test Cases
This feature introduces test case versioning, similar to the existing functionality for rules, enabling full visibility and control over changes.
When you create a new test case and navigate to the Edit Test Case page, a new tab called Version History appears at the bottom. Initially, only the first version is displayed. As soon as you make updates, such as renaming the test case or modifying steps, the system automatically creates a new version. Each version records key details, including the timestamp, author, and change type.
The Version History tab allows you to:
- View all previous versions of a test case
- Compare differences between versions, organized by categories such as name, labels, and steps
- Restore any previous version with a single click
For example, after updating a test case with new steps or labels, you can compare it against earlier versions and roll back if needed. Once restored, the test case reflects its original state, including name, steps, and labels.
The system also identifies how each change was made:
- Manual updates: Standard edits made directly in the test case editor
- Find and Replace: Bulk updates are logged and clearly labeled, showing exactly what was modified
- API updates: Changes made via API are tracked and marked as “Updated via API” with full details
If no method is specified, the change was made manually.
Version history is also preserved across additional workflows:
- Test case refactoring: Updates performed through bulk actions (e.g., Find and Replace) create new tracked versions
- Test case duplication: When copying a test case to another suite, the system retains its origin details, including source suite and version mapping
- Cross-suite visibility: You can access the original version history of a copied test case without leaving the current suite
For instance, when a test case is copied to another suite, the Version History tab shows where it originated and allows you to review or restore earlier versions from the source.
This ensures complete traceability, consistency, and control over test case evolution across all workflows.
Team-based Ownership for Folders
This feature introduces team-based ownership for folders in the Homepage, improving organization and access control within a company.
When a user belongs to multiple teams (for example, Team 1 and Team 2) and creates a new folder, they will see an Owner Team dropdown field. This allows the user to select which team will own the folder.
Once a team is selected, the folder is assigned to that specific team, ensuring clear ownership, better collaboration, and more structured resource management.
Rerun Failed Tests
This feature enables users to rerun only failed test combinations, helping reduce execution time and focus on unresolved issues.
For example, in a test run where one test passes and another fails for a specific dataset combination, you can select Rerun Failed Combinations (located in the Run Details page of any suite run). This action creates a new test run that includes only the failed combinations.
Before the rerun starts, a confirmation message ensures that only test cases that still exist will be included in the new run. Once executed, the system runs only the failed combinations, while previously passed test cases are excluded. Any combinations that are not part of the rerun are marked as not started.
This targeted rerun capability allows teams to quickly validate fixes without re-running successful scenarios, improving efficiency and test cycle speed.
