How We Test Games

Every one of the 171 games on SZ Games went through the same six steps below. We reject far more games than we publish, and the reasons are logged so the decision can be checked later.

1. License review

We open the license file for the code and look for an explicit license for every asset: sprites, music, sound effects and fonts. Accepted code licenses include MIT, BSD, ISC, Zlib, Apache 2.0, MPL 2.0 and the GPL family. Accepted asset licenses include CC0, CC BY and CC BY-SA. Anything missing, vague, non-commercial, "no derivatives" or "personal use only" is turned down, even when the game is excellent.

2. Originality check

We skip projects that reuse characters, logos, music or level designs from commercial games. When an open-source game recreates a classic format, it gets a plain descriptive name on SZ Games and keeps its own art. Brand names stay out of titles, page headings and descriptions.

3. Cleanup

Only the files a game needs are copied to our server. Analytics, outside ads, external fonts and links that would pull you away are removed or stored locally. License files and in-game credits are never deleted. Every change is written into a notes file next to the game, and for copyleft licenses we publish the matching source code.

4. Automated browser test

A headless browser opens every game page, presses Play and watches for script errors, missing files and requests to other domains. A game that fails does not go live. The same test runs again whenever the site is rebuilt, which catches problems before players do.

5. Hands-on play

A person plays each game on a desktop and on a phone-sized screen. That session is where we confirm the real controls, the goal, how scoring works and whether touch input is good enough for the "Works on mobile" badge.

6. Writing the guide

Only after playing do we write the page. Rules, level counts, modes and controls come from what we saw in the game and its code. We never add star ratings, play counts or reviews, because we cannot measure them honestly. Each page shows the date it was last tested and updated.

What happens after launch

Browsers change, and games can break. If you hit a problem, use the "Report a problem" link on the game page. We re-test the game, fix it if we can, and remove it if we cannot. Rights holders can always ask for changes through thecopyright policy, and the full list of authors and licenses is on thecredits page.