Hamrad

Why teams switch

Three generations of QA tooling — you're stuck in one of them

Spreadsheets & wikis

Confluence DoDs, Excel cases, Postman on the side. Breaks the moment you scale.

Manual-first TMS

TestRail-style tools built before AI. Automation is a bolt-on, not the workflow.

Design → spec → cases → Playwright → release score. Hamrad throughout, one linked chain.

Spec Generator with refine chat
Convert manual cases to Playwright in one click
Real staging + saved OTP login

Hamrad built in

From requirement to running test — not a separate product

Hamrad runs across the quality workflow: write the spec, generate test cases, convert steps to Playwright, explain what broke.

📄

Spec Designer

Figma, PDF, or description → DoD/PRD with quality score and Persian/English support.

✅

Case Generator

Scenarios, manual steps, QA warnings. Review before import — no duplicate spam.

🎭

Playwright bridge

Hamrad converts manual steps to browser automation. Screenshots, video, trace on every run.

🩺

Failure analysis

Plain-English explanation of what broke, right on the run detail page.

Unified workspace

Everything QA needs — nothing to glue together

Projects & environments — staging URLs, saved login for OTP sites
Test suites — batch Playwright runs with live progress
API smoke — OpenAPI or Postman import, chained scenarios
Release readiness — score, blockers, coverage tags
Defect reports — shareable HTML with run evidence

Try the full workflow

Dashboard · 94% pass rate

94% pass rate

12 cases

2 blocked

Passed Failed Blocked

Full feature set

Everything in Hamrad, at a glance

Four workflows, one workspace — no separate tools to license, sync, or forget to check.

🗂️ Organize

Projects & environments — staging/prod URLs, saved OTP login per project
Test suites — group cases, edit name/URL/default environment
Tags & bulk actions — FR/smoke labels, bulk status or add-to-suite
CSV import — bring existing test cases into a project in seconds
Global search — projects, cases, history, runs — from the sidebar

⚙️ Automate

Playwright runner — steps → pytest script, video, screenshots, trace.jsonl
Run single case — one click from the case editor
Live suite progress — real-time job page, browser notification when done
Retry failed — rerun only what broke, not the whole suite
Scheduled runs — daily suite runs while the app is open
Hamrad failure analysis — plain-English explanation on the run detail page

📊 Track & report

Dashboard — pass rate, trends, flaky-case hints, recent jobs
Requirements coverage — tag-based matrix per project
Release readiness — score and blockers before every release
Shareable HTML reports — public link after every suite run
Export — project or suite as JSON, CSV, or Markdown
Notifications — in-app alert the moment a job finishes

🔌 Integrate

Jira backlog — Epic, Stories, and tasks in one click
Figma API — auto-download frames for the DoD generator
REST API — every action available and auto-documented at /docs

How it works

Five minutes from design to first test run

1

Spec

Figma or docs → DoD/PRD

2

Cases

Hamrad scenarios & steps

3

Run

Playwright on staging

4

Release

Release readiness score

Built for teams who own quality end-to-end

Solo QA / PM+QA

One person, full cycle. Spec, cases, automation — without enterprise TMS overhead.

Startup squads

UI + API smoke before every release. Honest blocked vs failed for OTP-heavy sites.

Persian & English teams

Auto-detect language on specs. Refine with Hamrad chat — free, no quota burn.

Your QA workflow, powered by Hamrad