ISTQB_TEST MANAGEMENT_ The Context of Testing_1.2.7 Test Management Activities to Plan, Monitor, and Control

 

1. Test Planning

This is the foundation stage where everything is laid out.

• Scope Definition: Clearly define what will be tested – all functions and qualities of the software. Include both black-box (from user’s perspective) and white-box (internal logic) test methods.

• Risk Assessment: Identify possible risks early (e.g., unstable software, skill gaps) and plan how to deal with them (like adding more tests or training).

• Resource Allocation: Assign the right people and tools. If the team is split across locations, make sure communication is smooth and roles are clear.

🔹 2. Test Monitoring

This is where you track what’s happening during testing.

• Execution Oversight: Regularly check progress – are tests running as planned? Are defects being reported and resolved?

• Tools and Environment: Ensure test tools and environments are working well, especially in Agile/CI-CD setups where feedback should be quick.

• Dev Collaboration: Work closely with developers to spot and solve problems faster, using both technical (white-box) and user-focused (black-box) perspectives.

🔹 3. Test Control

This is about making changes when needed to keep things on track.

• Adaptive Process: Be ready to change your test strategy if things don’t go as expected – for example, if critical bugs are found late.

• Quality Gates: Set up checkpoints (gates) that define when testing can move to the next stage. Only pass if quality meets expectations.

Question 1: Test Planning (Scope & Risk)

Scenario: You’re the test manager for a banking application project. The client wants to focus on security and performance. You notice that the initial test plan lacks non-functional testing.

Which is the best action to take?

A. Increase test resources for GUI testing.
B. Add security and performance testing to the scope and re-assess risks.
C. Shift all functional tests to the development team.
D. Proceed as planned and raise concerns after the test execution phase.

✅ Correct Answer: B

---

Question 2: Test Monitoring

Scenario: Your team reports that the test execution is falling behind schedule due to frequent environment crashes.

What is your best next step?

A. Ignore it and wait for the environment team to fix it.
B. Reassign testers to documentation tasks.
C. Escalate the issue, prioritize environment stability, and update the test schedule.
D. Remove environment-related test cases from scope.

✅ Correct Answer: C

---

Question 3: Test Control (Adaptive Process)

Scenario: Midway through testing, you discover a major change in the application that was not communicated by the development team.

How should you respond?

A. Ask testers to ignore the changes and proceed.
B. Halt testing and wait for an updated test plan.
C. Reevaluate the impact, update test cases, and adjust the schedule.
D. Restart testing from scratch.

✅ Correct Answer: C

---

Question 4: Quality Gate Management

Scenario: A quality gate is set for the completion of 95% of planned tests with less than 2% critical defects open. Your current test execution is 90% complete, and 4% critical defects remain open.

What should you do?

A. Proceed to the next phase as you're close to the target.
B. Delay the gate review and work to meet the required thresholds.
C. Reduce the number of test cases to reach 95% completion faster.
D. Close critical defects and proceed.

✅ Correct Answer: B

1. You’re working on an Agile project and the development team frequently updates the code base. What is the most effective way to monitor quality?

   • A. Rerun all test cases manually each time

   • B. Use automated testing integrated into the CI/CD pipeline

   • C. Increase the number of manual testers

   • D. Reduce testing to meet the sprint timeline
     ✅ Answer: B

2. Your offsite test team is missing daily stand-ups and delaying communication. What is a key action you should take?

   • A. Replace the offsite team with onsite testers

   • B. Schedule mandatory end-of-day meetings

   • C. Establish clear communication protocols and tools

   • D. Ignore as long as work is being delivered
     ✅ Answer: C

3. A stakeholder wants to reduce testing time due to project delays. What should you do?

   • A. Agree and reduce the test scope blindly

   • B. Perform a risk-based analysis to reduce low-risk tests

   • C. Reject the proposal completely

   • D. Delay the release instead
     ✅ Answer: B

4. Testers report that test scripts are outdated due to frequent application changes. What is your control measure?

   • A. Continue testing using old scripts

   • B. Delay testing until scripts are updated

   • C. Prioritize updating scripts and use exploratory testing meanwhile

   • D. Cancel the current test phase
     ✅ Answer: C

5. You notice a rise in defect leakage in production. What should be done during planning for the next cycle?

   • A. Reduce the number of testers

   • B. Skip test case reviews

   • C. Strengthen test design and include root cause analysis in planning

   • D. Focus more on development
     ✅ Answer: C