Tester guide
How to Write a Useful Closed-Test Report
You do not need technical experience. A useful report simply lets the developer repeat one problem without asking for private information.
Confirm the correct game
StarEatingGirl SpaceCleaner is a separate private-testing game. It is not the production STAR-EATING GIRL game. Begin the report with the exact game name so code, package, assets, and Google Play tracks are never mixed.
Include six facts
- Build or version shown in the app.
- Device model, Android version, orientation, and approximate free storage.
- The screen, stage, and character where you started.
- The shortest numbered steps that reproduce the problem.
- What you expected and what actually happened.
- Whether it happened once, sometimes, or every attempt.
Use a clear category
Choose Access, Installation, Controls, Visual, Progress, Crash, Save, or Ad Reward. For a visual issue, name the character, enemy, item, boss, animation moment, and screen area. For an advertisement reward, say whether it opened, completed, closed, or failed and whether the promised reward appeared.
Protect personal information
Never send passwords, authentication codes, payment-card information, identity documents, home addresses, or unrelated notifications. Crop screenshots to the app area. Never click an advertisement to test revenue or click-through rate.
A useful example
Visual — StarEatingGirl SpaceCleaner. On [device] with Android [version], I selected [character] and started [stage]. During the third attack frame, a rectangular fragment appeared beside the right hand. It occurred in three of three attempts. Expected: only the character and weapon should be visible.
Test one path at a time
Begin from a known state: fresh install or update, selected hero, stage, network state, and whether the app resumed from the background. Follow the shortest path that produces the problem, restart, and repeat. If the result changes, record both outcomes instead of guessing.
For saving, verify state before leaving and after returning. For controls, describe finger action and character response. For a crash, include the immediately preceding action. These observations compare input, state, and output without access to a tester's account or device.
What happens after a report
A report may be confirmed, require detail, match a known issue, or remain unreproduced. Confirmation does not promise a release date. A follow-up should identify the build where behavior changed and repeat the original steps. Never manufacture ad activity, ratings, downloads, or engagement during testing.
About this guide
Written and tested by AllLife Games. This first-hand guide describes the studio's own game or production process. It was reviewed against current site and release information on August 31, 2026. Corrections can be reported through Support.