Tweet
DEFINITION: Set of conditions and/or variables under which a tester will determine if a requirement upon an application is satisfied
Guidelines for writing test cases
1. There is a difference between 2 questions:
- Write test cases for...
- How would you test...
2. First test case - single most important test (happy path)
3. Prioritizing test cases
4. Level of detail. Same test case should be executed in exact same way by each and every tester. Use Test Data.
5. Start with requirements
- test cases MUST match the requirements
- minimal possible change
Writing test cases would normally involve the following:
- Requirements (assumptions of requirements)
- Preconditions (prerequisites)
- Test data
NOTICE: The application is supposed to be in testable condition: avoid test cases such as "button is clickable", "text field accepts input", "check box could be checked"
- test case is 100% derived from requirement
- might fail or pass in just one place
- the smallest possible action in software testing
- the group of test cases is called "test suite"
- the lowest possible level document in software testing
Guidelines for writing test cases
1. There is a difference between 2 questions:
- Write test cases for...
- How would you test...
2. First test case - single most important test (happy path)
3. Prioritizing test cases
4. Level of detail. Same test case should be executed in exact same way by each and every tester. Use Test Data.
5. Start with requirements
- test cases MUST match the requirements
- minimal possible change
Writing test cases would normally involve the following:
- Requirements (assumptions of requirements)
- Preconditions (prerequisites)
- Test data
NOTICE: The application is supposed to be in testable condition: avoid test cases such as "button is clickable", "text field accepts input", "check box could be checked"