Software Engineering › Key terms › Y12 SE Project › Test plan
Test plan
Term Y12 SE Project
Definition
A document listing test cases, test data, expected output and results.
Example: Test 1: age = 17, expected output: Accepted.
Found in: syllabus.
Where it is used in the test
Syllabus area: Y12 SE Project.
Question types it can appear in
- Short answer: Define, outline or explain it and tie it to the scenario.
- Drawing: Table of test data
- Multiple choice: Pick the option that matches the definition or example.
Where it has appeared in the paper
The Software Engineering Project (Part B, C). Part letters follow each paper’s own layout.
Related past questions
- Sample exam Q11 (3 marks): Testing (test data) The Software Engineering Project (Part B) · 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: Test plan in The Software Engineering Project (Year 12) · study that set
- Memorise: Quality assurance, testing methods and test data
- Notes: Quality assurance, testing methods and test data (The Software Engineering Project (Year 12))
How to use it in an answer
A model sentence
“A document listing test cases, test data, expected output and results.” Then apply it: Test 1: age = 17, expected output: Accepted.
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
No linked question shows the command word for this term. Across the past short answer and drawing questions in this bank the words used most are: Explain, Outline, Describe, Compare, Classify, Analyse. Check the actual word in your question.
Technique for the question types
- Short answer: One clear point per mark, use the stimulus and course terms, and answer the command word.
- Drawing: Use the online drawing tool: label every symbol and arrow, use the correct symbols from the specification, and add every required item.
- Multiple choice: Read all four options, rule out wrong ones, pick one; no penalty for guessing so never leave blank.
What the marking guidelines and feedback say
Good extras: 1023 (just below desktop boundary) and 767 (just below tablet boundary). Test boundary values, both sides of each boundary, and one value for each path.
Worked answers from the marking guidelines
Sample exam Q11 (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. 2: Tests most of the boundaries and paths, with relevant outputs and reasons. 1: Some relevant information.
Sample answer
1024 -> Desktop (boundary check). 768 -> Tablet (boundary check). 100 -> Phone (below lowest screen size check). 850 -> Tablet (between Tablet and Desktop). 2000 -> Desktop (above highest screen size check).
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
- Drawing questions (2025 HSC exam Q22): refine attributes into separate inherited classes; use appropriate class diagram symbols.
- 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: Testing methodologies · Language-dependent code optimisation · Feedback · Path and boundary testing · Actual v expected output · Feedback report · Evaluating effectiveness