3.2 ProgrammingIntroduction

Finding Bugs Before Users Do

Part of Testing · GCSE GCSE Computer Science revision

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.

Topic position

Section 1 of 7

Practice

15 questions

Recall

8 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.

Keep building this topic

Read this section alongside the surrounding pages in Testing. That gives you the full topic sequence instead of a single isolated revision point.

Types of Test Data Deep Dive: Testing Methods Deep Dive: Test Plan Example

Practice Questions for Testing

A program accepts scores between 0 and 100. Which value is an example of erroneous test data?

A. 50
B. 0
C. 101
D. "hello"

1 markfoundation

Explain what a logic error is and give one reason why it is harder to find than a syntax error.

2 marksstandard

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)

15 questions on Testing — practise free

Instant marking, adaptive difficulty, and 8 spaced repetition flashcards. Free until your GCSEs.

Try PrepWise Free

Back to

Testing

Types of Test Data