---
title: "Test and release a small adult game"
description: "Test routes, controls, saves and the delivered package, then release a build you can identify, support and recover."
language: en
canonical: https://bestadultgames.io/en/developers/guides/test-and-release
---

[Developers](https://bestadultgames.io/en/developers.md) / [Guides](https://bestadultgames.io/en/developers/guides.md) / Production

Intermediate · A reading priority

# Test and release a small adult game

Test routes, controls, saves and the delivered package, then release a build you can identify, support and recover.

Best Adult Games · 3 min read · Sources checked 5 October 2026 · Based on published documentation

![Three cards connected by arrows: Brief, Playable slice and Release. Brief is highlighted in coral.](https://bestadultgames.io/images/developer-guides/test-and-release-intro-1.svg)

*Define the candidate and its test matrix before declaring the game ready to release. Best Adult Games · original diagram*

Test the build players will receive. A game that runs in the editor can still ship with missing assets, broken old saves or a storefront description that promises more than the package delivers. Give the release candidate a stable identifier and a short test matrix before testing begins.

Aim for three useful results: a tested package, a known-issue list and a support record. Choose checks around the game's systems and promised devices. A large test suite that only repeats implementation details can leave the problems players will encounter untouched.

## Freeze a candidate you can identify

![Three cards connected by arrows: Source revision, Build ID and Candidate. Build ID is highlighted in coral.](https://bestadultgames.io/images/developer-guides/test-and-release-section-1-1.svg)

*A build ID ties each test report to the package it actually covers. Best Adult Games · original diagram*

Record the source revision, engine version, content version and intended targets. Build from a clean workspace, or document its state. Once testing starts, check the effects of any further changes; an unrelated edit can still affect the candidate you are preparing to ship.

Keep the package and its checksum with the release notes. Ask testers to name that candidate, their device and the route they followed. A corrected development build should never be mistaken for the package they actually tested.

## Cover important routes and state

![Three cards connected by arrows: Routes, State and Test coverage. Test coverage is highlighted in coral.](https://bestadultgames.io/images/developer-guides/test-and-release-section-2-1.svg)

*Test route choices and saved state together, including required unlocks. Best Adult Games · original diagram*

Make a matrix covering every ending, major exclusive route, threshold and required unlock. Test a fresh start, save/load around choices, restart and supported update states, including old saves. Include skip, history and rollback wherever the game provides them. A working ending does not excuse a broken scene unlock along the way.

Check repeated events and exits from unusual states. A scene can look fine while granting a reward twice or leaving a route flag inconsistent. Turn defects found during development into focused regression checks, so the same bug does not quietly return in the next candidate.

## Verify the intended interaction

![Three cards connected by arrows: Input, Feedback and Interaction. Input is highlighted in coral.](https://bestadultgames.io/images/developer-guides/test-and-release-section-3-1.svg)

*Watch a tester navigate without explaining what each control is meant to do. Best Adult Games · original diagram*

Ask a tester to navigate without coaching. Check dialogue pacing, what menus communicate, legibility, keyboard or touch input, focus and settings. Watch for places where the player cannot find the next action. Your explanation of a button will not be bundled with the game.

Test audio controls and any motion or playback settings. Include interrupted sessions and returns from the background where relevant. Check that accessibility options behave reliably through routes and the save system; seeing the right toggle on the settings screen is only the start.

## Inspect packaging and external dependencies

![Three cards connected by arrows: Package, Dependencies and Install. Dependencies is highlighted in coral.](https://bestadultgames.io/images/developer-guides/test-and-release-section-4-1.svg)

*Launch the delivered package outside the source project to check what it needs. Best Adult Games · original diagram*

Install or extract the distribution outside the source project, then launch it there. Check for missing files, file-permission problems, save-location issues and required runtime components. Verify that the package contains no development secrets or unnecessary source data.

For a browser release, serve the actual export from the intended hosting context. Check asset paths, storage behavior and slow or failed loads. For a download, test the delivery archive and installation instructions on the supported operating system. The package players receive belongs in the test, too.

## Match the public description to the build

![Three cards connected by arrows: Description, Screenshots and Actual build. Actual build is highlighted in coral.](https://bestadultgames.io/images/developer-guides/test-and-release-section-5-1.svg)

*Every public promise should match the content and limits of the release build. Best Adult Games · original diagram*

Describe the available content, supported languages, system requirements, edition differences and known limitations accurately. Review the channel's current publishing and AI disclosure requirements. Choose public previews that meet the channel's content rules.

Do not label a prototype a finished game or present an estimate as a measured requirement. Use representative screenshots, and identify editorial illustrations when you use them. Resolve the payment and content approvals needed for the actual distribution route before release.

## Release with a recovery path

![Three cards connected by arrows: Release, Backup and Recovery. Release is highlighted in coral.](https://bestadultgames.io/images/developer-guides/test-and-release-section-6-1.svg)

*Archive the candidate and its sources so a later fix has a traceable starting point. Best Adult Games · original diagram*

Archive the candidate, editable sources, rights register and test evidence. Publish clear version information, a support contact and known issues. Keep a previous usable release where the distribution agreement allows it, so recovery does not depend on reconstructing an old build from memory.

When a report arrives, reproduce it against the affected version before making broad changes to the project. Fix the cause, check related state and update the regression matrix. Good support means being able to explain which build changed, what the fix covers and what you verified.

## Key decisions

- Give the packaged candidate a stable ID and test that package.
- Cover route boundaries, required unlocks and supported old saves.
- Check controls, delivery and the public description together.
- Archive the release and add fixed defects to the regression matrix.

## Guide files

[Release checklist](https://bestadultgames.io/developers/templates/release-checklist.md) [Test matrix](https://bestadultgames.io/developers/templates/test-matrix.csv)

External model communities and publishing sites may contain explicit material. Source links open in a new tab; this guide does not load their previews.

### Sources & further reading

- [Ren'Py release and build guidance](https://www.renpy.org/doc/html/build.html)
- [Godot export documentation](https://docs.godotengine.org/en/stable/tutorials/export/index.html)
- [Steam release process](https://partner.steamgames.com/doc/store/releasing)

Last checked 5 October 2026.

## In this guide

1. [Freeze a candidate you can identify](https://bestadultgames.io/en/developers/guides/test-and-release#section-1)
2. [Cover important routes and state](https://bestadultgames.io/en/developers/guides/test-and-release#section-2)
3. [Verify the intended interaction](https://bestadultgames.io/en/developers/guides/test-and-release#section-3)
4. [Inspect packaging and external dependencies](https://bestadultgames.io/en/developers/guides/test-and-release#section-4)
5. [Match the public description to the build](https://bestadultgames.io/en/developers/guides/test-and-release#section-5)
6. [Release with a recovery path](https://bestadultgames.io/en/developers/guides/test-and-release#section-6)

## Related tools and models

- [Git LFS](https://bestadultgames.io/en/developers/tools?q=Git%20LFS)

[Production templates](https://bestadultgames.io/en/developers/templates.md)

## Related guides

Production · Beginner · 3 min read

### [Plan a small adult game you can finish](https://bestadultgames.io/en/developers/guides/first-adult-game.md)

Define the player experience, count the assets, and choose a release route before your first adult game grows beyond its budget.

Read the guide → S reading priority

Production · Intermediate · 3 min read

### [Preserve saves across episodic updates](https://bestadultgames.io/en/developers/guides/save-updates.md)

Keep old saves usable with stable IDs, versioned state, representative test saves and clear update and recovery policies.

Read the guide → A reading priority

Production · Intermediate · 3 min read

### [Budget assets for mobile and browser builds](https://bestadultgames.io/en/developers/guides/mobile-performance.md)

Budget downloads, memory, video and input responsiveness on target devices while protecting the approved look.

Read the guide → A reading priority