agentleFS
Sign inStart free
mejbaurbaharmejbaurbahar/software-tester-skills/skills/game-testing/SKILL.md

game-testing

Skill1 starsChanged 53 days agoMITView on GitHub

Use when testing video games — gameplay/balance, playtesting, performance (FPS, frame pacing, memory), input devices, save/load integrity, multiplayer/netcode, platform certification (TRC/TCR), localization, anti-cheat, monetization, and Unity/Unreal automation.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Unity: Test Framework (Edit/Play mode), Unity Test Runner CLI -runTests -testPlatform PlayMode, Performance Testing package, AltTester.

    line 31

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Game Testing

Games combine software correctness with feel, fairness and fun. Blend scripted checks, exploratory play and telemetry.

Test areas

AreaFocus
FunctionalityCore loop, progression, quests/scripting triggers, UI/menus, achievements, tutorials, edge-of-map/out-of-bounds, sequence breaks, softlocks
CompatibilityGPU/driver/OS matrix, consoles/handhelds, controllers, resolutions/aspect ratios (ultrawide), HDR, refresh rates, cloud saves
PerformanceAvg FPS and 1%/0.1% lows, frame-time spikes/stutter (shader compile, streaming), load times, VRAM/RAM, thermals on mobile/Deck, battery; soak 4–24 h for leaks (memory-leak-resource-testing)
Multiplayer/netcodeLatency/jitter/packet loss (clumsy, tc netem), rollback/prediction correctness, desync detection, host migration, matchmaking, lobby/party, NAT traversal, server load, cheating/exploits
Save/loadSave at every state, corrupt/partial save, versions/migration, cloud conflict, disk full, quit during save
Economy/balanceCurrency sinks/sources, dupe exploits, drop rates statistics, difficulty curve (telemetry), progression pacing
MonetizationIAP purchase/restore/refund, entitlement sync, parental controls, loot-box odds disclosure (payment-ecommerce-testing)
LocalizationText expansion, fonts/glyph coverage (CJK, Arabic RTL), VO sync, culturally sensitive content, age ratings (localization-testing)
AccessibilityRemappable controls, subtitles, colorblind modes, difficulty options, motion/photosensitivity (Game Accessibility Guidelines; accessibility-testing)
CertificationPlatform requirements (Sony TRC, Xbox XR, Nintendo Lotcheck, Steam Deck Verified, Apple/Google store policies): suspend/resume, controller disconnect, account switching, trophies
Audio/visualClipping, z-fighting, LOD pop-in, shader errors, audio ducking/desync (visual-testing)

Automation

  • Unity: Test Framework (Edit/Play mode), Unity Test Runner CLI -runTests -testPlatform PlayMode, Performance Testing package, AltTester. Unreal: Automation System/Gauntlet, Functional Tests, stat fps/unit, Unreal Insights. Godot: GUT/GdUnit4.
  • Bots/monkey: random-input agents crawling levels, navmesh-coverage bots, replay-input determinism (record inputs + seed → replay), screenshot diff of known camera points.
  • Smoke per build: boot → main menu → load level → 60 s play → quit; fail on crash/hang/assert/log-error thresholds, track perf vs baseline.
  • Telemetry & crash: Sentry/Backtrace symbolicated crashes, funnel and heatmap analytics to find where players quit or die.

Playtest process

Define goals & questions · recruit target players · observe (don't coach) · think-aloud · capture video+telemetry · rate severity by player impact, not code cause · retest fixes; use structured bug titles ([Level 3][Boss] Player falls through floor after dodge-roll on ramp + repro save file).

Bug report extras

Build/CL number, platform/SKU, save file, video clip, coordinates/level, repro rate, network conditions, log & dump (bug-reporting).

Related

performance-testing, compatibility-testing, exploratory-testing, mobile-testing, chaos-resilience-testing

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free