Test Cases

A Test Case is a repeatable product workflow with ordered actions and observable expected results. Each background execution uses a fresh browser session, the project's Base URL, and the case's current configuration.

Choose how to create coverage

Generate, Record, and Import open in HiTest QA Agent. They produce editable drafts; select the cases you want and click Create to save them. If this is your first case, follow the Quickstart.

Give each case a clear outcome

Give every case a stable starting point, the setup it needs, and a success condition visible in the UI. Cases should run independently from the Base URL instead of depending on state left by another case.

Configure the saved case

• Name: The journey being verified.
• Test Account: Optional project account for authenticated flows.
• Priority: Low, Medium, or High.
• Precondition: Setup instructions before the main steps.
• Status: Active or Inactive. Plans execute only Active cases; running a case directly can still execute an Inactive case.
• Folder: Optional grouping for organization and plan targeting.
• Proxy: Optional proxy access and country, available on Starter and Team.
• Steps: At least one ordered Action and Expected result pair.

See Fields and limits for accepted input and Test Accounts for login setup.

Run and keep useful coverage

Run a saved case to verify it against your application. Background execution keeps the result in Runs. Review failures before changing the case or running it again.

Once you have a few useful checks, organize them with folders and include them in a Test Plan. Plans run only Active cases with steps; check execution counts alongside the final status.