Recorded on their test cases.
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.
One run in Hawzu, with each build broken down test by test.
From your pipeline to your test cases
-
Trigger
Hawzu starts the build, or you pick one that already ran.
-
Watch
You see its progress, and whether a failure is your tests or the import.
-
Parse
Hawzu reads the test report the build produced.
-
Map
Results are recorded on the matching test cases.
Automation results a sign-off can rest on
They match nothing in this run. You can still see them, but they never count toward pass rates or readiness.
The report never mentioned them, so they stay Not Executed.
Matching a test to a test case
Use any of these. Hawzu checks them in this order.
- 1
A code stated by the report
Tag the test with its test case code, like
@CHK-123in Cucumber. It survives any rename. - 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
An exact title match
Works for suites without codes. If two test cases share a title, Hawzu doesn't guess.
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' 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.