Quick-start guide

Create your first reviewed test suite

Follow this workflow to turn a clear requirement into a useful test-case draft without treating AI output as a substitute for QA judgment.

1
Sign in
Use the Login button and complete Google sign-in. Authentication connects usage and available plan features to your account.
2
Choose a source
Start with a typed requirement or user story. Jira, URL, screenshot, and supported file workflows are available when you have the required access and configuration.
3
Provide useful context
Include the user role, goal, acceptance criteria, business rules, data limits, permissions, and expected errors. Never include passwords, tokens, secrets, or unnecessary personal data.
4
Select the testing approach
Choose the mode and scenario types that match your goal. A balanced review normally considers positive, negative, edge, UI, API, and permission-related paths where relevant.
5
Generate and review
Generate a first draft, then compare every case with the source. Remove invented assumptions, clarify steps, correct expected results, and add missing product-specific risks.
6
Export or automate
Use the available export that fits your workflow. Automation exports are starter code and still require stable selectors, fixtures, test data, assertions, and framework conventions.

Before you use the output

• Confirm every test maps to a real requirement or identified risk.
• Remove assumptions that are not supported by product behavior.
• Verify data, roles, permissions, expected errors, and environment constraints.
• Keep an approved version in your team’s normal test-management workflow.

Learn about accuracy, privacy, access, and troubleshooting.

Convert a user story into reviewed positive and negative cases.