WJEC A-Level Computer Science 601-5345-3
Hardware: Architecture, Memory and Storage
Networks and Data Transmission
Logic Gates and Boolean Algebra
Data Representation and Data Types
Data Structures
Organisation of Data: Files and Records
Database Systems
The Operating System
Algorithms and Programs
Principles of Programming
Systems Analysis
Software Engineering and Program Construction
Types of Software System
Practical Programming
Data Security and Integrity
Computing, Society and the Law
Advanced Data Structures and Logic
Recursion, Sorting and Searching
Programming Paradigms and Translators
System Design and Human-Computer Interaction
Software Engineering Tools and Professional Practice
Advanced Architecture and Assembly Language
Communication Networks and File Organisation
Number Representation and Floating Point
Databases and Distributed Systems
Operating System Management
Software Systems and Applications
Data Security, Cryptography and Attack
Software Engineering Tools and Professional Practice
Testing tools and testing strategies
- 3 things to know
- A2 Unit 3
Overview
Test harness, stub in testing and driver in testing.
What you need to know
Answer each one before you reveal it.
What is a test harness?
What is a stub in testing?
Questions from this subtopic
Each one with the model answer underneath.
- 1
What is a test harness?
Model answer
A test harness is a program that runs a module with prepared inputs, collects the outputs and compares them with the results that were expected.
- 2
What is a stub in testing?
Model answer
A stub is a simple stand-in for a module that has not yet been written, returning a fixed result so that the module calling it can still be tested.
- 3
What is a driver in testing?
Model answer
A driver is a program written purely to call a module and supply it with data, so that the module can be tested before the rest of the system exists.
- 4
What is unit testing?
Model answer
Unit testing checks a single subroutine or module in isolation against what it was specified to do.
- 5
What is integration testing?
Model answer
Integration testing checks that modules already proved separately work correctly once joined, and in particular that the data passed between them is right.
- 6
Distinguish top-down from bottom-up integration testing.
Model answer
Top-down testing begins with the highest level module and uses stubs in place of those below it, while bottom-up testing begins with the lowest level modules and uses drivers to call them.
Other ways to work this
The same content, four other ways.
What is inside Levo
Six ways to work the same material.
Every question in Software Engineering Tools and Professional Practice, on a schedule.
Attempt a question from memory, write the correct version, then attempt it again. Levo records the jump between your first attempt and your last, and brings each question back on the day you are due to forget it.
Or £46 a year, about £3.83 a month. Cancel anytime.