/en-tutor-prep-s6-ict-system-testing-acceptance-practice-4/
/en-tutor-prep-s6-ict-system-testing-acceptance-practice-4/
General Inquiry: info@TutorZone.com.hk
Office Hours: Monday to Saturday - 9:00 AM to 6:00 PM
WhatsApp Monday to Sunday - 24 hours
Hotline: +852 6828 1809
Instant Support: +852 9061 3106

S6 ICT System Testing and Acceptance Practice 4 (Retry)

S6 ICT System Testing and Acceptance Practice 4 (Retry)

  • 2026-11-18

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.

Common mistakes broken down State which test level and which technique each item uses, then check the numbers.

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 Retry

02 Questions (10 items)

  1. FoundationHow do unit testing and system testing differ in scope?
  2. FoundationWhat is the main difference between black-box and white-box testing?
  3. FoundationWho should run acceptance testing?
  4. FoundationWhat is the purpose of regression testing?
  5. IntermediateA field ranges from 1 to 100. Which values belong in boundary value testing?
  6. IntermediateA field ranges from 1 to 100. How many equivalence classes does partitioning give?
  7. Challenge150 of 200 statements have been executed. What is the statement coverage?
  8. ChallengeA 10 KLOC system has 40 defects. What is the defect density?
  9. Error redoA student used equivalence partitioning but missed 0 and 101. What should be added?
  10. Error redoSomeone schedules alpha testing at users homes. What is the correct arrangement?

03 Answers and one-line notes

# 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.

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.

Join as a tutor or coach — academic, music, sports, arts, STEM. Free to register. See how it works →