1. [Home](https://www.g2.com/)
2. ...
3. [Automation Testing Tools](https://www.g2.com/categories/automation-testing-tools)
4. [CoverOps Discussions](https://www.g2.com/products/coverops/discuss)

[
 ![CoverOps](https://images.g2crowd.com/uploads/product/image/large_detail/large_detail_f77b5923ed540fdb3e2cdd6e41419f89/coverops.png "CoverOps")
](/products/coverops/reviews)

# CoverOps Discussions

CoverOps is a runtime test coverage and change impact analysis platform for QA and engineering teams. It answers the questions a coverage percentage cannot: which code did each test actually execute, what did this change touch, which tests reach it, and which changed lines did no test reach at all. How it works: lightweight agents run next to your services in test, staging or production (Java, .NET, Node.js, Python, Go and PHP). While automated suites or manual testers exercise the application, the agents record which files, methods and lines each test executes. Coverage is measured on the running system, across services, not only inside unit tests. What teams use it for: - Change impact analysis: point CoverOps at a commit range and see every changed file and line, the tests that last reached it, and the changed code nothing covers. - Test selection: CI asks which tests a change can reach and runs only those. An observation mode records what selection would have skipped while still running every test, so you can prove it is safe before you rely on it. Optional periodic full runs keep the data fresh. Plugins exist for Jest, Vitest, Playwright, Cypress, pytest, JUnit and TestNG, plus a GitHub Action and a CLI. - Quality gates on changed code: a rule such as "80% of changed lines on main" that CI evaluates on every build, so an untested new method cannot hide inside a healthy average. - Flaky test detection and quarantine, based on verdicts that flip on the same code. - Dead code: methods that were loaded in a running environment but never executed. - Code graph and service map: which service calls which, how often, how slow, and how well each part is covered. - KPI targets with notifications to Slack, Microsoft Teams, email or a webhook, reports with CSV export, and a detailed audit log for enterprise governance. CoverOps does not schedule or run your tests; it works with the test tools and CI you already have. It is available as a cloud service hosted in AWS Frankfurt, or self-hosted with Docker Compose, Helm or Terraform, including air-gapped installations. Packages are sized by monitored lines of code, projects, agent instances, users and sessions.

## Be the first to start the conversation

Get answers from real professionals in the G2 community.