Your test runs already capture what changed, what was verified, and what passed. Zerocheck compiles that into release notes, changelog entries, and QA sign-off documents automatically. One click at release time, not two days of Jira archaeology.
“The hardest part about releases isn't the code. It's remembering what you changed and why. We spend more time writing release notes than reviewing the actual PR.”
Engineering Manager, Series B SaaSsource
“Our changelog was six versions behind. Every customer-facing bug report started with 'what version are you on?' and nobody could answer confidently.”
Developer Experience Leadsource
“We had a compliance audit where the auditor asked for evidence of what was tested before each release. We had CI logs that expired after 30 days and nothing else.”
CTO, B2B Fintechsource
Engineering teams spend an average of 4-8 hours per release cycle compiling release notes and QA documentation manually.
78% of teams report their changelogs are at least one version behind (State of DevOps surveys).
CI logs, the primary record of what was tested, expire after 14-30 days on most platforms, leaving no long-term documentation.
Release documentation falls into a gap between tools. CI/CD platforms (GitHub Actions, CircleCI) capture raw build logs but don't produce human-readable summaries. Project management tools (Jira, Linear) track tickets but don't know what was actually tested and verified. Changelog generators (standard-version, release-it) parse commit messages but have no connection to test results.
The result: release notes are written from memory, QA sign-off is screenshots in Confluence, and changelogs are maintained by whoever remembers to update them. Nobody connects 'what code changed' to 'what tests verified it' to 'what the customer should know.'
Release day arrives. The engineering manager opens Jira and scrolls through the last two weeks of tickets, trying to reconstruct what changed. They message three engineers on Slack asking 'did this actually ship?' QA pastes screenshots into a Confluence page. The release manager writes notes from memory. Two hours later, incomplete notes go out and the changelog stays outdated.
Every PR test run has already captured what changed and what was verified. At release time, the engineering manager clicks 'Generate release notes' and gets a structured summary: verified changes with test evidence, known issues flagged by failed tests, and a QA sign-off document linked to commits and timestamps. Export as Markdown, PDF, or JSON. Total time: 5 minutes.
Tests run on every PR, capturing which flows were tested and what the results were, with screenshots and step traces attached to the commit.
Test results are automatically compiled into structured release note entries per PR, including what changed, what was verified, and confidence scores.
At release time, export compiled release notes, changelog entries, and QA sign-off as Markdown, PDF, or JSON with one click.
Every document links back to the specific commits, test runs, and evidence artifacts, creating an auditable chain from code change to release documentation.
Yes. You control the template: which sections appear, how changes are grouped (by PR, by flow, by team), and the output format (Markdown, PDF, JSON). The default template works out of the box, but you can adjust it to match your existing release notes style.
It can, but it doesn't have to. Zerocheck generates release documentation from test results, which is a different data source than commit-message-based tools like standard-version. Many teams use both: Zerocheck for 'what was tested and verified' and conventional commits for 'what code changed.' The two complement each other.
Failed tests are flagged in the release summary as 'known issues' or 'unresolved failures,' depending on your configuration. You can choose to include them as warnings, exclude them, or require resolution before the release notes can be finalized. Flaky tests that were quarantined are excluded by default.
Each PR's test results are compiled independently. At release time, Zerocheck aggregates all PRs since the last release tag, deduplicates overlapping test coverage, and produces a consolidated summary grouped by feature area. You get one coherent release document, not 20 separate PR summaries.
Every test run generates the release notes, changelog entries, and QA sign-off your team writes manually today.
Book a walkthrough