I85PREP
⌘ K
KDU CGT study materials
KDU CGT study resources

KDU CGT: Test Management, Tools, and Metrics

KDU CGT · Work through your exam, one topic at a time.

All guide sections

Test Management, Tools, and Metrics

What this domain tests

Test management is about planning, tracking and reporting testing so decisions can be made. The exam covers test plans, estimation, tools, automation and metrics, and how to avoid numbers that look good but mislead.

Core rules

  • A test plan states scope, approach, resources, schedule, risks, entry and exit criteria, and what will not be tested.
  • Risk-based prioritisation: spend effort where impact and likelihood are highest, such as progression, payments, saves and certification requirements.
  • Tools: test management (TestRail, Zephyr, Xray), defect tracking (Jira, Azure DevOps), automation frameworks, device farms, crash reporting and capture tools.
  • Automation suits stable, repetitive checks: smoke tests, unit tests, data validation, regression of core paths. Exploratory testing finds the unknown issues automation cannot.
  • Useful metrics: test execution progress, pass rate, coverage against requirements, defect density, defect removal efficiency, escaped defects, mean time to repair, and flaky-test rate.
  • Metrics must be paired with coverage and context; a high pass rate over a small, easy subset is not good news.

Worked example

A suite has 1,000 cases. 850 have run: 800 pass, 50 fail, and 150 are unexecuted, 30 of them critical-path. The raw pass rate is 94.1% of executed cases. Reasoning: the lead should not report '94% pass' as readiness, because execution is 85% and the unexecuted set contains critical cases. The report shows execution progress, pass rate, blocked cases, and the risk of the unexecuted critical set. Exit criteria are not met, so the recommendation is to finish the critical cases and resolve blockers before the gate.

Traps

Using bug counts as a productivity measure. Reporting pass rate without coverage. Automating unstable tests and ignoring the flaky rate. Letting test cases go stale after design changes. No entry or exit criteria. Skipping exploratory testing because automation exists. Treating a green dashboard as a release decision.