Software Engineering › Key terms › Y12 SE Project › Functional testing
Functional testing
Term Y12 SE Project
Definition
Checking that each function of the software does what the requirements say.
Example: Click Add to cart and check the item appears.
Found in: course specifications.
Where it is used in the test
Syllabus area: Y12 SE Project.
Question types it can appear in
- Multiple choice: Pick the option that matches the definition or example.
- Matching or table: Match it to its description, example or category.
- Short answer: Define, outline or explain it and tie it to the scenario.
Where it has appeared in the paper
The Software Engineering Project (Part B). 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
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: Functional testing in The Software Engineering Project (Year 12) · study that set
- Memorise: Quality assurance, testing methods and test data
How to use it in an answer
A model sentence
“Checking that each function of the software does what the requirements say.” Then apply it: Click Add to cart and check the item appears.
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 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
- Multiple choice: Read all four options, rule out wrong ones, pick one; no penalty for guessing so never leave blank.
- Matching or table: Tick or match each statement to the right column (for example ORM v SQL, SAST v DAST).
- 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
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).
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: Acceptance testing · Live data · Simulated data · Beta testing · Volume testing · Corrective maintenance · Adaptive maintenance · Perfective maintenance · Functional requirement · Driver (test driver)