Interactive Demo

Explore a live test execution run — step-by-step results, per-step screenshots, console logs, network traces, and AI root cause analysis, all captured automatically.

Quick answer

Explore a live test execution run — step-by-step results, per-step screenshots, console logs, network traces, and AI root cause analysis, all captured automatically. Use this page to preview the workflow and its visible results before following the linked written instructions.

What this page covers

Every ContextQA test run captures a complete evidence package automatically: per-step screenshots, session video, browser console logs, HAR network trace, and an AI root cause analysis for any failure. This demo walks through a 12-test execution run and shows how to investigate a failure using the captured artifacts.

Execution Overview

1

Execution Summary

A test plan with 12 test cases completed in 2 minutes and 34 seconds across 5 parallel workers.

Metric	Value
Total Tests	12
Passed	10
Failed	1
Self-Healed	1
Duration	2m 34s
Parallel Workers	5

AI Agent: Parallel execution distributes tests across multiple browser workers simultaneously, reducing total run time significantly compared to sequential execution.

2

Test Case List

Click any test in the list to view its step-by-step results.

12 test cases in this run:

#	Test Name	Status	Duration
1	Login — valid credentials	Passed	12s
2	Login — invalid password	Passed	9s
3	Login — MFA flow	Failed	18s
4	Add item to cart	Passed	14s
5	Apply discount code	Passed	11s
6	Checkout — credit card	Healed	22s
7	Order confirmation email	Passed	8s
8	Profile — update email	Passed	10s
9	Forgot password flow	Passed	13s
10	Search — product name	Passed	7s
11	Filter by category	Passed	9s
12	Mobile — responsive nav	Passed	11s

AI Agent: Failed and healed tests are highlighted in the list. Selecting a test shows its individual step results and links to all captured evidence artifacts.

3

Step-by-Step Results ✓

Selecting test #3 ("Login — MFA flow") shows the individual step results.

Steps for "Login — MFA flow":

1. ✓ Navigate to /login — 245ms
2. ✓ Enter email in Email field — 120ms
3. ✓ Enter password in Password field — 98ms
4. ✗ Click the Sign In button — POST /api/auth/login → 401 Unauthorized

AI Agent: Each step shows the action performed, the element targeted, the timing, and — for failures — the error response. A screenshot thumbnail is available for every step.

Actions available from the results view:

• Re-run All
• Export Report
• Share the result URL with recipients who have access to the ContextQA organization

Failure Investigation

1

Screenshots

The Screenshots tab shows a thumbnail for each step. Failed steps are highlighted in red, making it easy to see exactly what the browser displayed at the moment of failure.

Step screenshots for "Login — MFA flow":

• Step 1: Navigate — Pass
• Step 2: Enter Email — Pass
• Step 3: Click Login — Fail

AI Agent: Screenshots are captured automatically after every step — no configuration required. They are stored and accessible indefinitely from the execution results.

2

Console Log

The Console Log tab shows all browser console output captured during the test, including errors, warnings, and info messages with timestamps.

[12:34:01] INFO   Page loaded — https://demo.contextqa.com/login
[12:34:02] INFO   DOMContentLoaded
[12:34:04] ERROR  Cannot read property 'submit' of null
[12:34:04] WARN   Login button selector mismatch — retrying
[12:34:05] INFO   Self-healing activated

AI Agent: Console logs are captured at the browser level for every test run. The full log is indexed and searchable across executions — useful for diagnosing intermittent JavaScript errors.

3

Network (HAR) Trace

The Network tab shows every HTTP request made during the test, including the status code, response time, and content type — in HAR format.

GET   200  /login             45ms   text/html
POST  200  /api/analytics     12ms   application/json
POST  401  /api/auth/login    38ms   application/json  ← FAILED
GET   200  /assets/main.js   890ms  application/javascript

AI Agent: The HAR trace captures every network request, making it straightforward to identify failed API calls, slow responses, or unexpected redirects that caused a test to fail.

4

AI Root Cause Analysis ✓

The Root Cause AI tab provides an automated analysis of the failure, synthesizing the screenshot, console log, and network trace into a human-readable explanation with a suggested fix.

AI Root Cause Analysis
━━━━━━━━━━━━━━━━━━━━━━

Failure Summary:
  The login request returned HTTP 401 Unauthorized.
  The API rejected the credentials in step 3.

Classification: APPLICATION_BUG

Affected Step: 3 (POST /api/auth/login)

Evidence Used:
  • Screenshot step 3 — login form submitted
  • HAR log — 401 response from /api/auth/login
  • Console log — error: "Authentication failed"

Suggested Fix:
  Verify the test credentials are valid in the staging
  environment. The user account may have been deactivated
  or the password may have changed. Update the Test Data
  Profile with valid credentials.

AI Agent: Root cause analysis is generated automatically for every failed test — no manual investigation needed to understand why a test failed. The AI classifies the failure type (Application Bug, Flaky, Test Bug, or Environment Issue) to help teams prioritize their response.

Evidence Artifact	Format	Captured Automatically
Step Screenshots	JPG	Yes — every step
Session Video	WebM	Yes — full run
Console Log	Text	Yes — full browser log
Network Trace	HAR	Yes — all requests
AI Root Cause	Text	Yes — on failure
Playwright Trace	ZIP	Yes — DOM + timing

---

See ContextQA with your own workflow — Book a Demo →

Related documentation

Run tests · Review execution video and screenshots