Second Column: Test Scenario
This is where I describe what the user does to get the expected result to happen.
Third Column: Expected Result
What's supposed to happen when the scenario is executed.
Fourth Column: <font color="red">Post Condition</font>
What the user should do to undo the damage they did executing the test cases to let subsequent test cases start smoothly without setup that depends on prior test cases.
(5th, 6th, 7th column: Comments, Pass/Fail, Actual Result respectively)
The question is about "Post Condition." I'm in love with the concept but not the column heading. My consultant buddy says that other companies sometimes use this term in place of "expected result" and I don't want any confusion. What would you call it?
I like Reset and Restore, but I don't know if I like the condition part. If there are multiple steps here, it could e Steps to Restore or Reset. Maybe Restore Default Configuration? Since the given steps should always lead back to one baseline configuration, you could say that this is your default configuration.
[ QUOTE ]
Post execution, cleanup, reinitialization
A VM environment might solve your 4th column issues if it's a PC app.
[/ QUOTE ]
This is just for manual testing, this column is for things like "return to the first screen," since the test case might send the testers off the beaten track somehow and I'm trying to reduce interdependency between test cases.