S6 ICT System Testing and Acceptance Practice 4 (Retry)
Ten items retry the decisions that go wrong most: test levels, black-box versus white-box, who runs each test, boundary values and coverage calculations.
| 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 | Retry |
| # | Answer | One-line note |
|---|---|---|
| 1 | Unit testing targets a single program unit while system testing targets the whole system. | From narrow to wide the order is unit, integration, system and acceptance. |
| 2 | Black-box testing ignores the code while white-box testing designs cases from code structure. | The two approaches complement each other. |
| 3 | The customer or the users. | Developers only supply the environment and technical support. |
| 4 | To confirm that existing features still work after a change. | Run it after every defect fix or new feature. |
| 5 | 0, 1, 100 and 101. | Take one value inside and one outside each boundary. |
| 6 | Three. | Below 1, 1 to 100, and above 100. |
| 7 | 75 percent. | Divide 150 by 200 and multiply by one hundred. |
| 8 | 4 defects per KLOC. | Defect density allows quality comparison across project sizes. |
| 9 | Boundary value testing. | Boundaries are the most error-prone values, so partitioning alone is not enough. |
| 10 | Alpha testing runs at the developer site, and beta testing runs in user environments. | Matching the wrong location makes test results hard to control. |
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.

