A Test Case can be blocked during testing for a number of reasons, including unavailability of test data, dependency on other Test Cases not yet completed, Issues with the application under test, or unavailability of test environment.
It’s important to identify the root cause of the blockage and take appropriate actions to unblock the Test Case as soon as possible. This will help ensure that the testing process stays on track and the project timeline is not impacted.
In Vansah, a Test Case can be blocked against a specific requirement it is linked to, such as a Jira Issue or a Test Folder. When a Test Case is blocked against a requirement, it prevents users from testing the Test Case against the linked requirement and Test Reports will reflect the number of Blocked Cases against it.
In your Jira workspace, it is possible to globally block a Test Case, which means that it cannot be tested regardless of the Issue, Test Folder, or Test Plan it is associated with. This global block will also affect all Jira projects that have this Test Case.
Outcome of Blocked Test Cases on Test Execution
Planned Test
If a Test Case is blocked then the overall result for a Planned Test will no-longer consider the Blocked Test Case result, but it will consider the Test Case as part of the number of planned tests.
Miscellaneous Test Run
If a Test Case is blocked, you will no longer be able to update the test result without unblocking the testcase.
Blocking a Test Case Globally From a Test Case
- Open the Test Case
- Select More options
- Select Block Test Case
- Confirm to Block the Test Case
Blocking a Test Case Globally From the Vansah Board (Test Folder)
- Select the Test Case from the Grid
- Click on More options
- Select Block Test Case
- Confirm to Block the Test Case
Hovering cursor over the Result Dot for a Blocked Test Case will open a tooltip message displaying more information such as Blocked by, Blocked Date and Time and Blocked Status etc.
