Cofactor shows which parts of your product are tested, for which users, and which parts have never been tested at all.
Code coverage tells you which lines ran, but it can’t tell you whether a customer can still check out. Cofactor measures coverage of the product itself.
See which pages and flows are covered, and which depend on a single test.
If a page is tested for an Owner but never for a Viewer, that shows up as a gap.
Each flow links back to the requirement it came from, so you can see which requirements aren’t tested yet.
Requirements of your product that don’t have a test yet. This is the list of what you aren’t testing.
Filter to what changed and check whether anything affected by it is untested.
The whole team looks at the same view, so nobody has to explain a CI log.
You can back up the number, because every figure links to the runs and videos behind it.
Is this code coverage?
No. Code coverage tells you which lines of code ran. Cofactor’s coverage tells you which parts of your product have been checked, which is what customers actually notice.
How is a gap decided?
A gap is a requirement of your product that doesn’t have a test yet.
Can I export it?
Yes, through the API, so you can add it to the dashboards your team already uses.
Join the waitlist, or book a call to walk through your surfaces.