In this post we will discuss about some tips on Test case design.
You can also check my previous articles on:
- What is Performance Testing?
- Top-Down and Bottom-up Approach in Integration Testing
- Selenium interview questions and answers
(1) A test case must be designed to be reusable i.e.It should be executed on future versions of software also.
(2) A test case must consists constant results to different testers,while executingon software under testing.
(3) A test case name must start with Verify/Validate/Check.
(4) A test case must be specific to the testing object(field)or operation in software under testing.
(5) A test case must be divided into positive or negative.
(6) A test case must be divided into sub test cases to keep them as short.
(7) A test case contains 10 to 15 test steps procedure as maxium.
(8) The test case must specify defect id when the test case became failed.
(9) A test case must be reviewed by test lead along with BA/SA to ensure the coverage of functionality in that test case.
(10) A test case must be specify what that tester wrote and what tester has to perform and the response of software under testing.
(11) A test case must be approved by customer site representatives or PM.
You can also check my previous articles on:
- What is Performance Testing?
- Top-Down and Bottom-up Approach in Integration Testing
- Selenium interview questions and answers
(1) A test case must be designed to be reusable i.e.It should be executed on future versions of software also.
(2) A test case must consists constant results to different testers,while executingon software under testing.
(3) A test case name must start with Verify/Validate/Check.
(4) A test case must be specific to the testing object(field)or operation in software under testing.
(5) A test case must be divided into positive or negative.
(6) A test case must be divided into sub test cases to keep them as short.
(7) A test case contains 10 to 15 test steps procedure as maxium.
(8) The test case must specify defect id when the test case became failed.
(9) A test case must be reviewed by test lead along with BA/SA to ensure the coverage of functionality in that test case.
(10) A test case must be specify what that tester wrote and what tester has to perform and the response of software under testing.
(11) A test case must be approved by customer site representatives or PM.