Skip to main content

Test Case Execution Result

Keep enabled for structured, requirement-driven testing or disable when reporting is not requirement-dependent.

Updated today

By default, Vansah treats Test Case results as requirement-specific, meaning:

  • The latest test result is tied to the requirement or context (such as a Jira Issue, Test Folder, or Test Plan) where the Test Case was executed.

  • A single Test Case can have different results across different requirements depending on its execution context.

Impact When Enabled (Default State)

To enable go to Misc Settings in your Jira project.

Behavior

Explanation

Context-aware results

Test results are linked to the specific requirement being validated.

Accurate traceability

You can trace which requirement passed/failed based on its specific test run.

Ideal for structured testing

Especially helpful for teams testing across multiple stories, sprints, or releases.

Example:
If Test Case TC-101 is executed for:

  • Requirement A – Result: Pass

  • Requirement B – Result: Fail
    You’ll see different outcomes depending on the requirement.

Impact When Disabled

To disable go to Misc Settings in your Jira project.

If you deselect the option (i.e., uncheck "Test Results are requirements based")

Behavior

Explanation

Global latest result

Vansah will show the last execution result of the test case, regardless of requirement.

No context sensitivity

All references to that test case will show the same status (pass/fail/etc), even across different requirements.

Potential confusion in traceability

May lead to misunderstandings in Test Reports if the test was run under a different context.

A confirmation dialog will appear:

To confirm, select Disable to change how Test Case results are reported based on the Jira project. This will get the latest result of a Test Case irrespective of where it was last executed from.


Recommendation

  • Keep enabled for structured, requirement-driven testing (ideal for agile, regulated, or large-scale projects).

  • Disable when reporting is not requirement-dependent.

Did this answer your question?