QA visibility connected to execution

See project health clearly.
Turn execution into decisions.

AXQA keeps test status, execution history, release readiness, risk hotspots, API signals, and recent activity connected to the same QA workflow. Leads and stakeholders can understand what is healthy, what changed, and where attention is needed without rebuilding the story manually.

Explore reporting views See execution signals

The data shown below is representative sample project data modeled on AXQA reporting views.

Pulse Mobile

14 days

PROJECT HEALTH Snapshot

Connected

Snapshot Stability86%

Current health based on latest test case states

Release Readiness82%

Stability + pass rate + not-run coverage

Execution Stability96%▲ 1 pp

Executed Coverage100%7 / 7

Execution Volume9148 manual · 43 automated

86%

Snapshot stability from the current project state.

95%

Execution-based release readiness for the selected period.

100%

Executed coverage across the current seven-case scope.

91 runs

Execution volume across manual and automated activity.

Project health snapshot

Separate the current state from what actually ran.

Snapshot metrics tell you what the project looks like right now. Execution metrics tell you what happened across real runs over time. AXQA keeps both views available so teams do not confuse a static status with execution evidence.

Pulse Mobile Project Health

SNAPSHOT

SNAPSHOT STABILITY 86%

Reflects the current health of test cases based on their latest step statuses.

86%

SNAPSHOT RELEASE READINESS 82%

Heuristic score combining snapshot stability, pass rate, and not-run coverage.

82%

Passed 5 Failed 1 In progress 1 Not run 0

EXECUTION STABILITY 96%

Based on failed + error step ratio.

▲ 1 pplast 14d

RELEASE READINESS 95%

Stability + pass rate + executed coverage.

▲ 2 ppheuristic

EXECUTED COVERAGE 100%

7 of 7 cases executed in the selected scope.

0 not executedcoverage

EXECUTION VOLUME 91

48 manual executions and 43 automated executions.

▲ 11last 14d

Execution intelligence

Move from totals to trend, stability, and blockage signals.

Reporting becomes more useful when the team can see movement over time and connect that movement to concrete failed steps, errors, skipped work, risky test cases, and slow APIs.

14-DAY EXECUTION TREND

Execution Trend

Last 14d

Total Passed Failed Error In progress

Aug 23Aug 27Aug 31Sep 04Sep 05

STEP DISTRIBUTION

Where the outcomes landed

90%passed

Passed Failed Error Skipped

TOP RISK HOTSPOTS

Fail / error steps per test case

ACTIONABLE

Biometric login regression6

Offline queue regression4

Deep link routing regression3

First launch onboarding2

Background resume regression2

Upgrade install regression2

API STABILITY SIGNALS

Slow API endpoints

Avg 403 ms

Device Registration9,472 bytes

774.59 ms

Profile API9,245 bytes

695.03 ms

Average API duration increased by 17 ms in the selected range.

Status and execution visibility

Keep custom status meaning connected to the system view.

AXQA can show which display statuses are in use, how they map to system buckets, and where the latest execution activity is coming from. That keeps reporting readable even when teams customize how work is labeled.

STATUS MAPPING COVERAGE

Display mapping

0 custom

Not Run

Passed

Failed

Error

Skipped

CURRENT DISPLAY STATUSES

28 steps

25passed

PassedNot RunFailed

STATUS MAPPING SUMMARY

System buckets

System statusCustomDisplay label

Not Run0 / 1Not Run

Passed0 / 1Passed

Failed0 / 1Failed

Error0 / 1Error

Skipped0 / 1Skipped

RECENT EXECUTIONS

Latest activity keeps the history actionable.