Skip to content

Insight Categories

2 min read

Smart Insights are grouped into categories that map to the questions QA teams ask, rather than to the underlying data sources. Categories are collapsed by default in the Smart Insights view; expand the ones relevant to you.

This page describes each category and the questions it answers. Categories are listed in the order they appear in the product.


Find gaps in protection. Coverage is broader than executed-versus-total — it also spans traceability, orphan tests, and suite growth.

  • Are all requirements backed by tests?
  • How many tests aren’t linked to a requirement?
  • Is our test suite growing?

See Coverage for a full explanation of how Hawzu measures coverage.


Track automation maturity — how much of the suite runs without a human, and where manual effort is concentrated.

  • How fast are we automating our test suite?
  • Which priority tests still rely on manual coverage?
  • Is our high-severity coverage automated?

See how runs are performing across pass, fail, and blocked outcomes, and how much they cover.

  • How is each run trending across pass, fail, and blocked?
  • Which runs are carrying the most defects?
  • How much requirement coverage does each run hit?

Gauge stability and flakiness — how much you can trust a green run.

  • How stable is our test suite?
  • How much do flaky tests drag down pass rate?

Track bug hotspots and aging — where defects pile up and how long they linger.

  • Is our defect backlog growing or shrinking?
  • Which severe defects are still open?
  • How long have open defects been sitting?
  • How are our defects being resolved?
  • Are defects staying closed?

Verify traceability — whether what you promised is actually tested and where defect pressure sits.

  • Which requirements carry the most tests?
  • Which requirements are the most defect-prone?
  • Are our requirement tests automated?

Track release quality over time.

  • Is release quality improving over time?

See who’s driving the work — authoring, running, and executing across the team.

  • Who is authoring the most tests?
  • Who is running the most tests?
  • How is execution work split across roles?