Software Engineering › Learn step by step › Y12 SE Project
Item 358 of 426 · Year 12: The Software Engineering Project, 30 of 47
Testing methodologies
Term
Jump to a topic
- Exam format, question types and command words (46)
- Year 11: Programming Fundamentals (69)
- Year 11: The Object-Oriented Paradigm (33)
- Year 11: Programming Mechatronics (29)
- Year 12: Secure Software Architecture (57)
- Year 12: Programming for the Web (59)
- Year 12: Software Automation (35)
- Year 12: The Software Engineering Project (47)
- Diagrams and modelling tools (18)
- Python, SQL, pseudocode and CSS patterns (33)
Definition
Ways of checking code: unit, integration and system testing, using black box and white box approaches.
Example: Test each subroutine on its own first.
Found in: syllabus, school notes.
Where you'll use it 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.
- Multiple choice: Pick the option that matches the definition or example.
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
How to use it
A model sentence
“Ways of checking code: unit, integration and system testing, using black box and white box approaches.” Then apply it: Test each subroutine on its own first.
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.
Official worked answer
Sample exam Q11 (3 marks): Testing (test data) (3 marks): official 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).
Go deeper
- Flashcard: Testing methodologies in The Software Engineering Project (Year 12) · study that set
- Memorise: Quality assurance, testing methods and test data
- Full term page: every question, note and marking comment for Testing methodologies
Check yourself
Explain “Testing methodologies” in one sentence, give an example, and name a question type that could test it.
Reveal the answer
Ways of checking code: unit, integration and system testing, using black box and white box approaches.
Example: Test each subroutine on its own first.
Could be tested as: Short answer, Multiple choice.