S6 ICT System Testing and Acceptance Practice 1 (Basics)
- 2026-11-18
S6 ICT System Testing and Acceptance Practice 1 (Basics)
Ten items cover the four test levels, black-box and white-box testing, equivalence classes, boundary values, statement coverage and defect density.
Test levels and basic test design Separate the four levels first, then design test data with equivalence partitioning and boundary values.
01 Paper details (check answers afterwards)
| Item | Detail |
|---|---|
| Questions | 10 |
| Suggested time | 25 |
| Difficulty mix | Foundation 4 · Intermediate 2 · Challenge 2 · Error redo 2 |
| Chapter | Chapter: S6 ICT: system testing and acceptance |
| Level | Basics |
02 Questions (10 items)
- FoundationWhat scope does unit testing mainly check?
- FoundationWhere does system testing sit in the development process?
- FoundationWho normally runs acceptance testing?
- FoundationDoes black-box testing require reading the source code?
- IntermediateA field accepts integers from 1 to 100 only. How many equivalence classes result, counting invalid ones?
- IntermediateA field takes integers from 5 to 20. Which values must boundary value testing cover at minimum?
- ChallengeA system has 240 executable statements and testing has run 180 of them. What is the statement coverage?
- ChallengeA 10 KLOC system has 40 defects found during testing. What is the defect density?
- Error redoA student says developers should run acceptance testing. What is the correct practice?
- Error redoWhat goes wrong if acceptance testing is scheduled before integration testing?
03 Answers and one-line notes
| # | Answer | One-line note |
|---|---|---|
| 1 | A single program unit, such as the internal logic of one function or method. | Unit testing has the smallest scope and is normally run by developers while coding. |
| 2 | After integration testing and before acceptance testing. | System testing checks whether the whole system meets the requirements specification. |
| 3 | The customer or the end users. | Acceptance testing confirms that the system is ready to be handed over. |
| 4 | No, test cases are designed from inputs and outputs only. | Black-box testing focuses on behaviour and ignores internal structure. |
| 5 | Three: below 1, 1 to 100, and above 100. | One valid class plus two invalid classes makes three in total. |
| 6 | 4, 5, 20 and 21. | Take one value inside and one outside each boundary, which gives four test values. |
| 7 | 75 percent. | Coverage equals executed statements divided by total statements, times one hundred. |
| 8 | 4 defects per KLOC. | Defect density is defects per thousand lines of code, which allows comparison across project sizes. |
| 9 | The customer or users run it, while developers only provide the environment and support. | Developers checking their own work belongs to unit and system testing. |
| 10 | The modules are not yet combined, so interface defects get mistaken for requirement issues. | The four levels run unit, integration, system, then acceptance, and the order should not be swapped. |
04 What to do after marking
- After marking, redo only the wrong items and write down which step went wrong (formula, unit, or misread number).
- Repeat the same item two days later; move to the next paper only when both attempts are correct.
- Parents only need the answer and note columns; there is no need to explain every item.
Download the full ten-item paper as a PDF, answers and notes included.Tutor Registration →
Questions and answers are written originally by the TutorZone team and are not taken from any school, publisher or examination authority paper. Every value is checked by computer.



