Roblox Validation And Qa

Overview

Every claim about a change must name the rung of the evidence ladder it actually reached, backed by output produced in the current session. "Code done" and "verified" are different states — the board's Testing lane exists precisely for the gap between them. This skill applies to any project on the house stack (Rojo + Wally + Jest Lua via DevPackages + the roblox-testing plugin + UI Labs).

When to use / When NOT to use

Use this skill when:

• You are about to claim a change works, passes, or is done.
• You are writing or running unit tests, playtest scenarios, or UI stories.
• You need to know which shipped features are actually playtested vs merely code-complete.

Do NOT use this skill for: