This topic summary covers Knowledge Organiser: Testing within Testing for GCSE Computer Science. Revise Testing in 3.2 Programming for GCSE Computer Science with 15 exam-style questions and 8 flashcards. This is a high-frequency topic, so it is worth revising until the explanation feels precise and repeatable. It is section 7 of 7 in this topic. Use this topic summary to connect the idea to the wider topic before moving on to questions and flashcards.
Knowledge Organiser: Testing
Key Terms
- Normal data: Typical valid input the program should accept (e.g. age 25)
- Boundary data: Values at the exact edges of the valid range (e.g. 17, 18, 65, 66)
- Erroneous data: Invalid input the program should reject (e.g. -5, "abc")
- Iterative testing: Testing each module as it is developed, during programming
- Final testing: Testing the complete program end-to-end once development is finished
- Alpha testing: In-house testing carried out by the development team
- Beta testing: Testing by a limited group of real users before full release
Must-Know Facts
- Every test must state the test data, the type, and the expected outcome
- Boundary testing must cover both sides: just inside AND just outside the limit
- Iterative testing finds bugs early — earlier is cheaper and easier to fix
- Normal data should be accepted; erroneous data should be rejected
- A test without an expected result is not a valid test
Key Concepts
- Memory aid: NBE — Normal, Boundary, Erroneous
- For valid range 18–65: boundary values are 17, 18, 65, 66
- Test plan columns: Test number | Test data | Type | Expected result
- Alpha before beta: developers test first, then real users test
Common Mistakes
- Missing boundary values on both sides: For a valid range of 18–65, you must test 17 AND 18 (lower boundary) AND 65 AND 66 (upper boundary) — just testing 18 and 65 is incomplete
- Not stating expected results in test plans: A test without a clearly stated expected outcome is not valid — examiners require test data, type, AND expected result
- Confusing alpha and beta testing: Alpha is in-house testing by the development team; beta is testing by real external users before full release
- Confusing erroneous with boundary data: Erroneous data is completely invalid (wrong type, outside all reasonable range); boundary data is valid but at the edge of the acceptable range
- Saying iterative testing means testing at the end: Iterative testing happens during development, after each module is written — it is the opposite of leaving all testing until the end
Practice questions for Testing
A program accepts scores between 0 and 100. Which value is an example of erroneous test data?
Explain what a logic error is and give one reason why it is harder to find than a syntax error.
Quick recall flashcards
What is normal test data?
Typical, everyday values the program should handle
What is boundary test data?
Values at the edge of valid ranges (just inside and outside limits)