Skip to content

Quick Start

2 min read

This guide walks through the shortest useful path for a new Hawzu user.


Go to https://app.hawzu.com/, enter your email address and password, and select Log In.

If two-factor authentication is enabled, complete the verification prompt before continuing.

Learn more in Login.


After login, Hawzu opens your default workspace when one is set. If no default workspace is available, Hawzu opens the first available workspace or the Workspaces page.

From the Workspaces page, you can:

  • Open a workspace.
  • Star frequently used workspaces.
  • Set or clear a default workspace.

When you sign up, Hawzu provides a workspace for your account. Other workspaces appear after you are invited and accept the invitation.

Learn more in First Workspace.


  1. Open a workspace and go to Projects, then select Create Project to open the create-project window.

  2. Enter the project details:

    • Project Name — required, at least 3 characters.
    • Project Code — required, exactly 3 characters (e.g. TCM). It prefixes the project’s test case and requirement codes, like TCM-123.
    • Project Description — optional short summary.
  3. (Optional) Assign workspace users to project roles. Each row takes one or more users and one project role; use Add Role Assignment when different users need different roles. A user or role already chosen in one row isn’t available in the others.

  4. Select Create Project. The button is enabled once the required fields are valid.

  5. Return to the workspace Projects page and open the new project card.

Learn more in First Project and Creating a Project.


Open the project and go to Repository. Create test cases with a title, description, priority, severity, type, automation status, requirements, labels, preconditions, and steps where needed.

For reusable setup or repeated flows, use shared steps and parameters where your team has configured them.

Learn more in Creating Test Cases.


You can run testing in two main ways:

  • Use Test Runs for standalone, ad-hoc, regression, exploratory, or quick validation work.
  • Use Release Executions when testing is tied to a release milestone.

Both workflows let you select test cases manually, from requirements, or from test suites, then record results such as Passed, Failed, Blocked, Skipped, or Not Executed.

Learn more in Executions and Test Runs.


When testing finds an issue, create a Hawzu defect or link an existing defect. Defects can include priority, severity, assignee, due date, comments, attachments, traceability links, and external issue references when integrations are configured.

Learn more in Defects Overview.


Use release insights, execution analysis, defect insights, and Observatory panels to understand testing progress and quality risks.

Learn more in: