Text2Test Logo
Request a Demo
Reporting·Test Reports

Every test execution, drillable to the AI request that ran it.

Each test in your suite produces a Test Report when it runs. Pass/fail status, duration, executor, browser, environment. Click any test to see step-by-step replay, AI requests, screenshots, console logs, and network calls.

Request a Demo
app.text2test.ai / test-results
Dablin.co
Features
Analytics
Web Test
Overview
Test Results
Get Extension
Doc
Automation
Overview
Plan Results
Test ResultsLast 30 days ▾
Every web test execution across this workspace.
Pass Rate
27%76 / 279+4.3%
76
Passed
174
Failed
0
Running
21
Stopped
0
Pending
8
Errored
Search by test name, executor, run id...
Filter
Anyone ▾
TEST
STATUS
EXEC.
DUR.
STARTED
ENV.
Dablin.co – Homepage
Passed
Scheduled
33s
11/05/2026 14:03
Chrome
Demo from check
Passed
Manual
19s
07/05/2026 17:34
Chrome
Checkout – Apple Pay path
Failed
Manual
1m
04/05/2026 11:38
Chrome
Login – invalid credentials
Failed
Manual
14s
04/05/2026 13:41
Ext.
Search – sponsored card
Passed
Scheduled
17s
04/05/2026 13:03
Mobile
Cart drawer – quantity stepper
Failed
Manual
39s
04/05/2026 13:00
Brave
Header nav – mega menu hover
Error
Manual
5s
04/05/2026 09:00
Opera
Pricing – toggle annual/monthly
Stopped
Manual
8s
03/05/2026 08:44
Opus
What every test report captures

Per-test, per-step, per-call detail.

Status and timing

Passed, failed, running, stopped, pending, errored. Exact start time, duration, and which run number this was.

Step timeline

Every step that ran, in order, with duration per step. Spot slow steps at a glance.

AI request and response

The raw JSON request and AI response for each step. Useful when a step does something unexpected and you need to understand why.

Screenshots

Captured at every step automatically. Toggle through them inline or expand to full size.

Replay video

Full MP4 playback of the test run. Watch the test execute end to end.

Console and network logs

Console messages and network requests captured during the run.

Audit the model layer

See the exact JSON the AI ran.

For every step, the Test Report shows three tabs: AI Request, AI Response, Screenshot.

The AI Request tab includes URL, step UID, action, direction, type, argument, element, location, context, intent, and justification.

This is the layer most testing tools hide. We show it because debugging a step is impossible without it.

Environments tracked

Every test row shows the environment it ran in.

Filter and sort by browser to see how your suite behaves across the matrix.

Chrome
Firefox
Safari
Edge
Opera
Brave
Browser Extension
Row actions

One click per common task.

↻
Re-run (same env)
Repeat the test with identical setup
⎘
Copy share link
Public URL, 7-day expiry
↓
Download logs
Console and network output as .log
↓
Download replay video
Full test run as .mp4
⚑
Mark as flakySoon
Tag the test so it shows up in flakiness analytics
Mark as flaky
Soon

Tag a flaky test once. See it tracked over time.

A failed test is not always a real failure. Sometimes the test runs the same flow twice, fails the first time, passes the second. Most teams either ignore the flake or rerun the whole suite. Both waste time.

From any test row, mark it as flaky. The system tags the test, surfaces it in flakiness analytics, and keeps a count over time. You see which tests need fixing versus which tests are catching real bugs.

One-click flag

From the test row menu, click Mark as flaky. No separate workflow.

Analytics surface

Flaky tests appear in your flakiness view alongside their flake count and last failure.

Track until fixed

Once you ship a fix, verify the test passes consistently across new runs.

Find the run that broke yesterday in two clicks.

Filter by:

Time range — Last 30 days
Status — Passed, failed, running, stopped, pending, errored
Executor — Filter by who ran it, including ci-bot
Search — By test name, executor, or run ID
FAQ

Common Questions

The full test trace. In one click.

See per-step replay with AI requests inline. Live demo, your test runs.

Request a Demo