Step 01 · Define

What are we
testing today?

Give Probe the minimum — a feature and what it should do. Drop in a diff and it maps the blast radius too. Works for any platform, any company.

Feature name *

What should it do? *acceptance criteria, user story, or plain intent

Platform

Your lens tailors what gets prioritized

Target environment optional

Code / diff to analyze optional — unlocks the impact map

Drag & drop diffs or source files, or browse — parsed locally in your browser.

Quality dimensions

How Probe works

1

Read the codeParses your diff → files, symbols, endpoints, risk.

2

Generate casesDerives cases from intent + detected patterns.

3

Map impactShows what changed and the blast radius.

4

Run & auto-fixStreams results; the agent fixes failures for you.

Minimum to QA anything

✓ A feature name

✓ What it should do

◦ Code/diff — optional

◦ Environment URL — optional

Step 02 · Suite

Test cases

Generated from your feature and code. Expand any case for its Given/When/Then — failing ones show a diagnosis and a one-click agentic fix.

Step 03 · Blast radius

Code impact

CHANGED FILES

Blast radius

Solid = direct change · dashed = likely downstream.

select a file

Symbols touched · coverage

Step 04 · Execute

Live run

probe run --suite generated --reporter stream

0%idle

Passed0

Failed0

Blocked0

Queued0

Latency

avg —0.0s

Step 05 · Verdict

Report

Pass rate

0%

Passed · 0

Failed · 0

Blocked · 0

Coverage by dimension

Release readiness

For your lens