Test Conditions

Test conditions example is: "Customer can enter a valid username."  

Test condition expected result is: "The system accepts the data without error."

This is as opposed to Test steps which could be:

1. Open program.

2. Open login page.

3. Enter username XXXXX and password YYYYY

Obviously the test steps can be a lot more complex in a given real world situation so the test conditions are set and can be reviewed by business users for business functionality as opposed to the test steps technical functionality.

Would appreciate any feedback on this.

Thanks,

Robbie

Is there a reason why you cannot put the test conditions in as test steps? Even though you don't do them in sequence, you can read all the test conditions and pass/fail them if the test meets the conditions.

Regards

Sarah