Getting Started

How HiTest works

HiTest is an AI QA Agent for web applications. It uses a real browser to interact with your product and check visible behavior, including authenticated workflows such as onboarding, checkout, billing, and permissions.

There are two common starting points: investigate a workflow now, or build checks you can repeat.

Explore a product workflow

Open AI QA Agent inside a project and choose Find issues. Set the scope, choose a Test Account if needed, and start. Review the findings and save the reports you want to track.

This path is useful for investigating a new feature or looking for problems before you have a test library. It does not require saved Test Cases. Follow the Find issues guide.

Build repeatable coverage

Create Test Cases by asking HiTest to explore, recording a demonstration, importing Excel, or writing instructions yourself. Review the cases, run them, then group useful coverage into a Test Plan.

  1. DescribeSave actions and visible expected results in a Test Case.
  2. ExecuteRun a case or a plan in a real browser.
  3. ReviewInspect the saved Run and investigate any Issues.
  4. RepeatRun manually, on a schedule, or after a deployment.
Review generated drafts before saving, then execute them to verify the behavior they describe.

The objects you will use

ObjectWhat it representsExample
ProjectThe application or environment being tested, with a Base URL.Your staging web app.
Test AccountReusable login credentials for a role.A staging workspace administrator.
Test CaseOne repeatable journey with actions and expected results.Invite a teammate and verify the pending invitation.
Test PlanA selection of cases to execute together.Release smoke checks.
RunA saved background execution and its case results.Today's smoke check after deployment.

Issues track reported problems, including reviewed direct findings and reports linked to failed background runs. An Issue's reproduction steps and expected versus actual result help your team investigate. Resolving an Issue records a decision; a new test run verifies the changed behavior.

Where the agent fits

The project header's AI QA Agent opens shortcuts for discovery, case creation, and running saved coverage. Interactive cards collect the settings before you start. Manage your saved cases, plans, accounts, and notification rules on their project pages.

Background runs save results in Runs. A single case can also use the agent's optional Live view mode for immediate browser inspection; its result stays in the card instead of being saved to Runs history.

Follow the Quickstart
Put these concepts into practice with one project, one case, and one saved run.