Reports

Insight

QA Touch Insights

QA Touch Insights gives you a dashboard view of your project’s testing health coverage, automation, defects, productivity, and release readiness all in one place.

How to Access Insights

  1. Log in to your QA Touch account.
  2. Open the desired Project.
  3. Click on the Insights menu.

Image1   Image2

1. Project Health

What it shows: Overall project quality score based on key testing and quality metrics.

Steps to use:

  1. Go to the Insights dashboard.
  2. Locate the Project Health widget (usually at the top).
  3. Check the score — higher scores indicate better overall test coverage, execution, and issue resolution.
  4. Click the widget to drill down into the metrics contributing to the score.

  Image3

2. Requirement Coverage (Summary)

What it shows: Percentage of requirements mapped and covered with test cases.

Steps to use:

  1. Open the Requirement Coverage widget.
  2. View the percentage of requirements that have linked test cases.
  3. Identify requirements with low/no coverage.
  4. Click through to see the list of uncovered requirements and add test cases as needed.

3. Automation Coverage (Summary)

What it shows: Percentage of test cases automated across the project.

Steps to use:

  1. Open the Automation Coverage widget.
  2. Review the automated vs. manual test case split.
  3. Use this to plan which modules need more automation.

  Image4

4. Open Issues

What it shows: Total number of unresolved issues currently open in the project.

Steps to use:

  1. Check the Open Issues counter on the dashboard.
  2. Click on it to view the full list of open/unresolved issues.
  3. Filter by module, severity, or assignee to prioritize fixes.

5. Burndown Chart

What it shows: Tracks remaining test executions over time to measure testing progress.

Steps to use:

  1. Open the Burndown Chart widget.
  2. Select the date range or sprint/cycle you want to track.
  3. Review the downward trend line — a steady decline indicates on-track progress.
  4. Identify flat/stalled periods to investigate execution delays.

6. Velocity

What it shows: Shows the number of test executions completed over time.

Steps to use:

  1. Open the Velocity widget.
  2. Choose the time period (daily/weekly/sprint).
  3. Compare execution counts across periods to gauge team throughput.
  4. Use this data for future sprint/cycle planning.

  Image5

7. Requirement Coverage (Detailed View)

What it shows: Visualizes covered vs. uncovered requirements and overall coverage.

Steps to use:

  1. Open the detailed Requirement Coverage chart.
  2. Review the visual breakdown of covered vs. uncovered requirements.
  3. Click on any segment to view the specific requirements in that category.
  4. Assign test cases to uncovered requirements directly if supported.

8. Automation Coverage (Detailed View)

What it shows: Breaks down automated, manual, exploratory, out-of-scope, and unmapped test cases.

Steps to use:

  1. Open the detailed Automation Coverage chart.
  2. Review each category: Automated, Manual, Exploratory, Out-of-scope, Unmapped.
  3. Focus on the “Unmapped” or “Out-of-scope” segments to plan next steps.
  4. Use insights to build an automation roadmap.

9. Tester Productivity

What it shows: Compares test case creation, execution, and defect reporting across testers.

Steps to use:

  1. Open the Tester Productivity widget.
  2. Select the tester(s) or time period to compare.
  3. Review metrics: test cases created, executed, and defects reported.
  4. Use this for workload balancing and performance reviews.

  Image6

10. Module Risk Heatmap

What it shows: Highlights high-risk modules based on failures, issues, and test results.

Steps to use:

  1. Open the Module Risk Heatmap.
  2. Look for modules highlighted in red/orange (high risk).
  3. Click on a module to see failure counts, open issues, and test results.
  4. Prioritize testing/fixes for high-risk modules first.

  Image7

11. Defect Trend

What it shows: Tracks defects created and resolved over time to monitor quality trends.

Steps to use:

  1. Open the Defect Trend chart.
  2. Select the date range to analyze.
  3. Compare the “created” vs. “resolved” lines — a shrinking gap indicates improving quality.
  4. Spot spikes in defect creation to investigate root causes.

  Image8

12. Release Comparison

What it shows: Compares testing outcomes across releases, including pass, fail, blocked, and untested cases.

Steps to use:

  1. Open the Release Comparison widget.
  2. Select two or more releases to compare.
  3. Review the pass/fail/blocked/untested breakdown for each release.
  4. Use this to assess release readiness and quality trends over time.

  Image9

13. Developer Issue TAT (Turnaround Time)

What it shows: Measures the average time developers take to resolve assigned issues.

Steps to use:

  1. Open the Developer Issue TAT widget.
  2. Review the average resolution time per developer or team.
  3. Identify bottlenecks where TAT is high.
  4. Use this for sprint planning and workload distribution.

14. Tester Execution TAT (Turnaround Time)

What it shows: Measures the average time testers take to execute assigned test cases.

Steps to use:

  1. Open the Tester Execution TAT widget.
  2. Review average execution time per tester.
  3. Identify testers/modules with delays.
  4. Use this to improve test planning and resource allocation.

  Image10

PreviousBurndown & Velocity Report
NextProductivity Reports