Hawzu by Snoowl
Start free
Grounded in 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 Read-only by construction MCP server Let Claude, ChatGPT or Cursor read your test data
Author Requirements Hierarchy, tasks and coverage that rolls up the tree Canon The documents your AI output is grounded in and cites Atlas A map of the product, and what to retest when it changes
Run & catch CI/CD Automation Trigger a pipeline from a run, then import its report Releases Release-gated executions and a go/no-go you can defend Defects Native defect tracking and drag-and-drop Kanban boards
Understand Observatory Pick the question and it builds the chart for you Reports Readiness, traceability, coverage and flaky tests
Extend Integrations GitHub, GitLab, Jenkins, Jira, Slack and webhooks AI in Hawzu Readiness summaries, semantic search and rewrite
Compare Test Management OracleAI Pricing Blog Docs Login Start free
Changelog

Hawzu ships every month. Here's the receipt.

Every meaningful change since April 2025, newest first — and all of it on every plan, including the free one. Dates mark when the work landed, not a version number; we release continuously rather than in numbered drops.

Everything you can use today

Shipped, documented and in the free plan. Newest first.

  1. New Improved

    A test recorder, single sign-on & an audit trail for AI clients

    Hawzu learned to record a test in Chrome and keep it as steps and scripts, to sign your team in through your own identity provider, and to show administrators every call a connected AI client made.

    • Sign in through your company's identity provider — Okta, Microsoft Entra ID, Google Workspace or any OpenID Connect or SAML 2.0 provider — on every plan. Verify your email domain with one DNS record first, so your provider speaks only for addresses you own.
    • Require single sign-on once you have tested it, and a password stops opening the workspace for everyone on your verified domains. People on other domains carry on as they are, and an owner with two-factor authentication keeps a way in if the identity provider is ever unavailable.
    • Let a first sign-in bring somebody in, with a role you choose, instead of an invitation — or leave it off and keep inviting people yourself.
    • On Enterprise, connect your directory over SCIM so Okta or Microsoft Entra ID adds, updates and removes people in Hawzu as your directory changes. Someone deactivated there loses their workspace access here, including project access, pending invitations and connected AI clients.
    • Record a test once in Chrome with the Hawzu Recorder extension, in beta, and the test case keeps it as readable manual steps and two scripts, Playwright (TypeScript) and pytest + Selenium (Python), that your own CI runs, with each result mapping back to the test case by its code.
    • The recorder's controls sit in Chrome's side panel, beside the page rather than on top of it, and fields it recognises as passwords, one-time codes or card numbers, or that you mark Secret, are saved only as an environment variable name.
    • Write a recording into the test case as its manual steps, replacing or adding after what is there, open the Locators tab to see which locator each script uses and what else was tried, and when a page changes, fix the broken locator once in the project's Object Repository so every test case that uses it gets the new one.
    • Workspace managers can review every call a connected AI client made — which tool, when, and whether it was refused — in Settings → MCP activity. The arguments a call sent are kept; what came back never is, so reviewing a connection does not mean storing a second copy of your data.
  2. New Integration AI

    Pricing, an MCP server & a map that argues back

    Hawzu got its pricing and self-serve billing, opened up to AI clients over MCP, and started telling you when the things describing your product disagree.

    • Connect Claude, Claude Code, ChatGPT, Cursor or VS Code straight to your project over MCP, and ask about your test cases, requirements, defects and releases without leaving the editor you already work in.
    • It is read-only by construction and reads exactly what your own role reads, refusing rather than returning an empty list when it may not look. It uses no Hawzu AI credits, works on every plan including the free one, and connects with an access token or by signing in and approving one workspace — administrators can see and disconnect every connection into theirs.
    • Atlas now shows you where the things describing your product disagree: your specifications placing a feature somewhere your folder tree does not, parts of the product your tests walk through that the map has never been told about, and two nodes that look like one thing counted twice. Each side sits beside the other, dated and cited, so you can decide which is right.
    • A Map tab in Release Analysis and Execution Analysis shows the Atlas map narrowed to what that release, or a single run of it, actually walked, with each journey's health read from that scope, so a sign-off can see which parts of the product were exercised and which were not.
    • Duplicate a test case, or a whole folder with its subfolders and every case inside, so a new variant starts from something you already wrote instead of a blank form.
    • Comments on defects follow the same rules as comments everywhere else — anyone who can read a defect can read its discussion, you can always edit your own, and removing someone else's takes a moderator.
    • Three plans — Free, Growth and Enterprise — with no feature behind any of them: they differ by how much you use, never by what the product can do. Free covers five people in any mix of writers and read-only viewers, with the whole product including the AI, and does not expire, and Growth can be tried free for 14 days without a card, landing back on Free with your work intact.
    • Move to Growth yourself in workspace settings — monthly or yearly, priced from your real team before you confirm anything, with read-only viewers at a quarter of a member — alongside a billing card showing the period, the seat cost and every invoice raised so far.
  3. AI New Integration

    Oracle, Canon & Atlas

    Hawzu learned to read your specs, map your product, and answer questions about your project in plain English.

    • Ask Oracle a question about your project in plain English — it answers from your records, cites the ones it used, draws the chart when a chart is the answer, and can create records for you.
    • Point Canon at your specifications and requirements documents, and Hawzu's answers and generated test cases are grounded in them, with citations back to the source.
    • Atlas builds a map of your product's journeys, shows coverage on it, and tells you what to retest when something changes.
    • Rebuilt release, execution and readiness reports, so a sign-off decision reads off the evidence rather than a status field.
    • Pull results straight from Jenkins, GitHub Actions and GitLab CI — Hawzu parses the report and maps each result to its test case, so nobody transcribes pass/fail by hand.
    • Redesigned tables across the app with a persistent action rail, plus refined dataset variables and fixes to smart assign, test case diff and the coverage gaps view.
    • Full documentation for all three: thirty new pages across the Oracle, Canon and Atlas sections.
  4. New AI

    Observatory, subscriptions & demo projects

    Analytics you can ask questions of, and notifications that follow the work you care about.

    • Subscribe to a requirement, release or test run and get notified the moment it moves.
    • Observatory rebuilt as a command center — pick a question and it builds the chart, with saved collections and a 0–100 project health score.
    • Spin up a fully populated demo project in one click to explore Hawzu with realistic data.
    • Delete a project for good, with a force cleanup that purges its files and history.
    • The audit log gained an activity timeline, so a day's changes read in order.
  5. New Integration

    Requirement hierarchy, webhooks & the public API

    Requirements grew a tree, and Hawzu opened up to your own tooling.

    • Break requirements into sub-requirements and tasks, and report across the whole tree.
    • Signed webhooks fire on the events you choose, so Hawzu can drive automation you own.
    • A documented public API with an interactive reference — build against Hawzu directly.
    • Defects now appear inline in the executions table, alongside a rebuilt defect view.
    • Upgraded file manager and a new People custom field type.
  6. New Improved

    Reports, smart assignment & a platform refresh

    A proper reporting suite, plus the interface refresh that came with it.

    • A full reports suite — coverage, activity, defect aging and traceability — all exportable.
    • Smart assignment distributes test cases across the team instead of picking them one by one.
    • Flakiness scoring surfaces the tests that pass and fail without the code changing.
    • Notification center, background job dashboard and quick filters on defects.
    • Refreshed interface with an automatic light/dark theme and a layout that holds up on small screens.
  7. AI New Performance

    AI assistance, dataset variables & a faster backend

    AI moved into the authoring flow, and one test case learned to run against many data sets.

    • AI rewrite cleans up test case wording; Defect AI surfaces likely duplicates before you file.
    • Static and dataset variables let a single test case run against many sets of data.
    • Import test steps directly from a file instead of retyping them.
    • Chart presets, application preferences and a guard that stops you losing unsaved work.
    • A rebuilt backend that cut page and API load times across the app.
  8. New AI

    Automation insights, API docs & split view

    Quality trends over time, and a faster way to work a list.

    • Automation and defect insights track how quality trends over time, not just where it stands today.
    • Semantic search across defects and requirements finds related work by meaning rather than keywords.
    • Split view — work a list and a detail pane side by side.
    • See exactly where a label, parameter or shared step is used before you change it.
    • Attachments and avatars moved to signed-URL storage, with alternate 2FA verification added.
  9. New Improved

    Labels, a modern file manager & the public site

    Lighter-weight organisation, and a better home for your evidence.

    • Labels with multi-select filtering across modules, for the grouping that doesn't deserve a custom field.
    • A rebuilt file manager for attachments and test evidence.
    • The audit log extended with time-series history.
  10. New Improved

    Audit log, custom fields & documentation

    Answering “who changed this, and when?” — plus a documentation site to go with it.

    • A full audit log covering who changed what, when, across every module.
    • Custom fields overhauled with a proper lifecycle, and filters that understand them.
    • Change history on test cases and executions.
    • Import test cases from generic Excel files, whatever tool exported them.
    • The documentation site launched, with screenshots throughout and an AI assistant that answers from the docs.
  11. Integration New

    Integrations, Gherkin & help chat

    Hawzu started talking to the rest of your stack.

    • GitHub, Jira, Slack and Linear integrations — file or link an external issue as you create a defect, and see its live status on the defect.
    • Gherkin authoring, single-step test cases, and Markdown or HTML pasted straight into the editor.
    • Shared steps became usable inside execution, not just authoring.
    • In-app help and support chat, a settings page, and dedicated groups and roles pages.
  12. Improved New

    Analytics everywhere & a design refresh

    Every major screen gained the numbers that belong on it.

    • Repository overview with coverage analytics and trends.
    • Quick filters on the repository and defect views, for the cuts you take every day.
    • Column controls and analytics headers across the major screens.
    • Rebuilt login page and typography that scales with your display.
  13. Performance

    Built for large repositories

    The work that keeps Hawzu quick at thousands of test cases.

    • List virtualisation keeps repositories, suites and executions fast well past a thousand test cases.
    • Database indexing across the board, for faster search and filtering.
    • An invite-and-signup flow with avatars, so getting a team in takes minutes.
  14. New Improved

    Release analysis, bulk actions & self-serve accounts

    Releases got an opinion about whether they are ready to ship.

    • Release analysis turns execution and defect data into a readiness picture.
    • Bulk select operations, plus a combined view and search across the repository.
    • Permissions enforced across every module, with roles management to go with them.
    • Self-serve signup with email verification and password reset.
  15. Improved New

    Rich editor, history & charts

    Test cases and defects became somewhere you can actually write.

    • Inline images and attachments in the editor, with a floating formatting toolbar.
    • History tab on defects — every change, in order.
    • Charts for execution and defect trends.
    • Scoped access tokens and API logs.
    • Unsaved-changes protection across every form.
  16. New Integration

    Defect management, Jira & 2FA

    Failures stopped being a dead end and became something you can track.

    • Native defect management, tied to the test step that failed.
    • The first integration: Jira.
    • Filters persist in the URL, so a filtered view is something you can send to someone.
    • Comments across modules.
    • Two-factor authentication with backup codes, plus user management and settings.
  17. New

    The foundation

    The first version of Hawzu.

    • The test case repository, with rich-text authoring from day one.
    • Test suites, requirements and releases.
    • Roles scoped to a workspace and to individual projects.
    • Custom fields, filters and access control.

What we're building next

Ordered by how close it is, not by date. We don't publish target dates — this list moves as we learn what matters, and nothing on it is a promise.

  • In progress

    Manual test cases into automation scripts

    Turn a test case you already wrote into a runnable script — the steps, the dataset variables and the expected results emitted as code for your framework, so automating a suite starts from what your team documented rather than a blank file.

  • Planned

    Email notifications for what you watch

    Get an email when a requirement, release or test run you watch changes, as well as the notification inside Hawzu, so the people who need to know hear about it without keeping a tab open.

  • Planned

    Record across new tabs and popups

    Keep recording when a step opens a new tab or a popup, such as a sign-in window or a link that opens in a new tab, and follow it in both scripts instead of marking the step for review.

  • Planned

    Playwright for Python scripts

    Get a third script from the same recording, Playwright in Python, carrying the test case code so its results map back like the other two.

  • Planned

    Review and approval for test cases

    Send a test case for review and have named reviewers approve it, see at a glance which cases are approved when you build a run, and restore any earlier version from its history.

  • Planned

    Re-run failures, due dates and your own statuses

    Start a new run with only the failed or blocked cases, or clone a run in one click. Give runs due dates and time estimates, and define the execution statuses and priorities your team actually uses.

  • Planned

    Saved views and scheduled reports

    Save a filtered view for yourself or share it with your team, and have Observatory dashboards and reports arrive by email or Slack on a schedule, so stakeholders stay informed without logging in.

  • Planned

    What to run for this release

    Let Oracle recommend a run scope ranked by risk — flaky history, past failures, open defects, changed requirements and Atlas impact — with the reason for every case, so a short regression window goes where it matters.

  • Planned

    Hawzu CLI and GitHub Action

    Send test results to Hawzu from any CI pipeline with one command, or drop in the GitHub Action, without writing your own API scripts.

  • Exploring

    Java and Selenium scripts

    Get a Java + Selenium script from the same recording, with the test case code carried in a form your JUnit reports keep, so results map back without extra setup.

  • Exploring

    Hawzu Recorder for Microsoft Edge

    Install the recorder from the Microsoft Edge Add-ons store and record in Edge the same way as in Chrome.

  • Exploring

    Test library health sweep

    Find duplicate, near-duplicate and stale test cases across your whole repository, and flag steps too vague to run, so the library stays lean as it grows.

  • Exploring

    Failure triage by Oracle

    Turn a cluster of failing results into a root-cause summary and a pre-filled defect, checked against the defects you already have so the same bug isn't filed twice.

  • Exploring

    Let AI agents write back through MCP

    Let your coding agent create test cases, record results and file defects through the Hawzu MCP server, with every call visible on the MCP activity page.

  • Exploring

    Exploratory testing sessions

    Run time-boxed sessions against a charter, capture notes and screenshots as you go, and turn what you found into test cases or defects when the session ends.

  • Exploring

    Generate test cases from screenshots and designs

    Give Oracle a screenshot or a Figma frame as well as documents, and get test cases for the screen it shows.

Everything launched is in the free plan

Hawzu has been in active development since April 2025. Every feature in the launched section is available today, and every one of them is on every plan — including the free one. The plans differ by size, never by capability. No seat minimums, no quote-only wall.

Start free Read the docs

Talk to Us

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

Hawzu is built for structured, execution-driven QA teams.

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: —

We'll only use your email to schedule and confirm your demo.