Lecture 3 - Test Cases and Test Suites -> Quick Intro -> Test Case Structure -> Results Of The Test Case Execution -> Useful Attributes Of The Test Case -> Data-Driven Test Cases -> Maintainability Of Test Cases -> The Number Of Expected Results Inside One Test Case -> Bad Test Case Practices -> Test Suites -> States Of A Test Case -> The Importance Of Creativity -> Three Important Factors That Affect Test Cases -> Checklists -> Lecture RecapChecklists are simple test cases that assume that the test case executor knows the application well, or can figure out how the application should work. As a rule, advanced verifications like DB queries are not included in checklists.
Example:
Action | Expected | Check |
Do transaction with Visa | Success | |
Do transaction with MasterCard | Success | |
Do transaction with AmEx | Success |
Before executing the test case, print out the checklist and put a checkmark if something works and no checkmark if something is broken or the execution is blocked.
For projects of low importance, it’s okay to use checklists even after several years of existence.
For projects of high importance, highly formalized test cases are a must. Next ->
Lecture 3 - Test Cases and Test Suites -> Quick Intro -> Test Case Structure -> Results Of The Test Case Execution -> Useful Attributes Of The Test Case -> Data-Driven Test Cases -> Maintainability Of Test Cases -> The Number Of Expected Results Inside One Test Case -> Bad Test Case Practices -> Test Suites -> States Of A Test Case -> The Importance Of Creativity -> Three Important Factors That Affect Test Cases -> Checklists -> Lecture Recap
