Recommended mix
Not sure where to start? Get test-type suggestions based on the application data collected.
AI BUSINESS TEST DESIGN
Generate business tests. Beyond happy paths.
Choose from ten test types to guide the scenarios TestZombie suggests — such as successful journeys, invalid input or boundary values. Explore gaps in test coverage instead of generating more of the same tests.
Test more than the happy path — including what can go wrong
A successful click rarely provides enough coverage on its own. Choose what to test: regular journeys, invalid inputs, boundaries, search, navigation or accessibility. You can also ask for a suggested selection.
Happy path
Check a typical successful journey such as signing in, searching or checking out.
Validation
Test empty required fields, invalid email formats and helpful validation messages.
Negative
Check that the application handles invalid input or disallowed actions correctly.
Boundary
Explore boundary values such as maximum text length, quantities or numeric ranges.
Navigation
Check that users can reach their destination through menus, links and page transitions.
Search
Test how search and filters respond to relevant, empty or unusual queries.
UI Interaction
Include actions like opening a dialog, clicking a button or using a dynamic form.
Accessibility
Generate test suggestions for detectable accessibility concerns. This does not replace a full WCAG audit.
Combined
Combine multiple test aspects into realistic user journeys when the collected data supports them.
Suggestions depend on what was actually captured during discovery. “Recommended” does not guarantee complete test coverage, and accessibility suggestions do not replace a WCAG audit.
From discovered journeys to reviewable business tests
Start with a website address or a recorded test journey. Choose the test type and number of cases. Review each suggestion, its steps and expected result before using it.
Website to test casesWhat does this produce?
Example: a checkout may yield a successful purchase, missing required input, invalid voucher input or a cart value boundary – where supported by the discovery evidence.
How test design, healing and code maintenance fit together
Create new test cases and maintain existing tests independently. Used together, these capabilities support you from the first test idea to ongoing maintenance.
Find more test cases in your application
Start with a website address or an existing automated journey. Review the suggested cases and decide which ones to automate next.
Request a demo