Seven Principles Flashcards
Testing Shows Presence of Defects
Whatever count of defects there are always more. In case no defects are found, it’s not proof of correctness
Exhaustive Testing Is Impossible
Alternate, conduct risk analysis and priorities should be used to focus on testing
Early Testing
1) Review drafts
2) Save time and cost
3) To find defects
4) Testing activities must be coordinated with the corresponding development activities
5) Earlier or prevent defects being introduced
6) Get involved as soon as possible in the development lifecycle
Defect Clustering
It is possible that the more the defects are clustered in smaller modules compared to being distributed among bigger and other modules. In this regard, a tester must consider and prepare proportional test cases to test such system
Pesticide Paradox
If the same tests are repeated over and over again eventually the same set of test cases will no longer help find new defects. To overcome this “Pesticide Paradox” test cases to to be regularly Review and Revised
Testing Context Dependent
Testing is done differently in different context. Two different software are test with a different strategy. Example: e-comm vs security
Absence-of-Error is a Fallacy
Meeting the requirement is equally important. Finding and fixing a defect does Not help if the system built doesn’t fulfill the end-users needs and expectations