TestNeo
TestNeo Docs Regression Intelligence
Product guide

Regression Intelligence

Continuously turns project knowledge — real user journeys, production incidents, defects, designs, APIs, and code impact — into a recommended run pack and gaps to generate. You always approve creates; nothing invents a suite silently.

Release Intelligence vs Regression Intelligence. Release Intelligence is PASS / WARN / BLOCK for a change or release. Regression Intelligence is the suite brain: what to run and what to generate from journeys and incidents. Both live in the product; this page is the suite guide.
Knowledge (Connect or upload) → Thin ETL → Analyze → Run pack + Gaps → Generate drafts (approve) → Test Runner

Overview

Supported production sources:

SourceWhat TestNeo usesBest for
MixpanelThin event / funnel sequencesProduct journeys
AmplitudeThin event exportFunnels & drop-offs
HotjarFriction signals / Mixpanel-shaped eventsUX friction (upload often richest)
ClaritySession / insight rows (not video)Rage clicks & path friction
SentryUnresolved issues + breadcrumbsIncident → regression paths

Also fused when present: Jira / bugs, Figma, Swagger/API NLP, existing web tests, Engineering Memory, PR / code impact.

No warehouse dumps. Connect and upload both use thin JSON — sessions, journeys, issues — with hard caps.

Where to find it

  1. Sign in to app.testneo.ai
  2. Open Release Readiness (/web/release-readiness)
  3. Select your project
  4. Scroll to Regression Intelligence

You will see four tabs: Run this pack · Generate from knowledge · What changed · Connect sources.

How it works

1. Ingest Connect (API keys) or upload thin JSON. Cleaners + parsers store journey / incident requirements.
2. Analyze Ranks existing tests (impact, risk, Engineering Memory) and finds uncovered journeys.
3. Decide Run pack = open in Test Runner. Gaps = select → Generate drafts (deterministic NLP).
4. Next sprint New data → Sync / Refresh → What changed shows the delta.

Core ranking and NLP generation are deterministic (stable, inspectable). Optional narrative text explains the pack — it does not invent test steps.

Connect sources (recommended)

One-time setup per vendor. Credentials are encrypted at rest.

  1. Open the Connect sources tab
  2. Pick a vendor (Sentry, Amplitude, Mixpanel, Clarity, Hotjar)
  3. Enter API token / keys and org, project, or site ids as prompted
  4. Click Connect & sync — TestNeo validates, stores, pulls thin data, and refreshes analysis
  5. Later: Sync now, or wait for auto-sync (about every 6 hours when enabled)
VendorWhat you typically need
SentryAuth token (project:read, event:read) + org slug + project slug
AmplitudeAPI key + secret key (US or EU region)
MixpanelProject API secret (+ project id recommended)
ClarityData Export API token + Clarity project id
HotjarAPI token + site id (some plans still need JSON upload for rich sessions)
Seed demo pack appears only on localhost for demos. Customers on production never see it.

Upload JSON (always available)

If you prefer exports, or a vendor API is limited:

  1. In TestNeo Studio / Web AI chat, use Attach Analytics
  2. Upload Mixpanel, Amplitude, Hotjar, Clarity, or Sentry JSON (filename often auto-detects source)
  3. Return to Regression Intelligence → Refresh analysis

Same cleaners and parsers as Connect. Sample shapes live in the product docs / repo samples.

The four tabs

Run this pack

Ranked list of existing tests to run for recent risk (code impact, flakiness, Engineering Memory). Rank is a priority score, not accuracy %. Click Open in Test Runner — you choose when to execute.

Generate from knowledge

Journeys / incidents in project knowledge that are not covered yet. Select gaps → Generate drafts → review NLP in Test Cases → mark ready → run. Dismiss hides noise.

What changed

Sprint delta vs the last analysis snapshot: new gaps, resolved gaps, pack changes.

Connect sources

Manage vendor connections, Sync now, Remove.

Typical sprint loop

Sprint N: Connect / upload → Refresh → Generate drafts → Run pack → ship Sprint N+1: New production data → Sync / Refresh → What changed → accept new gaps → run pack again

As Jira, Figma, Swagger, and more tests accumulate in the project, analysis fuses them with analytics — coverage tracks how the product is really used.

FAQ

Does Connect auto-create tests?

No. Sync ingests knowledge and refreshes recommendations. Creating NLP tests requires Generate drafts (human approve).

Does anything auto-run in Test Runner?

No. The pack is a recommendation. You open Test Runner and start the run.

Is this the same as the Release Intelligence dashboard?

No. That dashboard is PR / Engineering Memory / release confidence. Regression Intelligence is the suite recommender on Release Readiness.

Will customers see Seed demo pack?

No — localhost / gated API only.

Last updated October 2026 · Regression Intelligence P0–P3 (analyze, generate, delta, Connect) · Thin analytics only · Open Release Readiness