Now in development — in the open
From Performant Labs

Aftersight — open-source test intelligence, built CTRF-native.

Self-hosted, MIT-licensed, AI in the core.
Follow the build Book a testing review
aftersight.performantlabs.com
★ —
stars
repo is private for now
watching
public count at launch
v0.2.2-dev
current build
self-hosted · CTRF-native
MIT licensed
Latest build note: development is underway in the open — follow progress on the build.

Product features

HISTORY

Every run, one continuous timeline

CTRF reports land automatically and build a searchable history — no more digging through CI logs to find when a test started failing.

  • Pass/fail trend per suite
  • Jump straight to the offending commit
  • Works with any CTRF-emitting runner
aftersight.performantlabs.com/history
FAILURE ANALYTICS

See patterns, not just red X's

Aftersight clusters recurring failures across runs so flaky tests and real regressions stop looking identical in a wall of red.

  • Failure clustering across runs
  • Flaky vs. broken signal
  • AI-assisted root-cause hints
aftersight.performantlabs.com/analytics
SEARCH

Find the one failing assertion, fast

Full-text search across every report, stack trace, and log line — self-hosted, so your test data never leaves your infrastructure.

  • Full-text across all reports
  • Filter by suite, tag, status
  • Self-hosted — your data, your servers
aftersight.performantlabs.com/search
Services

The team behind Aftersight tests Drupal for a living. ATK, Testor, and the workflows that heal their own tests — available as services while we build the platform.

01 / Tools

Tools the Drupal community uses

ATK (Automated Testing Kit) and Testor are ours. Aftersight is in active development. All actively maintained, adopted across the ecosystem. Read the source. Ask questions.
02 / AI

Tests that heal themselves

Claude agents diagnose and fix broken Playwright tests in CI — nightly, on this very site. Not a demo. A shipped workflow, running right now.
03 / People

Experts alongside your team

When you need hands, we embed senior testing engineers. Nearshore project leads available. Fully billable or fractional.

Trusted by teams at

CBS Interactive logo
DocuSign logo
Orange logo
Renesas Electronics logo
Robert Half logo
Tesla logo
Dogfooding

We heal our own tests nightly.

Every night, Playwright tests run against this site in CI. When a test breaks, a Claude agent diagnoses the failure, classifies it (test issue or website issue), and — when appropriate — opens a pull request with the fix. No Monday-morning flake triage. The workflow is in our public repo: read heal-tests-claude.yml — the code that decides what our AI is allowed to touch. See the workflow →

Built for the whole Drupal team.

  • Dev teams catch regressions before users do.
  • Engineers deploy with confidence, not anxiety.
  • Manual test cycles drop as automated runs cover the regression surface.
  • Leadership ships on schedule and on budget.

Frequently asked questions.

What is the Automated Testing Kit (ATK)?
ATK (Automated Testing Kit) is the open-source Drupal testing library Performant Labs maintains on drupal.org. It ships pre-written Playwright and Cypress tests for the work every Drupal site ends up doing — login, registration, content CRUD, taxonomy, sitemaps, accessibility — so your team starts with a working suite instead of a blank file.
Do you work with Drupal CMS and contributed distributions?
Yes. We actively contribute to Drupal CMS and a wide range of contributed modules. Our engineers understand how distributions are composed and how to extend them without breaking upstream update paths.
How does a testing engagement work?
Four shapes, depending on what’s broken: a test-suite takeover (we fix and run a broken or abandoned suite), an embedded testing engineer (a senior testing engineer joins your team for a release cycle), an autonomous-healing pilot (we wire up the same Claude-agent workflow we run on this site, scoped to a slice of your CI), or accessibility testing (continuous WCAG audits in your pipeline). Most engagements begin within one to two weeks of scoping.
Can you test a Drupal 7 or Drupal 9 migration in flight?
Yes. We don’t run the migration — your team or your build agency does that — but we write the regression suite that validates each stage of it. Pre-migration baseline tests, mid-migration parity tests, post-migration smoke tests. The suite lives in your repo, runs in your CI, and stays yours after the migration ships.
Book a review

Ready for a release you don’t have to babysit?

Book a 30-minute testing review with a senior engineer. We'll look at your current workflow, tell you honestly where autonomous healing would (and wouldn't) help, and leave you with a one-page writeup. No sales pitch. No obligation.