“Step-by-Step Guide: Setting Up Your First Diff-IE Project” is the foundational documentation for initializing Diffie, an AI-driven, end-to-end (E2E) software testing platform that integrates directly with Claude Code.
The guide outlines a fast, three-step “Quick Start” process designed to get developers from a fresh installation to a passing, automated browser test using natural language. 🛠️ Step 1: Install the Plugin
The setup begins inside a Claude Code terminal session. You do not need to configure complex testing frameworks or boilerplate code. Instead, you run two quick slash commands within the console to pull the developer tool from the marketplace:
/plugin marketplace add diffie-ai/diffie-skill — Registers the official Diffie plugin marketplace.
/plugin install diffie@diffie — Installs the actual testing engine directly into the project environment.
Once running, the plugin remains globally active for any future Claude Code interactions inside that specific repository. 🔐 Step 2: Zero-Config Authentication
Diffie relies on an automated, web-based sign-in loop to eliminate manual API key configuration:
Automatic Trigger: The moment you issue your very first testing prompt, the terminal automatically launches a browser window.
Instant Account Linking: The browser prompts you to log in or authenticate with Diffie Cloud.
Session Persistence: Once verified, the credentials securely link back to the command line. Subsequent testing sessions authenticate automatically in the background. 🤖 Step 3: Author and Run Your First Test
Instead of writing heavy JavaScript or Playwright scripts, you author the initial test using plain, conversational English.
The Prompt: You provide a direct objective, such as: Create an E2E test for my app at https://app.example.com that covers logging in with email and password.
The AI Blueprint: Diffie maps the target application, scans the source code for UI selectors (like buttons and inputs), and presents a text-based testing blueprint to you for approval.
Execution & Playback: If the app requires hidden information, the plugin prompts you to save items like passwords as local LOGIN_PASSWORD secrets. It then runs the test, provides a pass/fail summary in the console, and links to a full video recording of the browser execution. If you are setting this up, let me know: What web framework your application uses?
Whether you want to configure this to run locally or against a live staging URL?
If you need help structuring your CI/CD configuration for automatic pull-request testing? Quick start | Diffie Docs