Features
Everything Qaver can do today — 40 features across 5 areas.
Test Management13 features
| Feature | Description |
|---|---|
| Products & workspaces | Organize testing per product with member-based access control; admins and “all products” users see everything. |
| Test cases | Nested sections, priorities, types, preconditions, numbered steps, expected results, estimates and references. |
| Common test case sets | Shared banks of reusable cases (login, security, accessibility…) available in every product. |
| Test runs | Select cases (all, by section, or by keyword), assign per-case testers, and record pass / fail / blocked / retest results. |
| Test plans | Group related runs into a plan and track them together; closing a plan closes its runs. |
| Milestones | Tie runs to releases or dates and watch progress roll up. |
| Case versioning | Every edit snapshots an immutable version; runs pin the exact version they executed (fork-on-execute). |
| Keywords & organization | Tag cases with keywords, filter runs by keyword, and clone, copy or move cases — including copying into common sets. |
| KPI test cases | Mark a case as a KPI with a unit and chart its measured values across runs and releases. |
| Custom fields | Admin-defined fields (text, dropdown, multi-select, checkbox, date, URL…) on cases, results, runs and requirements, with required-field enforcement. |
| Reports & PDF export | Product and run reports with status distributions, tester breakdowns and PDF export. |
| Cleanup | Suggest-first housekeeping: stale never-run cases, old runs, and duplicate cloned runs — nothing is deleted until you review the exact list and accept. |
| Backup & restore | Download a full product backup and restore it into this or any other product. |
Requirements7 features
| Feature | Description |
|---|---|
| Rich-text requirements | Author requirements with formatting, embedded images and links; reference them from test cases (REQ ids). |
| Requirement hierarchy | Nest requirements under parents to decompose epics into specifics, with an indented tree view. |
| Coverage tracking | See per-requirement coverage rolled up from the latest execution status of linked cases; filter uncovered requirements. |
| Requirement versioning | Every edit snapshots a version with a change note; browse the full history on the requirement. |
| Sign-offs (e-signature) | Request approval on a specific requirement version; approvers sign with a typed name, and sign-offs show as outdated after later edits. |
| Comments | Threaded comments on requirements and test cases for lightweight collaboration. |
| Traceability matrix | Requirements ↔ test cases with latest status and sign-off state, exportable as CSV or PDF — the report auditors ask for. |
AI (Claude-powered)9 features
| Feature | Description |
|---|---|
| Test case generation | Generate reviewed-and-editable test case suggestions from a requirement or a free-text description, de-duplicated against existing cases. |
| Generation from mockups | Upload Figma frame exports or screenshots — AI vision drafts test cases or product requirements with acceptance criteria. |
| Automation script generation | Turn a manual case into a runnable script (Pytest first, plus Playwright, Cypress, Jest, Selenium…) — per case or in bulk per section. |
| Requirement-impact review | When a requirement changes, AI reviews the linked cases and flags each as OK, needs update, or obsolete, with concrete suggestions and coverage gaps. |
| Test prioritization | Rank a run's tests by risk — failure history and recency, cases changed since last execution, priority and type — with a reason per test and a priority-order view. |
| Smart follow-up runs | As bugs get fixed mid-release, AI assembles a shorter next run from the plan's history — failures to verify, flaky cases to re-test, changed cases, and a thin safety net — dropping stable passers. |
| Release notes generation | Turn a release's testing data — runs, pass rates, verified requirements, open issues with bug links — into a polished markdown document, with KPI measurements in a dedicated section. Copy or download for your release notes. |
| Test plan generation | Describe what's in the release and AI drafts the whole test plan — feature runs matched semantically against your case library, a lean regression baseline, and naming that mirrors your previous plans. Review every pick before creating. |
| Feature tagging | Optional one-click organizer: AI proposes feature keywords for your cases (reusing existing ones), you review and apply — no forced taxonomy, but sharper filters and planning when you want it. |
Integrations & API6 features
| Feature | Description |
|---|---|
| REST API v1 | Full API with human-friendly reference ids (P1, R7, TC12, TR29), API-key auth, and per-product access enforcement. |
| CI results ingestion | POST a JUnit/xUnit XML report from any CI (pytest, Playwright, Cypress, Jest…) and results land on the matching cases in a run. |
| Automation export | Export a product's generated scripts as a CI-ready bundle via the API. |
| Jira | Link requirements to Jira issues with live status, and file a Jira bug from a failed test with one click. |
| TestRail import | Connect a TestRail site and import projects — suites, section hierarchy and cases with priorities, types, steps and references. |
| Single sign-on (OIDC) | Okta, Microsoft Entra ID, Google Workspace, Auth0, Keycloak… with optional just-in-time account provisioning and password-login lockdown. |
Platform5 features
| Feature | Description |
|---|---|
| Roles & permissions | Admin, Lead and Tester roles; per-product membership; admin-managed users with password reset. |
| Self-service accounts | Users change their own password and upload a profile photo; avatars show across the app. |
| Activity log | Who did what, when — creations, edits, results, imports, sign-offs and cleanups are all recorded. |
| Dark mode | System-aware theme with a one-click toggle. |
| Self-hosting | Run the whole stack with Docker — a single all-in-one container for demos or a compose stack with automatic HTTPS. |