This introduction covers Finding Bugs Before Users Do 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 1 of 7 in this topic. Use this introduction to connect the idea to the wider topic before moving on to questions and flashcards.
Finding Bugs Before Users Do
Testing is trying to break your own program before releasing it. Like a car manufacturer crash-testing vehicles - better to find problems in the factory than on the road! You need to test with normal data (should work), extreme/boundary data (edge cases), and erroneous/invalid data (should be rejected). If you only test with data you expect, you'll miss bugs users will find immediately.
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)