Objective :They all essentially function to reduce risk and qualify the testing effort. So, a good test provides some measurable value to the organization with the explicit purpose of:
Steps 1.You should have 3-8 test steps in a test case. If you only have a few test steps, you should probably consider making a checklist instead its not worth your while to keep track of a lot of small test cases when a checklist will do the job just as well.
2.When testers report defects based on the test case, they should indicate which test step failed, in order to make troubleshooting easier.
3.When you write a test case, you dont need to specify the expected result for each test step if the result is obvious.
4.If your test case has too many test steps you ought to think about breaking up the test case into a set of smaller ones. If the test case contains a long list of test steps, and an error occurs, the developer will have to backtrack and repeat all the test steps, which he or she might not do by accident, or out of laziness.
Ready to start your tutorial with us? That's great! Send us an email and we will get back to you as soon as possible!