Stop writing tests.
Start describing them.
Raiken generates production-ready Playwright tests from plain English. It indexes your codebase and captures your UI to create tests grounded in how your app actually works.
One config file. Zero boilerplate.
"projectType": "nextjs",
"testFramework": "playwright",
"ai":
"provider": "openrouter",
"model": "anthropic/claude-3.5-sonnet"
What Raiken does today
A local-first CLI and dashboard that understands your project before generating a single test.
Code Graph Indexing
Raiken scans your project and builds a structured graph of components, routes, and dependencies—stored locally in .raiken/raiken.db.
Smart Project Detection
Automatically identifies your framework (Next.js, React, Vue), test framework (Playwright, Vitest), package manager, and entry points.
Live DOM Capture
Uses Playwright to capture a semantic snapshot of interactive elements on your page—buttons, inputs, links—so tests use real selectors.
Streaming Test Output
Describe what you want to test in plain English. Raiken streams AI-generated Playwright code directly to the dashboard as it's written.
Local Dashboard UI
A browser-based interface served by the CLI at localhost:7101 for writing prompts, viewing results, and managing tests.
Privacy by Default
All project context stays in your local .raiken/ directory. Only minimal prompts are sent to the AI provider you configure.
From install to first test in under a minute
No complex setup. No test recorder. Just describe what you want to test.
Initialize
raiken init Sets up config, test directories, and scripts
Launch
raiken start Opens the dashboard at localhost:7101
Describe
"Test that a user can add an item to their cart"
What we're building next
Where Raiken is headed
Beta testers help shape priorities. These are the capabilities we're actively working toward.
Multi-page flow capture
Navigate across pages with AI-guided loops so Raiken can capture full user journeys, not just single screens.
Ticket-aware test updates
When requirements change in Jira or GitHub, affected tests surface automatically so nothing falls out of sync.
Shared test graph
A visual map of test flows your whole team can build, review, and evolve together in real time.
Guided auth capture
Step-by-step session state capture so protected pages are testable without manual Playwright scripting.