Sunday, August 4, 2019

When to STOP testing?

When to STOP testing?

This is a common question which hits every tester's mind. At the initial iterations of the development we are interested to find defects in the product but later on after two, three iterations on the same, testing the same stuff, a question arises on our mind, "When to STOP testing?".

Ideally, as we all know that although it's possible to find all the defects in the software but this will take a lifetime and the process of getting bugs and fixing will go on forever. So there are certain factors to be taken into considerations while testing to fulfil the intent of testing. Testing is a process which is involved so that the current and expected behaviour is matched. Here are some of the conditions when testing can be stopped:
  • Allocated Budget for testing is consumed.
  • When all the planned test cases are executed and passed
  • When timelines for the released are reached.
  • Major Areas are working as per expectations
  • Test coverage is fulfilled as per plan.
 
There can be more such conditions when we testing can be stopped. Let me know your thoughts in comments on "by when do you think testing can be stopped?".

No comments:

Post a Comment

Featured Post

API Automation using Newman - Part II

HTML Report via Newman In previous post we have seen how to setup Newman and execute the collections via Newman in command line. Ne...