Belajar QA Tester - QA Metrics & Reporting

#Pendahuluan

Setelah di episode 24 kita mempelajari shift-left & continuous quality, pada episode ini kita mempelajari QA metrics & reporting — bagaimana mengukur dan melaporkan kualitas secara efektif. Metrics yang baik membantu tim memahami status kualitas dan mengambil keputusan yang tepat.

Mengapa QA metrics penting? Karena "apa yang tidak diukur, tidak bisa diperbaiki." Dengan metrics yang tepat, tim bisa mengidentifikasi area yang perlu perbaikan dan membuktikan dampak dari improvement yang dilakukan.

#QA Metrics

#Process Metrics

text

Process Metrics:
├── Test Coverage:
│   ├── Requirement coverage: % requirement yang tercover
│   ├── Code coverage: % code yang di-test
│   └── Test case coverage: % test case yang dijalankan
├── Test Execution:
│   ├── Tests executed per day
│   ├── Pass rate
│   ├── Average execution time
│   └── Flaky test rate
└── Efficiency:
    ├── Tests per hour
    ├── Bugs per test hour
    └── Automation ROI

#Product Metrics

text

Product Metrics:
├── Defect Metrics:
│   ├── Defect density: bugs per KLOC
│   ├── Defect removal efficiency
│   ├── Defect aging: waktu dari report sampai fix
│   └── Defect slippage: bugs yang lolos ke production
├── Quality Metrics:
│   ├── Customer satisfaction
│   ├── Escape rate: bugs ditemukan di production
│   ├── Mean time to detect
│   └── Mean time to resolve
└── Release Metrics:
    ├── Release frequency
    ├── Lead time
    ├── Change failure rate
    └── Time to restore service

#Defect Density Calculation

text

Defect Density:
├── Formula: Total Defects / KLOC
├── KLOC = Lines of Code / 1000
├── Example:
│   ├── Total bugs: 15
│   ├── Lines of code: 10,000
│   ├── KLOC: 10
│   └── Defect density: 1.5 bugs/KLOC
└── Benchmark:
    ├── Good: &lt; 1 bug/KLOC
    ├── Average: 1-3 bugs/KLOC
    └── Bad: &gt; 3 bugs/KLOC

Note

Jangan over-metrics. Fokus pada metrics yang actionable — yang bisa kalian gunakan untuk membuat keputusan. Metrics yang terlalu banyak bisa menjadi noise dan mengaburkan insight penting.

#QA Dashboard

#Dashboard Components

text

QA Dashboard:
├── Overview:
│   ├── Total test cases
│   ├── Pass rate
│   ├── Open bugs
│   └── Quality score
├── Trend:
│   ├── Pass rate trend (7 days)
│   ├── Bug trend (30 days)
│   ├── Coverage trend
│   └── Execution trend
├── Details:
│   ├── Tests by priority
│   ├── Bugs by severity
│   ├── Tests by component
│   └── Automation coverage
└── Alerts:
    ├── Flaky tests
    ├── Regression failures
    └── Quality gate failures

#Contoh Dashboard

text

QA Dashboard - Sprint 5:
├── Overview:
│   ├── Test Cases: 150
│   ├── Executed: 150 (100%)
│   ├── Passed: 145 (96.7%)
│   ├── Failed: 5 (3.3%)
│   ├── Open Bugs: 3
│   └── Quality Score: 85/100
├── Trend:
│   ├── Pass Rate: 95% → 96.7% (+1.7%)
│   ├── Bug Count: 10 → 3 (-70%)
│   └── Coverage: 85% → 90% (+5%)
└── Details:
    ├── Critical: 0 open
    ├── High: 1 open
    ├── Medium: 2 open
    └── Low: 0 open

#Practical: Metrics Collection

yaml

metrics_collection:
  automated:
    - test_execution_results
    - bug_count_by_severity
    - test_coverage
    - pass_fail_rate
  manual:
    - exploratory_testing_hours
    - bug_triage_time
    - stakeholder_feedback
    - team_satisfaction
  reporting:
    - daily: quick_status
    - weekly: trend_analysis
    - sprint: comprehensive_report
    - monthly: executive_summary

Tip

Automate metrics collection sebanyak mungkin. Gunakan tools seperti TestRail, Jira, atau Grafana untuk generate metrics secara otomatis. Manual metrics collection memakan waktu dan prone to error.

#Penutup

Pada episode 25 ini, kalian telah mempelajari QA metrics & reporting.

Inti yang harus dibawa pulang:

Process metrics: test coverage, test execution, efficiency.
Product metrics: defect density, escape rate, quality metrics.
QA dashboard: overview, trend, details, alerts.
Metrics harus actionable dan automated.

Di episode 26 selanjutnya, kita akan membahas ekosistem & tren modern 2026 — bagaimana QA berkembang di era continuous quality dan AI-powered testing. Sampai jumpa di episode 26!