Before using this feature, set up the Claude Code integration first. See Claude Code Integration for installation and authentication.
Creating a Test
In Claude Code, use the/decipher-qa slash command followed by a description of what you want to test:
- Explore your codebase to understand your pages, components, and routes
- Generate test steps based on your description
- Run the test on a cloud-hosted browser
- Validate each step and capture screenshots
Describing Your Test
Write your prompt like you’d explain the test to a teammate. Be specific about what the test should do, but you don’t need to be technical. Good prompts:| Prompt | What Claude generates |
|---|---|
test the login flow with invalid credentials and verify the error message | Navigate to login, enter bad credentials, submit, assert error message appears |
test creating a new project, editing its name, then deleting it | Full CRUD flow across multiple pages |
test the billing settings page as an admin user | Authenticated flow using a login identity |
test that the search bar returns results for "shoes" | Navigate to search, type query, assert results appear |
- Mention the specific page or feature (e.g., “the settings page”, “the checkout flow”)
- Include what you want to verify (e.g., “verify the success message appears”)
- Mention the user role if the flow requires authentication (e.g., “as an admin user”)
Generating Multiple Tests
You can ask Claude to generate several tests at once:Automatic Self-Fixing
When a generated test fails during validation, Claude automatically diagnoses and fixes the issue:- Decipher’s agent runs each step and flags any failures with diagnostics and screenshots
- Claude analyzes the failure — wrong selector, missing wait, incorrect assertion, etc.
- Claude fixes the failing steps
- Validation resumes from where it left off, without re-running the entire test
Modifying Tests with Natural Language
After a test is created, you can modify it without manually editing steps. Use “Ask for Changes” in the Decipher dashboard or ask Claude directly:When to Use Claude vs. Recording
| Scenario | Recommended approach |
|---|---|
| You know the flow but don’t want to click through it | Claude — describe it and let Claude generate the steps |
| The flow involves complex interactions you’d rather demonstrate | Recording — click through it with the Chrome extension |
| You want to generate tests for multiple flows quickly | Claude — describe them all in one prompt |
| You need to test a page that isn’t built yet | Claude — generate tests from your code before the UI is live |
| You want to capture exact timing and interactions | Recording — the extension captures your real behavior |