The Fundamentals of Testing
The Fundamentals of Testing
Study why software fails, what testing does, the general testing principles, the test process, and the psychology of effective testing.
Why Software Fails
Human errors can become defects in work products, and defects may cause observable failures. Testing helps detect problems, reduce risk, and provide information about quality.
A useful causal chain is: Error → Defect → Failure. A false positive reports a failure when behaviour is actually correct; a false negative misses a real failure.
Essential Testing Terms
Tap each card to review the vocabulary used throughout Chapter 1.
General Testing Principles
These principles guide effective testing and help avoid common misconceptions.
Compare Key Concepts
Several Chapter 1 concepts are closely related but should not be treated as interchangeable.
Testing
Systematically examines work products and software to find and report defects, evaluate behaviour, and provide information about quality.
Debugging
Identifies the cause of a defect and corrects it. Testing and debugging are distinct activities, although both contribute to a quality result.
The Test Process
The generalised test process contains seven activity groups. They have a broad sequence, but can overlap, run concurrently, and be revisited.
Test Activities and Work Products
Open each activity to review its purpose and typical outputs.
Testing in Practice
Explore important relationships and practical distinctions from the chapter.
Key Takeaways
Use these high-yield points as a final revision pass before the knowledge check.
Testing can show that defects are present, but it cannot prove that software is completely defect-free. Testing should be prioritised according to risk and importance.
Do not equate “no defects found” with “good enough to release.” Software must also satisfy user needs, requirements, and relevant quality expectations.
Knowledge Check
Answer each question once. The correct answer and an explanation appear immediately.