Usage
Writing end-to-end tests has always been a two-step problem: figure out what to click, then figure out how to click it in code. The Diffie plugin handles the first step. It analyzes your source (the full repo or just a PR diff), proposes test cases covering the user-facing flows it finds, and on your approval creates them in Diffie. Diffie generates the Playwright code, runs it in a real browser, and hands back a video recording.
What you get
- Interactive test authoring. Ask Claude Code to create tests for your app. The plugin scans your source, proposes a spec, waits for your approval, then creates the test in Diffie and reports back with the run result.
- Selector-aware planning. The plugin reads your source for
data-testid,aria-label, and other selector hints and bakes them into the spec so generated tests don't rely on brittle CSS paths. - Real browser runs with video. Diffie runs every generated test in a real cloud browser and produces a Playwright recording you can watch, share, or seek through by clicking execution log lines.
- Secrets management. Store login credentials and API keys in Diffie once; tests reference them by name. Values are encrypted and never leave your workspace.
- Auto-fix. When a test fails, ask the plugin to reprocess it with a short fix prompt. The plugin updates the spec and Diffie regenerates the code and reruns.
- PR testing on tap. The same plugin can install a workflow that lets any teammate comment
/diffie teston a pull request and get an AI-generated test run back as a PR comment.
Your first test
Ask Claude Code, in plain English, to create a test:
> Create an E2E test for my app at https://app.example.com
that covers logging in with email and password.The plugin will walk through a short plan with you:
- Ask about credentials (it can read login email and password from a
LOGIN_EMAIL/LOGIN_PASSWORDsecret that it creates for you). - Scan your source (the whole repo, or just a diff if you point it at one) for the user-facing flows worth testing, plus selector hints like test IDs and aria labels so the resulting spec points at stable elements.
- Present one or more test specs and wait for your approval or edits before creating anything in Diffie.
- On approval, create the tests in Diffie via the API. Diffie generates the Playwright code, runs the test against the URL you provided, and records the session.
- Report pass or fail with a link to the recording. If it failed, offer to reprocess with a fix prompt.
State tracking
State is tracked in a .diffie-qa.md file in your project root, so the next conversation already knows what tests you have, which are passing, and what's being reprocessed. Commit this file into version control so the rest of your team shares the same view of the suite.
Common authoring gotcha
“Tests keep picking the wrong button.” Add a data-testid on the element you want targeted and reprocess the test. The plugin prefers stable test IDs over visible text, so a single testid hint is usually enough to pin the selector for good.