QAcove
Changelog

QAcove Changelog

The most important changes we've shipped, in order.

October 6, 2026

  • Bugs on the board now show their screenshot as a thumbnail, the assignee's photo and, when someone else is reviewing them, their name on the card.
  • The Projects list now shows who is inside each project and in which folder, live.
  • If two people open the same case they now see each other; if one is editing, the other cannot save until they agree on who makes the change.
  • Folder presence: you now see who is working in each project folder, with their avatar and a notice inside the folder, so you can coordinate without overwriting the same cases.
  • CI uploads can now create cases automatically: add onUnmatched=create and tests without a case are created and recorded in the same upload.
  • Import requirements from a CSV and read or create them through the REST API (GET /api/v1/projects/:id/requirements and POST /api/v1/requirements); each case now shows the requirements it verifies.
  • New Requirements tab with traceability: link requirements to test cases and bugs, see their coverage and export the matrix to Excel.
  • Outgoing webhooks per project: receive reported bugs, failed runs and closed cycles in your own system, with an HMAC signature and a button to test them from Integrations.
  • New POST /api/v1/bugs to report bugs from your scripts; it notifies Slack just like the app.
  • Per-API-key rate limit (120 requests per minute): if you exceed it you get a 429 with the wait time.
  • More accurate CI upload: if a case code repeats across modules, you can break the tie by writing the module in the test name.

October 5, 2026

  • API keys with permissions: create several read-only or read-and-write keys, and limit them to one project, from My account.
  • Public REST API at /api/v1 to query projects, cases, bugs and a summary, and to log runs from your own scripts.
  • Upload your CI results (JUnit XML, Playwright or simple JSON) and QAcove logs the runs on the cases that match, with no duplicates on retries. Also available as a GitHub Action: qacove/upload-results@v1.
  • You can now edit the runs in a case's history: result, text, notes and evidence.
  • Markdown formatting (bold, italics, lists and code) when creating test cases, incidents and runs, with a button bar; notes and descriptions now display formatted.
  • Long or unbroken text no longer spills out of the test case cards.
  • Notifications now appear in your language (some titles used to show in English).
  • Evidence videos in test runs now play correctly.
  • Generate cases with AI: describe what you need with text or attach an image, and we guide you to activate the feature by messaging the administrator on WhatsApp or in the chat.

September 1, 2026

  • Folders to organize a project's test cases, and shared steps so you don't have to retype steps that repeat across several cases.
  • Run cycles, to group the runs from a testing round and see its progress at a glance.
  • GitHub Projects Kanban board inside QAcove, synced with the Issues in your connected repository.
  • Automatically creating an Issue for every reported bug can now be turned on or off separately from the Kanban board.
  • More granular roles for invited editors: you can now choose whether they can manage integrations or delete content, on top of the create-and-edit permission.
  • 2-step signup: first name, email, and password, with document verification moved to a second step.

August 30, 2026

  • New public Security page, with the real details of how we protect your account, your content, and your payments.
  • Per-person pricing note on Plans and the homepage, to make it easier to compare against other test management tools.
  • The free trial now lets you invite one more person to your project.
  • Homepage reviews are now real opinions from QAcove users, with their photo and star rating — they used to be examples only.
  • GitHub integration: connect a repository to your project and every bug you report automatically creates an Issue there.

August 29, 2026

  • Slack integration: get a notification in your channel when a bug is reported or a test run fails.
  • Terms and Privacy Policy acceptance notice the first time you log in after a meaningful change to those documents.

August 25, 2026

  • Automatic sign-out after 4 hours of inactivity, to protect your account if you leave a session open on a shared computer.
  • General security review: encrypting integration credentials at rest, browser security headers, and fixing cases where concurrent requests could exceed your plan's limits.
DocsSecurityBack to home