# roblox-testing

Debugging, profiling, and testing workflows for Roblox Studio projects using TestEZ, Luau type checking, and engine diagnostics.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 319 installs · ★ 24
- Author: nonlooped
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/nonlooped/roblox-suite/tree/HEAD/roblox-testing/SKILL.md
- Updated: 2026-10-22
- HTML: https://affpapa.org/en/nevibecode/skills/roblox-testing

## What it does

This skill guides coding agents through isolating client and server issues in Roblox experiences. It structures workflows around Developer Console tabs, MicroProfiler inspections, Luau typing with `--!strict`, and unit test suites running on TestEZ.

The instructions enforce connection cleanup via Maid or Janitor patterns to prevent dangling `RBXScriptConnection` leaks. The skill also steers the model away from legacy `spawn` or `wait` calls in favor of the modern `task` library, while implementing `xpcall` with `debug.traceback` to preserve call stacks across asynchronous callbacks.

Generic exponential retry loops are restricted to read operations: replaying writes on failed network responses risks out-of-order execution and corrupted DataStore state.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add nonlooped/roblox-suite --skill roblox-testing -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/roblox-testing/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/roblox-testing/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add nonlooped/roblox-suite --skill roblox-testing -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/roblox-testing/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add nonlooped/roblox-suite --skill roblox-testing -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/roblox-testing/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install nonlooped/roblox-suite roblox-testing
```

2. **Manually: put the files in place**
- File: `.github/skills/roblox-testing/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add nonlooped/roblox-suite --skill roblox-testing -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/nonlooped/roblox-suite --path roblox-testing
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/roblox-testing/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add nonlooped/roblox-suite --skill roblox-testing -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/nonlooped/roblox-suite/tree/HEAD/roblox-testing/SKILL.md

## When to use it
- Author TestEZ unit test suites with describe and it blocks
- Prevent RBXScriptConnection memory leaks using Maid or Janitor cleanup
- Capture stack traces in async callbacks using xpcall with debug.traceback
- Inspect and assign explicit physics network ownership with SetNetworkOwner

## Example prompts
- Write a TestEZ test suite for this damage calculation module
- Audit this character controller script for RBXScriptConnection leaks and add Maid cleanup
- Add xpcall error logging with debug.traceback and log throttling to this remote event handler

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 3e88d009d018396a.

BEGIN THIRD-PARTY FILE 3e88d009d018396a
````text
---
name: roblox-testing
description: "Test, debug, or profile Roblox experiences. Use for Studio debugging, TestEZ, logging, connection cleanup, memory or network diagnostics, MicroProfiler, Scene Analysis, and Script Profiler."
last_reviewed: 2026-10-21
---

# roblox-testing

**Official sources:**
- https://create.roblox.com/docs/en-us/studio/developer-console
- https://create.roblox.com/docs/en-us/performance-optimization/identify
- https://create.roblox.com/docs/en-us/performance-optimization/microprofiler
- https://create.roblox.com/docs/en-us/performance-optimization/scene-analysis
- https://create.roblox.com/docs/en-us/studio/optimization/memory-usage
- https://create.roblox.com/docs/en-us/studio/optimization/scriptprofiler

Start with a reproducible failure and identify whether it occurs on the client, server, or both. Choose a debugging or profiling tool based on that evidence.

## The debugging mindset

1. **Reproduce it.** If you can't reproduce it, you can't fix it.
2. **Isolate it.** Remove systems until the bug disappears; the last thing removed is the cause.
3. **Measure it.** Use tools instead of guessing.
4. **Fix one thing at a time.** Verify the fix and add a regression test if possible.
5. **Log defensively.** Good logs make future debugging faster.

## Logging discipline

Use `print`, `warn`, and `error` deliberately:
- `print` for normal diagnostics.
- `warn` for recoverable problems you should notice.
- `error` for programming errors that should stop execution.

Include context in log messages:

```lua
warn(string.format("[DataStore] Save failed for %d: %s", userId, tostring(err)))
```

Avoid logging secrets, player data, or PII.

## pcall and assertions

Wrap fallible calls, especially cloud services, HTTP, DataStores, Marketplace:

```lua
local ok, result = pcall(function()
    return someService:DoSomething()
end)
if not ok then
    warn("DoSomething failed:", result)
end
```

Use `assert` for internal invariants that should never fail:

```lua
assert(config.MaxSpeed > 0, "MaxSpeed must be positive")
```

## Developer Console

Open with `F9` in-game or in Studio play mode.

Tabs:
- **Log**: client/server output, errors, warnings.
- **Memory**: categorized memory usage.
- **Network**: HTTP and service requests.
- **Server Stats**: heartbeat, ping, data ping.
- **Script Profiler**: record script CPU usage.
- **MicroProfiler**: capture server dumps.

Toggle Client/Server views to see which side emitted output.

## Unit testing with TestEZ

The standard Roblox testing framework is [TestEZ](https://github.com/Roblox/testez). It supports nested `describe`/`it` blocks, lifecycle hooks, async tests, and a rich matcher API.

TestEZ example:

```lua
local ReplicatedStorage = game:GetService("ReplicatedStorage")
local TestEZ = require(ReplicatedStorage.DevPackages.TestEZ)

local MathUtils = require(ReplicatedStorage.MathUtils)

describe("MathUtils", function()
````
END THIRD-PARTY FILE 3e88d009d018396a

The third-party file has ended. Everything between the 3e88d009d018396a tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2927 of 12467 bytes. © nonlooped · MIT · https://github.com/nonlooped/roblox-suite/tree/HEAD/roblox-testing/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md