ISTQB_TEST MANAGEMENT_ The Context of Testing_1.2.5 Test Management Activities at Various Test Levels

 

Test Level	Managed By	Focus Area	Key Test Manager Responsibilities
Component	Developers	Individual modules or units	Provide guidelines if TMs support component tests; ensure testability and unit test completeness if required.
Integration	Dev/Test	Interfaces between components	Plan integration strategies (top-down, bottom-up); align with system architecture; ensure integration environments.
System	Test Team	Entire system vs. requirements	Coordinate all system test activities, prioritize risk-based testing, plan test data and test environment.
Acceptance	Customer/BA	Business processes, end-user needs	Coordinate with customers/users, support UAT planning, monitor execution and defect management.

Test Management Activity Examples by Level

1. Component Level

• Ensure developers follow code coverage and static analysis standards.

• Review unit test results if applicable.

2. Integration Level

• Choose integration strategy.

• Make sure stubs and drivers are ready.

• Plan for continuous integration pipelines.

3. System Level

• Plan system test cases based on requirement traceability.

• Organize environment setup and data preparation.

• Schedule test execution and track metrics.

4. Acceptance Level

• Confirm acceptance criteria are defined.

• Coordinate business stakeholders.

• Support defect triage and go/no-go decision.

Question 1 

Scenario:
You are managing a project where developers have just finished component testing. Integration testing is scheduled to begin, but the integration environment is incomplete, causing potential delays.

Question:
As the Test Manager, what should you do first?

A) Postpone integration testing until the environment is fully ready.
B) Escalate the issue to project management and coordinate to speed up environment setup.
C) Start system testing activities to keep the project on schedule.
D) Request developers to perform integration testing on their local machines.

Answer: B

---

Question 2

Scenario:
In your project, acceptance testing is planned to be performed by the customer. However, acceptance criteria are not clearly defined, and business representatives are unclear on their responsibilities.

Question:
What is your best approach as a Test Manager?

A) Define acceptance criteria yourself and assign testers to perform acceptance testing.
B) Facilitate a workshop with business stakeholders to clarify and agree on acceptance criteria and responsibilities.
C) Postpone acceptance testing until the criteria are documented by the business team.
D) Ignore acceptance testing since system testing covers all requirements.

Answer: B

---

Question 3 

Scenario:
During integration testing, the development team is using stubs and drivers, but the stubs are incomplete, leading to failed tests and inaccurate results.

Question:
What is the most effective action the Test Manager should take?

A) Replace stubs with actual components immediately, even if not ready.
B) Work with the development team to prioritize and complete the stubs quickly.
C) Cancel integration testing and move directly to system testing.
D) Ignore the stub issues and continue testing to meet deadlines.

Answer: B

---

Question 4 

Scenario:
System testing is underway, but you find that the test environment does not contain realistic data, which affects the validity of test results.

Question:
How should you address this issue?

A) Use existing data anyway and note the limitations in the test report.
B) Stop system testing until realistic test data is created.
C) Collaborate with data owners to generate or anonymize realistic test data as soon as possible.
D) Skip system testing and start acceptance testing early.

Answer: C

---

Question 5 

Scenario:
Your project uses component, integration, system, and acceptance testing. You notice that defect reports from component testing lack detail, making it difficult for integration testers to identify root causes.

Question:
As a Test Manager, what should you do?

A) Assign testers to rewrite defect reports.
B) Provide guidelines and training for developers on effective defect reporting and monitor compliance.
C) Ignore component defect quality since integration testing will catch remaining issues.
D) Escalate the problem to senior management without trying to resolve it at the team level.

Answer: B

Question 6

Which of the following is typically a Test Manager responsibility during the System Test Level?

A. Writing unit tests for each function
B. Defining acceptance criteria
C. Organizing defect triage meetings with business users
D. Ensuring availability of the system test environment

✅ Correct Answer: D

Question 7

You are a Test Manager in a large banking project. Developers are performing unit tests. You notice delays due to missing unit test reports.
What action should you take?

A. Take over unit testing from developers
B. Escalate immediately to senior management
C. Provide guidance and monitor compliance with unit test reporting guidelines
D. Wait until integration testing to assess the impact

✅ Correct Answer: C

Question 8

Your team is moving to Agile. Who is typically responsible for Acceptance Testing, and how should you adapt?

A. Test Manager; you create all UAT scripts
B. Customer/Product Owner; you support by aligning testing with business goals
C. Developer; you review UAT scripts
D. Scrum Master; you track user feedback

✅ Correct Answer: B