Skip to content
Hawzu Docs

Create a Test Run

3 min read

Test runs are created from the project’s Test Runs page and exist independently of any release.

Create a test run

Section titled “Create a test run”

  1. Open a project.

  2. Go to Test Runs.

  3. Click Create Test Run.

  4. Choose a Type — Manual or Automated (CI/CD).

  5. Enter a required Title.

  6. Add an optional Description and Labels.

  7. Complete any required custom fields.

  8. Select test cases.

  9. Click Create.

Fields

Section titled “Fields”

Type Manual or Automated (CI/CD) — “A manual run is worked through by testers; an automated run is driven by a CI/CD pipeline.” Choosing Automated (CI/CD) adds a CI/CD Config panel; see Automated runs below.

Title Required. The Create button is unavailable until a title is present.

Description Optional. Use this to describe what is being validated, the scope, or any special testing notes.

Labels Optional. Assign project labels to the test run. Search and select existing labels, create one with Create New Label when your role allows it, and remove a label from its badge. Labels appear in the Labels column on the Test Runs list and can be filtered there.

Custom Fields If the project has active custom fields for test runs, they appear during creation. Required custom fields must be completed before the test run can be created.

Select test cases

Section titled “Select test cases”

A test run can draw test cases from three sources.

Manual selection Use Add / Update Test Cases to choose individual test cases.

Requirements Add requirements to include their linked test cases. Requirements you have already selected are not offered again.

Test Suites Add test suites to include their test cases. Suites you have already selected are not offered again.

All three can be combined in one run.

Deduplication and source indicators

Section titled “Deduplication and source indicators”

If the same test case arrives from more than one source, Hawzu keeps a single copy. Source indicators show whether a test case came from manual selection, a requirement, a test suite, or several at once — so it is clear why a case is included without creating duplicate work.

Removing a source before creating removes only the test cases that source alone contributed. A test case still covered by another source stays selected.

Automated runs

Section titled “Automated runs”

Choosing Automated (CI/CD) replaces manual result entry with a pipeline. The CI/CD Config panel — “Which pipeline runs this test run, and what happens on create.” — asks for the provider, the repository or project, the workflow or job, and any build parameters.

You also choose what happens immediately:

  • Start a new build — the build starts at once and results import themselves when it finishes.
  • Use a finished build — pull the report from a build that already ran.
  • Just bind the pipeline — nothing runs now; start a build later from the run itself.

If no CI provider is connected, the panel says so: “No CI/CD provider is connected to this workspace yet. Connect Jenkins, GitHub Actions or GitLab CI under Integrations, then come back.”

Full detail is in Create an Automated Test Run.

If Create is unavailable

Section titled “If Create is unavailable”

Check:

  • A title is present.
  • Required custom fields are complete.
  • You have project access to create test runs.
Section titled “Related Guides”