How dejav works
Describe your app, create tests, and run them whenever you need to check a change.

Describe
Give dejav a description of what your app should do: bullet points, prose, or cells pasted from a spreadsheet. No particular format is required.
Connect a GitHub repository to the project, and dejav reads the whole repository on each scan. It finds what to check in your specs, tests, and source code.
- Users can sign up with email and password
- Coupon SAVE10 takes 10% off the cart total
- Stock decrements after a purchase
- Pasted from a spreadsheet · 14 more rows
Generate
A scan reads your description against your site's pages and writes test cases. Each case has a title and a description of what to check and what should happen, and most name the page they start on. The intermediate results are saved with the scan, so you can check how each case was derived.
For each feature, dejav also writes cases you did not list. [Edge] cases cover boundary values, double submits, going back mid-flow, and empty states. [Error] cases cover invalid input, XSS and SQL injection, and access without signing in.
- Sign up with email and password
- Double submit on the signup formEdge
- Sign up with a malformed emailError
- Coupon SAVE10 takes 10% off the cart total
- Apply the same coupon twiceEdge
- + 4 more
Run
Select your tests and choose Run. Preparation happens automatically. If steps or expected results are missing, dejav tells you what to add.
Run tests as they are created, or save them for later. Results and screenshots stay together in the run.
- 1Open /cartpass
- 2Fill the coupon field with SAVE10pass
- 3The total is reduced by 10%pass
- Run passed
Run again
Run a saved test again with the same Run button.
Runs that need no preparation or repair use no extra credits. Edits to steps and expected results are applied on the next run.
- 1Open /cartpass
- 2Fill the coupon field with SAVE10pass
- 3The total is reduced by 10%pass
- Replayed · 0 credits · 6s
Automatic repair
When a page change prevents an operation, dejav attempts a repair within the run. There is no separate repair action to choose.
The steps and expected results stay the same. Product bugs and unresolved problems remain visible in the results. Successful automatic repairs use credits.
- Automatically repairing an operation that could not find its target
- Results recorded with the original expected outcomes
Credits and pricing
Credits cover test creation, execution preparation, and automatic repair. Other reruns use no additional credits. Free covers one site with no time limit.
Start testing with dejav.
Start free