QAcove Documentation
A quick guide to how each part of the platform works.
Getting started
Create your free account and set up your first project — the starting point for organizing an application's test cases, runs, and bugs. The free trial lasts 30 days, no card required, with full access to runs, bugs, and reports.
Test cases
Every test case has steps, an expected result, and a priority, organized into folders within its project. Steps that repeat across several cases are saved once as shared steps and inserted wherever they're needed, without retyping them. If your team needs extra information (say, the affected module or the type of test), you can add custom text, long-text, or select fields from the project's settings. Text fields accept Markdown formatting (bold, italics, lists and code) with a button bar to apply it.
Runs and bugs
Every time you run a test case, you log a run with its result and notes — building a traceable history of what was tested and when. You can group the runs from a testing round into a run cycle, to see that round's progress at a glance. If something fails, you can report a bug with a severity and status, linked directly to the case that caused it. The result and notes of a run, and a bug's description, also accept Markdown, and you can upload screenshots or videos as evidence.
Reports
The reports section shows pass rate, bugs by severity, and run trends in charts, always up to date. From there you can also export a report to Excel to share outside the platform.
AI test case generation
QAcove can suggest test cases from a description of a feature, with a monthly generation quota based on your plan (8 on the free trial, 50 on Pro, 150 on Business, unlimited on Team). You can always edit what it suggests before saving it.
Integrations
Connect a GitHub repository to a project and track your bugs on a Kanban board inside QAcove, synced with GitHub Projects. Automatically creating an Issue for every reported bug can be turned on or off separately, depending on what your team needs. You can also set up an incoming Slack webhook per project to get notified when a bug is reported or a run fails.
API keys with permissions and REST API
From "My account" you can create several API keys (up to 10), each read-only or read and write, and optionally limited to a single project. They work for your coding assistant's MCP server and also for the public REST API at /api/v1: query projects, cases, bugs and a project status summary, and log runs from your own scripts. Keys respect your roles and your account's plan, and you can revoke them at any time. You can also list and create requirements (with coverage and links) from the REST API.
CI results and GitHub Action
Upload your automated test report (JUnit XML, Playwright JSON or a simple JSON) to POST /api/v1/ci/results and QAcove logs one run for each test that matches a case, by its code (for example TC-12) or its exact title. If a code repeats across modules, you can break the tie by writing the module in the test name ("Payments › TC-01"). With dry-run mode (dryRun) you see what would be logged without saving anything. For GitHub there is a ready-made Action: qacove/upload-results@v1. If you add onUnmatched=create, tests that match no case are created as new cases (up to 200 per upload and within your plan limit); with dryRun=true you see how many would be created without writing anything.
Outgoing webhooks
From Integrations you can add up to 5 webhooks per project so QAcove notifies your system (Zapier, n8n, Jira, your own server) when a bug is reported (bug.created), a run fails (run.failed, also from the API and CI) or a cycle is closed (cycle.closed). Each delivery is signed with HMAC-SHA256 in the X-QAcove-Signature header, using a secret shown only once when you create the webhook. Only public https URLs are accepted; if your server fails, QAcove retries once, and the Test button sends a test event and shows the result.
Requirements traceability
In each project's Requirements tab, record product requirements (RQ-1, RQ-2…) and link them to the test cases that verify them and the bugs that affect them. QAcove computes each requirement's coverage (no cases, failing, blocked, pending or covered) from the latest result of its cases, and exports the traceability matrix to Excel in one click.
Team collaboration
You can invite people to a project as an editor (creates, edits, and logs runs) or a viewer (view only). For a given editor, you can fine-tune their permissions: whether they can manage integrations (Slack, GitHub) and whether they can delete content (cases, bugs, folders, shared steps, and run cycles). How many people you can invite depends on your plan.