Total cases in the current project.
Project visibility for clients and stakeholders
Share the QA picture.
Share the QA picture.
Keep it connected to real execution.
AXQA Client Dashboard turns project status, execution trend, release health, API performance, status mapping, and recent activity into one project-scoped view. Clients can understand what is happening without navigating the full QA workspace or rebuilding status updates manually.
Representative sample data modeled on AXQA client-facing project dashboards. Values below are illustrative, not live customer data.
PROJECT DASHBOARD
Pulse Backend
Connected
Test Cases6
Passed6
Failed0
Not Run0
Execution Trend14 days
100%
Project stability from the latest project state.
100%
Release readiness with all six cases passing.
24 steps
Display status labels visible across test steps.
14 days
Execution and activity range shown to the client.
A project-scoped operating view
TEST CASES6
PASSED6
FAILED0
IN PROGRESS0
NOT RUN0
Show the health of the project without exposing workspace noise.
The dashboard stays focused on the project the client cares about: current state, execution movement, delivery confidence, and the signals that may need attention. Project metadata and status context remain visible without requiring access to administration or authoring workflows.
PROJECT DASHBOARDPulse Backend
Download PDF
Refresh now
ConnectedPlatform: APIVersion: 11.7.248Build: DEMO-260905Status: ActiveTimezone: UTC
Passing state coverage across the scope.
No cases currently contain a failed step.
No mixed execution states are open.
All planned cases have execution evidence.
EXECUTION TREND
14 days
See movement across the selected range.
TotalPassedFailedSkipped
Status, quality, and performance
Keep client reporting useful beyond a single pass percentage.
The client view can combine execution distribution with quality signals, API latency, display labels, and status mapping. That gives stakeholders a better explanation of why the project is healthy and where change is happening.
STATUS BREAKDOWN
Total: 6Overall distribution
6Passed
Passed 6Failed 0Not Run 0
QUALITY SIGNALS
3 signalsWhat deserves attention
No failed or error casesCurrent execution state is fully passing.
Session Service latency watch421 ms average · non-blocking performance signal.
Regression activity decreased10 executions recorded today, down from 14 yesterday.
API PERFORMANCE
avg msSlowest endpoints
DISPLAY STATUS LABELS
24 stepsCurrent labels used on test steps
24steps
Passed
Every current display status is mapped to the passing system bucket in this sample project.
STATUS MAPPING SUMMARY
0 customCustom labels mapped to execution buckets
SystemCustomLabels
Not Run0/1Not Run
Passed0/1Passed
Failed0/1Failed
Error0/1Error
Skipped0/1Skipped
Client activity view
Let stakeholders move from latest update to timeline to risk.
Activity is more useful when the client can answer three different questions from the same project view: what just happened, how the days are trending, and what needs attention now.
ACTIVITY
Project: Pulse Backend
Latest updates and daily timeline
| Time | Item | Status | Notes |
|---|---|---|---|
| Sep 05, 2026 · 06:23 PM | Notification preferences regression / Step 3 | Passed | Read preferences again |
| Sep 05, 2026 · 06:23 PM | Notification preferences regression / Step 4 | Passed | Verify only requested channel changed |
| Sep 05, 2026 · 02:51 PM | Offline action replay regression / Step 4 | Passed | Verify actions are applied once |
| Sep 05, 2026 · 12:12 PM | Device token rotation regression / Step 4 | Passed | Verify old token is inactive |
| Sep 05, 2026 · 11:03 AM | Background resume regression / Step 2 | Passed | Resume state persisted correctly |
| Date | Executions | Pass | Fail | Error | Highlights | New bugs |
|---|---|---|---|---|---|---|
| 2026-09-05 | 10 | 9 | 1 | 0 | 1 unstable execution | 1 |
| 2026-09-04 | 14 | 10 | 0 | 2 | 2 unstable executions | 2 |
| 2026-09-03 | 8 | 5 | 2 | 0 | 2 unstable executions | 2 |
| 2026-09-02 | 6 | 6 | 0 | 0 | All executions passed | 0 |
| 2026-09-01 | 5 | 1 | 2 | 0 | 2 unstable executions | 2 |
| 2026-08-31 | 4 | 4 | 0 | 0 | Clean regression day | 0 |
PERFORMANCE WATCHSession Service latency
WatchAverage duration is 421 ms. It is not blocking release readiness, but the client can see the signal before it becomes a delivery risk.
EXECUTION VARIANCE
Sep 04 showed two error executions
Review
The current project state is healthy, but historical execution evidence remains visible so a temporary instability is not lost.
Useful visibility without workspace overload
Give the client context.
Give the client context.
Keep QA operations in AXQA.
The client dashboard can expose the project story while the QA team keeps authoring, execution control, configuration, and operational administration inside the main AXQA workspace.
Project-scoped contextShow the selected project, platform, build, version, status, and timezone.
Export-ready reportingKeep a clear route to downloadable PDF reporting when stakeholders need a portable update.
Fresh activityRefresh the view and keep recent execution, timeline, and risk context connected.
Client-friendly signal densityPrioritize health, trend, status, performance, and recent changes instead of authoring controls.
CONNECTED CLIENT VISIBILITY
Share the project picture.
Share the project picture.
Keep the evidence connected.
Use Client Dashboard for stakeholder visibility, then move into AXQA Reporting & Dashboards when the QA team needs deeper execution intelligence and operational analysis.