Executing Test Steps and Recording Results
If the test which has been selected for running has steps defined in it, those steps are displayed in the test runner dialog, with the first step selected for execution. The step that is currently being executed is highlighted and has a small 
icon corresponding to it. Its Actual result field is open.
icon corresponding to it. Its Actual result field is open.The tester reads and executes the action of the test, then compares the result with the expected result, and records the difference in the Actual result field, if necessary. The Actual result field can be edited with the rich text editor. By clicking Pass Step, Fail Step, Block Step, or Not Applicable, the focus moves to the next step.
You can return to any previous step by clicking the step. You can then update the Actual result value or the step's result.
When all the steps are completed, the runner asks you if you are ready to move to the next test case. At this point, you can optionally report bugs and execute any post-actions. If the tester agrees, then the test runner dialog moves to the next available test.
If all test cases are completed in the current test set, then the execution is done, and the runner closes automatically. The test set moves to Finished status.
If there are no steps defined for the current test case or the tester does not want to execute all of them for some reason, the user can mark the current test case as passed, failed, or blocked using the buttons at the bottom of the test runner dialog.