Manual testing
A new tab shows step-by-step the tasks to be performed in the given test case. The screenshot below shows a conditional step. The Actual Results field is used to document the current behaviour. As with all description fields, the text can be formatted and tables or images can be added (using the toolbar at the bottom of the results field or by copy & paste).
If the first step is passed, we confirm the result by clicking on the Pass button. The first step will be green, and the next step will be displayed automatically.
The second step is a Test Step. Here we find an Instruction and an Expected Result, as well as the Actual Results field. Again, you are going to document your result in the Actual Results field and set the appropriate status. You can then go through all the individual test steps and mark them as
Pass,
Fail,
Blocked,
Not Applicable.
If you have configured the Actual Result to be a required field in the Project Settings, you cannot set an execution status for the steps until this field is empty. When you set a test step to Pass, you automatically proceed to the next step. You can also use the list of steps on the left or the ribbon button to navigate between the steps.
The Save button allows you to save your execution at any time. As long as you have not marked all steps as Pass or at least one step as Fail or Blocked, you can only Suspend, Save & Close
, i.e. pause the execution. A paused execution can be resumed later in the Execution tab of the test case. Once an execution has been executed completely, you can Finalize, Save & Close
it to save the result in a final and audit-proof way or only Save & Close
if you want to edit the execution later.
All executions including the execution details can then be viewed in the Execution tab where they can be continued, edited or finalized. If you discover a defect during your execution, you can set the corresponding step to fail and then create a new defect directly from the execution or link an existing defect to this execution. If you successfully execute a test case that is linked to a defect, you can review the related defects from the execution and set it to closed, for example.
Last updated