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 within its project. 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.
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. If something fails, you can report a bug with a severity and status, linked directly to the case that caused it.
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, unlimited on Team). You can always edit what it suggests before saving it.
Integrations
Connect a GitHub repository to a project so every reported bug automatically creates an Issue there. You can also set up an incoming Slack webhook per project to get notified when a bug is reported or a run fails.
API token and coding assistants
From "My account" you can generate a personal API key to connect QAcove to an AI coding assistant (like Claude Code) through its MCP server — so it can read and write your test cases directly from your editor, respecting the same limits and roles you already have on the platform.
Team collaboration
You can invite people to a project as an editor (creates, edits, and logs runs) or a viewer (view only). How many people you can invite depends on your plan.