How-to complete testing:
- Complete all test cases that had been written.
- Signed off from testing.
- Test exit report produced.
- The team can not find any more bugs.
- Managers decided no more testing is required.
- PM decided that all risks are evaluated and no more testing required.
- You confirmed all requirements are met.
- All acceptance criteria are met.
- Deployed to production.
What’s your way of communicating testing is completed?
What if, it’s all wrong to claim testing is completed or done?
First, what does that even mean “testing is completed or done”? Try to describe the benefits by “completing your testing” in plain English.
Second, why should anyone care about if testing is completed or not?
Third, how can you measure testing is actually completed?
Last but not least, think about why are we testing? What is the purpose of testing? Testing should never be anyone’s goal or aim to complete or done. It is only one way of evaluating and learning about the #risks and #quality of the product at a point of time.
Focus on asessing risks (social and technological) & quality of the product. STOP further testing if business is satisfied and accepts risks of releasing to production.
Testing can never be completed, but STOPPED