How to Write Release Notes for Closed Test Builds
Good “What’s new” notes for testing tracks say what changed and what to check. A template, examples, and how notes become production evidence.
Short answer
For a test build, release notes should say what changed, what to re-test, and who reported it. Keep each line short, credit testers where you can (“Fixed widget refresh, thanks to two testers”), and add a “please check” line. They tell testers their feedback mattered and give you a dated record of fixes.
Where they go
When you create a release in Play Console you can enter release notes (“What’s new”) per language. On testing tracks, testers see them on the Play listing for the test version. Keep them within Play Console’s character limit per language.
Template
1.0.4 (test) Fixed: widget now refreshes after midnight (reported by 2 testers). Fixed: crash when denying notification permission on Android 13. New: undo after deleting a habit. Please check: the widget tomorrow morning, and whether undo feels obvious.
Good vs weak notes
| Weak | Strong |
|---|---|
| Bug fixes and improvements | Fixed crash when opening Stats with no data |
| Updated UI | Larger check-off button (testers missed it on small phones) |
| New version | Please re-test sign-in with Google. We changed the flow |
Why they help your application
The production access questionnaire asks what you changed because of testing. A trail of dated release notes, each pointing to tester reports, is exactly that evidence. Keep a copy in your own changelog with the versionCode and date.
Rhythm during a 14-day test
- Day 0: first build. Notes explain the app and the first tasks.
- Days 4-7: first fix release from early feedback.
- Days 9-12: second fix release, plus anything left from the pre-launch report.
- Last 2 days: avoid risky changes. Stability matters when you apply.
Don’t forget to bump the versionCode (see version code already used). Shipping updates doesn’t reset the 14 days (see does updating reset the clock).
Frequently asked questions
Do release notes need to be in every language?
You can provide notes per language. For a closed test, the language your testers use is enough.
Can I leave release notes empty?
You can, but testers then don’t know what to check. A few lines make every update more useful.
Should I copy test notes into production?
Rewrite them for public users. Leave out tester credits and internal details.
Sources and how we keep this accurate
- Play Console Help: App testing requirements for new personal developer accounts
- Android Developers: Version your app
Policy facts are checked against Google's own documentation on the date shown above. Google can change requirements at any time, so confirm in your Play Console. Where we give advice or estimates rather than Google's rules, we say so. TestersZone is independent and not affiliated with Google. Drafts are AI-assisted and reviewed by our team.
Need 12 testers? Get them free.
Test 3 apps, earn 60 credits, and list your app for up to 20 real testers with verified daily check-ins.
Start freeKeep reading
Does Updating Your App Reset the 14-Day Closed Test?
How to Triage Tester Feedback in a 14-Day Closed Test
Applying for Production Access After Closed Testing
How to Upload Your First App Bundle to Play Console
How to Promote a Closed Test Release to Production
How to Test In-App Purchases With License Testers
Browse all guides, or see the quick answers, guides and comparisons.