Skip to main content

Choose How Test Case Execution Results Are Reported

Understand requirements-based results and latest results, then change the Test Case Execution Result setting for your Jira space.

A Test Case can be used to test more than one requirement. Vansah’s Test Results are requirements based setting controls whether supported views select a result from the current requirement or allow the latest matching result from another testing context.

The setting is enabled by default for a Jira space. It changes how results are selected for display; it does not replace the saved results in individual Test Runs.

Compare the two options

Setting

How supported views select a result

When to use it

Selected: requirements based

Use an execution associated with the requirement being viewed, subject to the case version and applicable filters.

When you need to see whether testing passed for that particular work item or Test Folder.

Cleared: latest matching result

Allow the latest matching execution without restricting it to the current requirement. Other filters and view rules still apply.

When you intentionally want to review a case’s latest result across testing contexts.

A result shown from another context does not demonstrate that the Test Case was executed against the requirement you are currently viewing. Check the Test Run context when making coverage or release decisions.

Example: one Test Case, two requirements

Suppose the same version of DEMO-C46 is linked to two Jira work items. It passes for DEMO-123, then fails in a later execution for DEMO-124.

View

With requirements-based results

With latest matching results

DEMO-123

Passed from the execution for DEMO-123.

May show Failed from the later execution for DEMO-124, when it matches the view’s filters.

DEMO-124

Failed from the execution for DEMO-124.

Failed from the latest matching execution.

This example assumes the same linked case version, no blocking override, and matching report filters. The two original Test Runs keep their own saved results.

Change the setting for a Jira space

A Jira administrator or an administrator for the Jira space can change this setting.

  1. Open Vansah in the Jira space you want to configure.

  2. Open the Settings gear, then select Settings and Compliance → Space Settings → Miscellaneous.

  3. Find Test Case Execution Result and its Test Results are requirements based checkbox.

  4. Select the checkbox to use requirements-based results. To turn it off, clear the checkbox and select Disable in the confirmation dialog.

  5. Wait for the success message, then reopen or refresh the affected testing view to check the result.

The highlighted option is shown in an earlier settings layout. Use the navigation above to reach the same setting.

Clearing the checkbox requires confirmation because it changes how supported views choose the latest result.

Check the view or report you are using

  • The Jira space preference is used by supported work item and Test Folder case lists and related summaries.

  • Test Plans and their iterations have additional execution rules. Individual Test Runs keep the results recorded for that execution.

  • Some reports have their own options, such as Report by Latest/Last result. Check the report configuration as well as the Jira space preference.

  • The Requirements Traceability Matrix uses executions matched to its linked case version and work item context. Do not assume changing this preference changes every gadget.

For the other Jira space options, see Manage Vansah Miscellaneous Settings.

If results differ between views

  1. Open the result details and confirm the Test Run’s work item, Test Folder, or Test Plan.

  2. Check the Test Case version and Test Plan iteration where applicable.

  3. Compare the Jira space preference and any report-specific latest-result option.

  4. Check filters such as Test Environment, release, sprint, or tested date, then refresh the view.

If the result still does not match the expected execution, contact Vansah support with the case key, work item or plan key, run key, and the views and filters you compared.

Did this answer your question?