Supported Report Formats
1 min read
Hawzu parses reports, not automation source code. If your framework can emit one of the formats below, Hawzu can import it — no plugin, no SDK, and no assumptions about how the tests were written.
Formats
Section titled “Formats”| Format | Typical source |
|---|---|
| JUnit / xUnit XML | Playwright, pytest, Jest, TestNG, Selenium, PHPUnit |
| TRX | dotnet test, MSTest, Visual Studio |
| NUnit 3 XML | NUnit |
| Cucumber JSON | Cucumber, Behave, SpecFlow, Godog |
| Allure result JSON | Allure-instrumented suites |
Most frameworks reach this list through JUnit XML — it is the format CI systems consume, so nearly everything can emit it.
Detection
Section titled “Detection”You do not choose a format. Hawzu inspects each artifact and detects it, trying the narrower formats before the broader ones: TRX, then NUnit, then JUnit, then Cucumber, then Allure.
Zip archives are unpacked automatically — which is what a GitHub Actions artifact always is, and what an Allure results directory looks like once uploaded.
If one file inside an archive cannot be parsed it is skipped rather than failing the build. Only a build where nothing could be parsed is reported as an error.
Limits
Section titled “Limits”| Limit | Value |
|---|---|
| Maximum size of a single report or artifact | 64 MB |
| Artifacts downloaded per build | 10 |
| Artifact download timeout | 120 seconds |
| Other CI provider calls | 30 seconds |
Hawzu only downloads artifacts that could plausibly be a report — .xml, .json, .trx, .zip, and archives. Playwright videos and traces are left where they are, so a large artifact bundle does not slow the import down.