Browse QA Engineers Section 9: Test Reports & Metrics

Quality Metrics Dashboard Specification

11 fill-in slots · from The AI Prompt Handbook for QA Engineers

Your details

0/11 filled

Quality Metrics Dashboard Specification

Design a quality metrics dashboard for our mobile app testing.

CURRENT TOOLS:
- Test management: [TestRail / Zephyr / qTest / Xray / spreadsheets]
- CI/CD: [GitHub Actions / Bitrise / CircleCI / Jenkins]
- Bug tracking: [Jira / Linear / Azure DevOps]
- Crash reporting: [Firebase Crashlytics / Sentry / Bugsnag]
- Analytics: [Firebase / Mixpanel / Amplitude]

Define dashboard sections with specific metrics:

RELEASE QUALITY:
- [Metric 1: e.g., "Test pass rate per sprint"]
- [Metric 2: e.g., "Bug escape rate to production"]

TEST EFFICIENCY:
- [Metric 1: e.g., "Automation coverage %"]
- [Metric 2: e.g., "Time from bug found to fixed"]

PRODUCTION HEALTH:
- [Metric 1: e.g., "Crash-free rate"]
- [Metric 2: e.g., "App store rating"]

For each metric:
1. Definition (exactly what it measures)
2. Data source (where to pull the numbers)
3. Target/threshold (what "good" looks like)
4. Visualization type (line chart, bar chart, gauge, number)
5. Update frequency (real-time, daily, per sprint)

Highlighted [slots] are still empty. Downloads are plain .txt — paste into any AI assistant.