Overview
HiTest tests your web application in a real browser. Start with one workflow, review what happened, then build a set of checks your team can run before every release.
Start hereRun your first browser testCreate a project, generate a test case, and review your first run.
How the workflow fits together
- Set upChoose your app URL and a test account if needed.
- Create coverageExplore, demonstrate, import, or write a workflow.
- Run & reviewExecute saved cases and inspect the evidence.
- RepeatGroup checks into a plan for releases or a schedule.
What do you want to do?
Turn a critical user journey into reviewed test cases you can run again.
Ask the agent to look for problems without creating test cases first.
Connect a test plan to your deployment pipeline and receive the result.
Use failure reasons and recordings to decide what needs to change.
Start from what you already have
| Your starting point | Follow this guide |
|---|---|
| A website and a workflow to cover | Generate test cases |
| A workflow you can demonstrate | Record a test case |
| An existing Excel test library | Import test cases |
| A precise set of actions and expected results | Write a test case |
| Saved cases ready to repeat | Create a test plan |
Product guides and reference
Use Getting started for your first run and Workflows for end-to-end tasks. The product guides explain Test Cases, Test Plans, and Runs and Issues in more detail.
For configuration, see Test Accounts and Notifications. For exact allowances and accepted input, use Credits and plans and Fields and limits.