Software Engineering : Software Testing Principles - Webriology

Crucial Insights and Information About the Industry to Our Audiences

Software Engineering : Software Testing Principles

Share This



Software Testing :

Software testing has many definitions but in simple terms, Testing an application on the basis of client requirements.


To test an application or software, we need to follow certain principles to make our product defect-free, and also help test engineers to test the software with their effort and time.

There Are Seven Principles to Perform Software Testing.

  • Testing shows the presence of defects.
  • Exhaustive Testing is impossible
  • Early Testing
  • Defect clustering
  • Pesticide paradox
  • Testing is context depending
  • Absence - of - error fallacy 

- Testing Shows the Presence of Defects :

The testing process can show how many defects are present, but we can’t prove that as there are no defects. So, 100% defect-free software is not possible.

- Exhaustive Testing :

If we test functionality with all possible inputs called exhaustive Testing, but always exhaustive testing isn’t possible. It requires more resources

- Early Testing :

Start testing activities as soon as possible in the development life cycle called early testing (before coding)

- Defect Clustering:

Sometimes small modules produce more defects than bigger functionality. So, we have to perform more testing on every module.

- Pesticide Paradox :

While executing test cases, if test cases are not producing any defects then add more test cases or modify the test case to finding defects. 

- Testing is Context Depending :

Testing is a basic requirement depending, so, different kinds of applications testing differently. 

- Absence-of-Errors Fallacy :

if you find more defects without fulfilling customer requirements, those defects are not useful.



No comments:

Post a Comment

Pages