Statuses of Tests and Test Steps

When you set the status of a test step in the Manual Testing window, the status of the test changes. The following table shows how Silk Central calculates the test status depending on the statuses of the test steps:

Status	Description
Passed	If all steps are passed, the test status is set to `Passed`. No status reasons from test steps are propagated to a test's status.
Failed	If all steps are executed and at least one step is failed, the test status is set to `Failed`. The status reason of the first failed test step is used as the failed status reason for the test.
Not Executed	As long as all steps are not executed, the test status is set to `Not Executed`. The status reason of the first not-executed test step is used as the not executed status reason for the test. If you change the status of at least one step, the test status is set to `In Progress`.
In Progress	Until every step is executed, the test status is set to `In Progress`.

You can also set the test status manually. In the overview area of the Manual Testing window, or in the test steps area of a test step, click (Select Status) beside the status icon and select a status. See Status Reasons for detailed information about defining reasons for each status.

Apart from the test's status, you can also set a test to being blocked. Setting a test to blocked is useful to indicate that the test cannot be continued due to certain restrictions, for example a problem with the IT infrastructure.

Note the following:

A manually set test status overwrites the automatically calculated one.
If you change a step status afterwards, the test status is calculated again.
You can manually set a test status back to Not Executed. However, Silk Central will never automatically set back the test status to Not Executed.
You can manually set a test status to In Progress, even if you do not change any step status.