CLOSED Release: Last updated 5th of November 2024

What’s New

Introducing Active and Default Versions for Improved Test Management Flexibility

Vansah Test Case versioning has introduced a new set of features to enhance flexibility and control in managing Test Case versions across different requirements.

Active vs. Default Versions in Vansah:

Active Version:

An Active version is specific to a particular requirement (e.g., a Jira Story, Test Folder, or Test Plan).
Multiple versions of a Test Case can be associated with a requirement, but only one version is designated as Active for that specific requirement.
When you associate a Test Case with a requirement, the default Test Case version at that time becomes the Active version for that requirement.
You can change the Active version for a requirement without affecting other requirements using the same Test Case.
This allows for different versions of the same Test Case to be active across various requirements, providing flexibility in test management.

Default Version:

The Default version is a global setting for the Test Case itself, not tied to any specific requirement.
It serves as the version Vansah chooses when creating a new Test Run without specifying a particular version.
The Default version should typically be the most recent approved version ready for execution.
It must be set manually by users and can be changed at any time.
The Default version cannot be deleted .
It is reflected in Vansah custom fields such as Manual Test Steps, Cucumber Scenario, Test Type, and Pre-Conditions association.

Key Differences:

Scope: Active versions are requirement-specific, while the Default version is global for the Test Case.
Purpose: Active versions allow different versions of a Test Case to be used across various requirements simultaneously. The Default version serves as the go-to version for new Test Runs and is reflected in custom fields.
Flexibility: You can have multiple Active versions (one per requirement) but only one Default version at a time.

This versioning system allows for greater control and flexibility in managing Test Cases across different requirements and stages of development, enabling teams to maintain multiple versions of tests as the application under test evolves.

Standalone Test Run Viewing for Test Plans

Seamlessly access and manage individual test case executions while maintaining full traceability within your test plans. This enhancement allows users to view and manage executed test cases within a test plan individually, offering greater flexibility and control over the testing process.

New Test Plan Repository Folder Tree

Test Plan Folders now share the same Tree view experience which we recently updated for Test Case Folders. This now completes our upgrade giving our users a better folder tree management experience across both Test Cases and Test Plans.

Vansah Intelligence 2.0 (AI Test Case Generation)

We are thrilled to announce the launch of Vansah Intelligence 2.0, a ground-breaking AI update that redefines Test Case generation.

Key Features

Context-Aware Test Cases: Our AI analyzes your Jira issues in depth with a configurable option allowing users to Add more Issue properties to be used by Vansah Intelligence creating test cases that are perfectly aligned with your project's context and requirements.
Comprehensive Coverage: Ensures all aspects of your software are thoroughly tested, minimizing the risk of overlooked scenarios.

Test Plans now have "New Test Run" for a Test Case.

We're excited to announce a significant improvement to test case execution within Vansah's Test Plans.

Key Updates:

Multiple Test Runs: Users can now execute multiple test runs for a single test case within a Test Plan iteration.
Historical View: Previous test runs are now accessible, allowing for easy review and management.

Vansah Reports

Vansah Reports, is now available within the Vansah Board for each Jira project. These reports offer valuable insights into your testing process, helping you track progress, identify bottlenecks, and ensure comprehensive test coverage.

Report Categories:

Test Summary
Test Execution
Burnup Execution
Traceability

Bug Fixes

VANS-2428 - Runtime Error Occurs When Clicking "Failed" Comment in Jira Issue for Test Case Execution
VANS-2445 - Implement HTML Markup Support for Test Case Import Functionality
VANS-2526 - UPDATE TEST STEP API Error: "resultData Required" When Updating stepData
VANS-2553 - Missing Functionality: Unable to Unlink Test Plan from Test Plan Folder
VANS-2538 - Test Plan Data Missing in Exported File After Export Operation
VANS-2448 - New Jira Projects Lack Automatic Creation of Default Test Case Status
VANS-2541 - Test Plan Count Not Incrementing When Cloning Test Plan Within a Folder
VANS-2563 - Selecting Issue Filter and changing to List filter for Test Plan configuration was not clearing the previous issues selected.
VANS-2615 - Test Folder Traceability Report not displaying data when user clicks on In-Progress information.
VANS-2675 - Incorrect Step Number Reference shown in Jira Issue Comment

Support

If you encounter any issues or require assistance, our dedicated support team is available to help. Contact us through the support portal or email us at [email protected].