7 software testing principles every tester needs to know

Tram Ho

  1. Testing introduces defects but does not prove that the product is free from defects
  2. Exhaustive testing of all cases is not possible: Hence it is necessary to apply suitable test scenario design techniques so that with a certain number of test perspectives but still have high requirement coverage.
  3. Early testing saves time and costs: Testers should be involved in the software development process as early as possible, right from the requirements document stage in the draft.
  4. Fault clustering: Errors are often not evenly scattered across functions, but 80% of defects are often concentrated in 20% of product functions. Therefore, when performing tests, testers need to judge error clustering when there are many defects occurring in a certain functional group, spending more resources on high-risk and error-prone areas.
  5. Pesticide paradox: If you keep executing tests on a set of Test cases, it is difficult to find new bugs. Therefore, it is necessary to regularly think about new testing perspectives and update the Test case suite
  6. Context-dependent testing: Depends on each context to apply appropriate testing techniques and strategies
  7. Misconception about no bugs: After testing is done, even if the programmer fixes all the bugs reported by the tester, it is not guaranteed that the product has succeeded, it is not guaranteed that the product is successful. The product has met the expectations of the end user. Therefore, in the testing process, testers need to put themselves in the role of end users, understand customers and give suggestions to improve product quality and experience.
Share the news now

Source : Viblo