Please enable JavaScript.
Coggle requires JavaScript to display documents.
SEVEN TESTING PRINCIPLES (Testing shows the presence of defects (Testing…
SEVEN TESTING PRINCIPLES
- Testing shows the presence of defects
Testing can show that defects are present, but it cannot prove that there are no defects
Testing reduces the probability of undiscovered defects remaining in the software, but even if no defects are found, it is not proof of correctness
- Exhaustive testing is impossible
Testing everything (all combinations of inputs and preconditions) is not feasible except for trivial cases
-
To find defects early, testing activities shall be started as early as possible in the software or system development life cycle
-
Testing effort shall be focused proportionally to the expected and later observed defect density of modules
A small number of modules usually contains most of the defects discovered during pre-release testing or is responsible for most of the operational failures
If the same tests are repeated over and over again, eventually the same set of test cases will no longer find any new defects
-
- Testing is context dependent
Testing is done differently in different contexts. For example, safety-critical software is tested differently from an e-commerce site
- Absence of errors fallacy
Finding and fixing defects does not help if the system built is unusable and does not fulfill the user's needs and expectations