Testing and Debugging Flashcards

1️⃣ Familiarise yourself with the flashcards:

  • Look through all the flashcards to see what's on both sides.
  • Make sure you understand the information on each card. If something's unclear, click the link to the revision notes at the bottom of the page for more details.

2️⃣ Test yourself:

  • Look at the question or prompt on each card and try to remember the answer before flipping it over.
  • Check the answer and make a note of any cards you find challenging and need to go over more.

3️⃣ Consistently Review and Practice:

  • Use spaced repetition: spend more time on the cards you struggle with and go over them more often.
  • Regularly review all the flashcards to help you better understand and retain the information over time.

Note: We may include questions that have multiple correct answers. It's useful to remember specific examples to understand these concepts better.

PERSONALISED 1-TO-1 TUTORING

Need more help on this topic? Get 1-to-1 support

Get support with clear explanations, practice and feedback (Ages 5 to 16).

  • DBS-checked tutors
  • Flexible times
  • Parents can be updated

Want an ad-free experience? Subscribe to remove ads

What is the main purpose of testing a program?

To find errors and check it meets the requirements.

What is debugging?

Finding and fixing bugs (mistakes) in the code after tests show problems.

What is a syntax error?

An error where code breaks language rules, so the program will not run.

What is a logic error?

An error where the program runs but gives the wrong result.

What is a run-time error?

An error that happens while the program runs, often causing a crash.

What is iterative testing?

Testing often during development to spot and fix issues early.

What is final (terminal) testing?

Testing the finished program to check it meets all requirements.

What is a test plan?

A list of tests with inputs, expected outputs, and actual results.

What is normal test data?

Typical valid inputs that a user would enter.

What is boundary (extreme) test data?

Valid inputs at the edges of the allowed range.

What is erroneous (invalid) test data?

Inputs that are not allowed and should be rejected.

What is a dry run in debugging?

Going through code by hand, line by line, tracking variable values to find errors.