mcpField
R
roblox-playtest-qa

roblox-playtest-qa

github.com/ashexplainedTesting & quality38124 installsUpdated 17w ago
Repository

About roblox-playtest-qa

A QA skill for testing Roblox changes in Studio, covering both behavior and player-facing quality. It combines interaction, visual, state, and console checks in a structured playtest report.

Key features

  1. 01Checks setup and live play mode
  2. 02Tests movement, controls, and UI
  3. 03Verifies rewards and progression
  4. 04Inspects game state and console output
  5. 05Ranks issues by player impact

Use cases

  1. 01Validating a Roblox feature before release
  2. 02Checking controls and HUD during playtests
  3. 03Finding errors or performance risks after a change

MCP support

The skill uses MCP tools to control Roblox Studio, interact with the game, capture the screen, inspect instances, and review console output.

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/ashexplained/roblox-skills --skill roblox-playtest-qa

After installing, type/roblox-playtest-qain Claude Code to confirm it loaded.

Details

From the project README

Roblox Playtest QA

Purpose

Use this skill to verify that a Roblox change works in Studio and supports player-facing quality. A playtest should prove both behavior and feel.

Setup

  1. Run list_roblox_studios.
  2. Use set_active_studio if needed.
  3. Run get_studio_state.
  4. Start play mode with start_stop_play when verification requires live behavior.

Test Checklist

  • First action is reachable within 10-30 seconds.
  • Controls work without keyboard-only assumptions.
  • HUD text is readable and not blocking gameplay.
  • Rewards, currency, XP, or progress update correctly.
  • The next objective is visible after each loop.
  • Social features are visible early when relevant.
  • Monetization prompts are optional and do not interrupt first-session flow.
  • Server-side systems own valuable state.
  • No obvious frame drops or runaway instance/script growth.
  • get_console_output has no new errors.

MCP Tools To Use

  • character_navigation for movement and route checks.
  • user_keyboard_input and user_mouse_input for controls and UI.
  • screen_capture for visual verification.
  • get_console_output for errors and warnings.
  • inspect_instance or execute_luau for state checks after interaction.

Report Format

Return:

  • What was tested.
  • Evidence gathered, including screenshots or console results when available.
  • Pass/fail by area.
  • Bugs or risks ranked by player impact.
  • Recommended next verification step.

Do not mark roadmap items complete without human approval, even after a passing playtest.

Next

Send any bug to roblox-debugging-bugfix and any performance issue to roblox-performance-optimization. If the slice passes, mark it in roblox-triage / ROADMAP.md and prepare the build with roblox-release-operations.

Comments

Markdown supported