Public sample · read-only

A report developers can act on.

This is a fixed demonstration report using safe fixture data. It is not a live customer run and does not require an account or project ID.

Sample run
demo-auth-flow
Completed · 00:08.4
Assertions passed
3
Review items
1
Duration
8.4s
Confidence
92

Journey timeline

Every action is paired with an outcome and timestamp.

Open landing page
GET / returned 200
Passed00:01.2
Open sign-in form
Form fields were visible and enabled
Passed00:02.8
Submit invalid email
Validation message appeared without a network error
Passed00:04.1
Navigate to account area
A visual shift was retained in Audit Log
Review00:06.7

Why this page is separate from the console

A public sample should never depend on a customer project, a private run, or an existing session. When you are ready to test your own application, create an account and Matrix QA will open the authenticated console with your organization context preserved.

Read the evidence correctly

Questions about this sample

Is this a live customer report?

No. This is a fixed public demonstration report using safe fixture data. It is not a live customer run and does not require an account or project ID.

What does the sample report show?

It shows a browser journey timeline in which each action is paired with an outcome and timestamp, along with summary metrics for passed assertions, review items, duration, and confidence.

What evidence is included in the sample?

The sample shows four captured screenshots, two retained console events, twelve observed network checks, and a Markdown-ready report export.

What is different in the authenticated console?

The real console adds project context, issue filters, audit logs, assertions, and artifact links for authenticated workspaces. The public sample remains separate so it never depends on a customer project or session.