Written from your specs AI Test Case Generator Map the coverage, then write the cases you pick Do the test once Record a Test Beta Get readable steps and Playwright + pytest scripts It can only read MCP server Let Claude, ChatGPT or Cursor read your test data Compare Test Management OracleAI Pricing Blog Docs Login Start free
CI/CD Automation

Your pipeline already runs the tests. Hawzu makes the results mean something.

Start a build from a test run. Hawzu reads the report and puts each result on the test case it belongs to.

Drives JenkinsGitHub ActionsGitLab CI
Parses JUnit / xUnitTRXNUnit 3Cucumber JSONAllure
An automated test run in Hawzu — build history with a build in flight, a completed build expanded to its per-test results, grouped failure causes, and the source JUnit report

One run in Hawzu, with each build broken down test by test.

One path, whichever provider

From your pipeline to your test cases

  1. Trigger

    Hawzu starts the build, or you pick one that already ran.

  2. Watch

    You see its progress, and whether a failure is your tests or the import.

  3. Parse

    Hawzu reads the test report the build produced.

  4. Map

    Results are recorded on the matching test cases.

What you get

Automation results a sign-off can rest on

The report 47 rows
reconciled against
This run 40 test cases
Applied 38 rows

Recorded on their test cases.

Quarantined 9 rows

They match nothing in this run. You can still see them, but they never count toward pass rates or readiness.

Not executed 2 cases

The report never mentioned them, so they stay Not Executed.

The hard part

Matching a test to a test case

Use any of these. Hawzu checks them in this order.

  1. 1

    A code stated by the report

    Tag the test with its test case code, like @CHK-123 in Cucumber. It survives any rename.

  2. 2

    A code in the test's name

    Just put the code in the title. A test can name several test cases, and each gets the result.

  3. 3

    An exact title match

    Works for suites without codes. If two test cases share a title, Hawzu doesn't guess.

Or don't let us drive

Pipelines that already run on their own

Prefer to start builds yourself? Your pipeline can report to Hawzu instead.

A signed webhook

Your pipeline tells Hawzu when it's done, and Hawzu fetches the report.

Post the report

Send the report with one API call, from any CI.

curl --data-binary @results.xml \
     -H 'Authorization: Bearer <token>' \
     '.../import/results?run_title=CI%20build%20123'
One connected system

Automation feeds everything downstream

Automated results count toward coverage and readiness just like manual ones.

Connect a pipeline in a few minutes

Every feature on every plan. Free for five people, then $20 per member. No credit card.

Talk to Us

Tell us about your QA setup. We'll get back to you within 24 hours.

Book a demo

Pick a time that works — we'll confirm by email and send a calendar invite.

Select a date

Available times

Times shown in your timezone: —