AXQA Client Dashboard | Secure Read-Only QA Visibility

The AXQA Client Dashboard provides clients and external stakeholders with a secure, read-only view of project quality, execution progress, risks, and release indicators without requiring access to the main AXQA workspace.

It is designed to give clients continuous visibility into QA activity while keeping project management and test configuration under the control of the QA team.

Why it matters

Gives clients direct visibility into project quality and testing progress.
Reduces the need to manually prepare recurring status updates and QA summaries.
Helps QA teams communicate execution results, risks, and release confidence using live project data.
Keeps client visibility separate from internal test management activities.
Provides a consistent project view that can also be exported as a PDF report.

When to use it

When a client needs visibility into an active QA project.
When external stakeholders need regular testing progress without full AXQA access.
When a QA service provider wants to provide a professional live quality dashboard to its customers.
When project managers need to share execution status, risks, and release indicators.
When stakeholders need downloadable QA reports for reviews or project meetings.

Core concepts

Client Dashboard – A read-only external view of project quality and execution information.
Secure Share Link – A project-specific link used to provide controlled Client Dashboard access.
Allowed Email – An approved email address that can use the Secure Share Link.
Client Timezone – The timezone used to display dates and times in the dashboard and generated reports.
Project Health – High-level indicators that summarize the current quality condition of the project.
Stability – An indicator based on the current failed and error states across project Test Cases.
Release Readiness – A combined indicator that considers stability, passing coverage, and remaining unexecuted coverage.
Live Updates – Dashboard information that refreshes as new execution activity becomes available.
PDF Report – A downloadable snapshot of the project dashboard and its supporting quality information.

How it works

An authorized AXQA user creates a Secure Share Link for a specific Project.
One or more client email addresses are added to the link.
The client opens the shared link and verifies access using an approved email address.
AXQA displays information only for the Project associated with that Secure Share Link.
Execution results, project health, risks, and activity are reflected in the Client Dashboard as testing progresses.
The client can refresh the dashboard or download a PDF report.
Authorized AXQA users can later update the allowed recipients, change the Client Timezone, disable the link, or delete it.

Warning

The Client Dashboard does not provide access to edit Test Cases, Test Plans, API definitions, execution configuration, or other project management information.

How to use it

Step 1: Create a Secure Share Link

Go to:

User Management → Add new → Secure Share Link

Select the Project that you want to share.

A Secure Share Link is associated with one Project. After the link is created, the Project cannot be changed. Create a new link when you need to share another Project.

Step 2: Configure the Client Timezone

Select the timezone that should be used for the client.

The selected timezone is used when displaying dates and times in:

Client Dashboard activity
Latest Updates
Daily Timeline
Execution information
Generated PDF reports

Choose the timezone that best represents the client or project reporting location.

Step 3: Add allowed client emails

Enter the email addresses that should be allowed to access the dashboard.

Multiple client email addresses can be added to the same Secure Share Link when several stakeholders need access to the same Project.

Only approved recipients should be added.

Step 4: Configure additional access restrictions when required

If your organization uses AXQA IP access restrictions, the Secure Share Link can also use the configured IP whitelist.

Use this option when Client Dashboard access should only be available from approved networks.

Step 5: Create and share the link

Create the Secure Share Link.

From User Management, locate the Client Secure Share Links section and use Copy link to copy the generated Client Dashboard URL.

Send the link only to the intended client or stakeholder.

Step 6: Client verification

When the client opens the link, AXQA asks for an approved email address.

The client completes the verification process and is then redirected to the Project Dashboard.

No regular AXQA workspace account is required for Client Dashboard access.

Step 7: Review project information

The top section of the Client Dashboard shows the current project context, including available information such as:

Project
Platform
Version
Build
Project Status
Client Timezone
Last Update

This helps ensure that the client understands exactly which project environment and build the dashboard represents.

Step 8: Review Test Case status

The dashboard provides a project-level Test Case summary using the following categories:

Test Cases – Total Test Cases currently included in the Project.
Passed – Test Cases currently in a passing state.
Failed – Test Cases containing at least one failed step.
Error – Test Cases that could not be successfully executed or evaluated.
Skipped – Test Cases that were skipped, incomplete, or contain mixed incomplete execution states.
Not Run – Test Cases that have not yet been executed.

These values provide a quick view of current testing coverage and outstanding quality work.

Step 9: Review the Execution Trend

The Execution Trend chart shows testing activity across a selectable time range.

Available ranges allow the client to review recent execution behavior over different periods.

The chart can be used to identify:

Increasing or decreasing test activity
Passing execution trends
Failure patterns
Execution errors
Skipped activity

This is useful for understanding how project quality changes over time rather than relying only on the current status.

Step 10: Review Project Health

The Project Health section provides two high-level indicators.

Stability

Stability reflects the current proportion of the project that is not affected by failed or error Test Case states.

A higher value generally indicates a more stable current test result set.

Release Readiness

Release Readiness combines several project signals, including:

Stability
Passing coverage
Remaining Not Run coverage

Release Readiness is a quality indicator designed to support release discussions. It should be evaluated together with project risks, severity, business context, and the organization's own release criteria.

It is not an automatic release approval.

Step 11: Review Status Breakdown

The Status Breakdown chart displays the overall distribution of Test Cases across:

Passed
Failed
Error
Not Run
Skipped

Use this section to quickly understand which execution states currently make up the Project.

Step 12: Review Quality Signals

The Quality Signals section highlights failed and error Test Cases based on their configured priority.

This helps clients understand whether current problems are concentrated in high-priority or lower-priority test coverage.

Priority-based quality information should be evaluated together with the Test Case scope and the business importance of the affected functionality.

Step 13: Review API Performance

When the Project contains API execution metrics, the API Performance section displays the slowest measured API endpoints.

The dashboard can display API information using:

Average response duration
Average response size

Use Toggle Size to switch between the available views.

If no relevant API execution metrics are available, the dashboard displays an empty state instead of generating artificial data.

Step 14: Review Display Status information

If the Project uses custom Test Step status labels, the dashboard provides:

Display Status Labels – The status labels currently represented in execution data.
Status Mapping Summary – How custom labels relate to AXQA execution status groups.

This allows client-facing terminology to remain visible while preserving consistent execution reporting.

Step 15: Review Latest Updates

Open the Latest Updates tab under Activity.

This section shows recent Test Step execution activity, including:

Time
Test Case and Step
Status
Execution information or notes

Use this view when the client wants to understand what changed recently without reviewing the complete Project history.

Step 16: Review the Daily Timeline

Open the Daily Timeline tab.

The timeline summarizes testing activity day by day and includes:

Date
Total executions
Passed executions
Failed executions
Errors
Highlights
New failed/error findings

The available range can be changed to review a longer or shorter reporting period.

Step 17: Review Risks

Open the Risks tab.

The dashboard summarizes current quality signals such as:

Test Cases affected by execution errors
Failed Test Cases
Test Cases that have not yet been executed
Skipped or incomplete Test Cases

The purpose of this section is to make important testing gaps and unstable areas immediately visible to stakeholders.

Step 18: Refresh the dashboard

The Client Dashboard receives updated project information while the client remains connected.

The client can also select Refresh now to immediately reload the main dashboard information and charts.

The Connected indicator shows whether the dashboard currently has an active live connection.

Step 19: Download the PDF report

Select Download PDF to generate a client-facing project report.

The PDF can include:

Project and build context
Test Case KPIs
Pass rate
Project Health
Stability
Release Readiness
Execution Trend
Status Breakdown
Quality Signals
API Performance
Display Status information
Latest Updates
Daily Timeline
Risk summary

The selected reporting range is used where applicable.

PDF reports are useful for project reviews, release discussions, stakeholder meetings, and historical reporting.

Step 20: Manage existing Client Dashboard access

Go to:

User Management → View all

Under Client Secure Share Links, authorized users can:

Copy the share link
Edit allowed emails
Change the Client Timezone
Enable or disable IP whitelist usage
Enable or disable the Secure Share Link
Delete the Secure Share Link

The Project assigned to an existing Secure Share Link cannot be changed.

Create another Secure Share Link when a different Project needs to be shared.

Best practices

Create separate Secure Share Links for different Projects or client contexts.
Add only the stakeholders who currently require access.
Remove outdated recipients when project responsibilities change.
Select the correct Client Timezone before sharing the dashboard.
Disable access when a client no longer needs ongoing visibility.
Use the dashboard for live status and PDF reports for formal reporting checkpoints.
Review Failed, Error, Skipped, and Not Run separately because they represent different QA conditions.
Use Release Readiness as a supporting indicator rather than the only release decision.
Keep Test Case priorities and project metadata accurate so client-facing quality indicators remain meaningful.
Review the Client Dashboard yourself before providing the link to an external stakeholder.

Common mistakes

❌ Sharing the link with an email address that was not added to the Secure Share Link.
✔ Add the recipient to the allowed email list before asking them to access the dashboard.

❌ Expecting the client to edit Test Cases from the Client Dashboard.
✔ Use the main AXQA workspace for Test Case management. Client Dashboard access is read-only.

❌ Using one Secure Share Link for a different Project.
✔ Create a new Secure Share Link. The Project associated with an existing link cannot be changed.

❌ Selecting the wrong timezone and seeing unexpected activity times.
✔ Configure the Client Timezone according to the client or project reporting location.

❌ Treating an Error as the same thing as a Failed Test Case.
✔ A Failed Test Case represents a failed test result, while Error indicates that execution or evaluation could not be completed successfully.

❌ Treating Not Run or Skipped Test Cases as Passed coverage.
✔ Review unexecuted and incomplete coverage separately before making release decisions.

❌ Using Release Readiness as an automatic release approval.
✔ Combine the indicator with business risk, severity, coverage, known issues, and release requirements.

❌ Leaving old client access active after the engagement has ended.
✔ Disable or delete Secure Share Links that are no longer required.

Security & permissions

Client Dashboard access is separate from normal AXQA workspace access.
Access is limited to the Project associated with the Secure Share Link.
Only approved recipients can complete the Client Dashboard access process.
Additional network access restrictions can be applied when required.
Client Dashboard access is read-only.
Clients cannot use the Client Dashboard to modify Test Cases, Test Plans, API definitions, Project configuration, or execution settings.
Authorized AXQA users control who can access each shared Project.
Existing Secure Share Links can be disabled when temporary access should be suspended.
Secure Share Links can be permanently deleted when they are no longer required.
Access to a Project is no longer available through the Client Dashboard when the Project is no longer in a shareable active state.

AXQA

Did You Know?

Client Dashboard