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. Download what's available, read the source, ask questions.
Ship Drupal releases with confidence.
Book a testing review See how we test this site
Performant Labs built the Drupal testing stack the ecosystem already uses (ATK, Testor), is building Aftersight for the broader testing community, extends them with AI workflows that heal broken tests on their own, and — when you need it — embeds senior testing engineers alongside your team.
Tests that heal themselves
AI agents diagnose and fix broken Playwright tests in CI — nightly, on this very site. Not a demo. A shipped workflow, running right now.
Experts alongside your team
When you need hands, we embed senior testing engineers. North American project leads, nearshore delivery options. Fully billable or fractional.
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. No staging calls with a testing engineer chasing yesterday's flake. The workflow is in our public repo; you can 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.
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, a quarter, or open-ended), 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.
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.
Book a testing review
Or start with the tools