Software Engineering › Key terms › Y11 Programming Fundamentals › Testing and debugging
Testing and debugging
Process Y11 Programming Fundamentals
Definition
Testing runs the software with chosen data to find errors; debugging finds the cause of each error and fixes it.
Example: Testing finds that something is wrong; debugging finds out why and fixes it.
Found in: syllabus, 2025 HSC marking guidelines, school notes.
Where it is used in the test
Syllabus area: Y11 Programming Fundamentals.
Question types it can appear in
- Multiple choice: Pick the option that matches the definition or example.
- Drag into order: Know where it sits in the sequence.
- Short answer: Outline a test method or a debugging tool
Where it has appeared in the paper
The Software Engineering Project (Part A, C). Part letters follow each paper’s own layout.
Related past questions
- 2025 HSC Q15b (3 marks): Testing and debugging The Software Engineering Project (Part A) · 3 marks
- Familiarisation Q5 (3 marks): Testing (test data) The Software Engineering Project (Part C) · 3 marks
These are the questions the flashcard set links to this term. Open each one and compare your answer with its marking criteria.
Study links
- Flashcard: Testing and debugging in Programming Fundamentals (Year 11) · study that set
- Memorise: Software development steps and algorithm design
- Notes: Interpret and apply fundamental software development steps to develop secure code,… (Secure Software Architecture (Year 12))
- Notes: Explore tools used to develop ideas and generate solutions, including brainstorming,… (The Software Engineering Project (Year 12))
- Notes: Fundamental software development steps for secure code (Secure Software Architecture (Year 12))
- Notes: Define and analyse the requirements of a problem (The Software Engineering Project (Year 12))
How to use it in an answer
A model sentence
“Testing runs the software with chosen data to find errors; debugging finds the cause of each error and fixes it.” Then apply it: Testing finds that something is wrong; debugging finds out why and fixes it.
In a short answer, give the definition in your own words first, then tie it to the situation in the question. Do not copy the example above unless it fits the scenario.
Command words used with it
- Outline: Sketch in general terms; indicate the main features of. (2025 HSC Q15b (3 marks): Testing and debugging)
Technique for the question types
- Multiple choice: Read all four options, rule out wrong ones, pick one; no penalty for guessing so never leave blank.
- Drag into order: Put the steps in the correct order; know the SDLC order and the web request order.
- Short answer: One clear point per mark, use the stimulus and course terms, and answer the command word.
What the marking guidelines and feedback say
Marker feedback: identify two debugging tools used for LOGIC errors; distinguish logic from syntax errors; distinguish manual testing from software debugging tools.
Worked answers from the marking guidelines
Familiarisation Q5 (3 marks): Testing (test data) (3 marks): criteria and sample answer
Criteria
3: Test data that thoroughly tests the algorithm, with expected outputs and reasons for inclusion. 2: Tests most boundaries and/or paths, with most expected outputs and reasons. 1: Some relevant information.
Sample answer
85 -> H (testing greater than 80). 80 -> H (boundary value 80). 60 -> P (between 50 and 80). 50 -> P (boundary value 50). 45 -> N (testing 'otherwise', below 50).
Common mistakes
- Use the term exactly as the syllabus words it, then link it to the scenario in the question; the 2025 feedback repeatedly rewards using the stimulus.
- Answer the command word: outline gives main points only, explain gives a reason or cause, discuss gives both sides.
Related terms
Same group in the syllabus: Software development steps (the order) · Requirements definition · Determining specifications · Design · Development · Integration · Installation · Maintenance · Online code collaboration tools