Debugging

Use the CLI when you want a repeatable terminal-first debug loop.

Start with one failing target

glubean run ./tests/users.test.ts --verbose --emit-full-trace

This gives you both:

• detailed terminal output
• full trace artifacts on disk

Narrow the scope

glubean run ./tests/users.test.ts --filter "create-user"
glubean run ./tests/users.test.ts --pick "edge,invalid"

Use --filter for a test name or ID and --pick for named test.pick() examples.

Step through in the editor

In VS Code/Cursor, run Debug Test from gutter/Test Explorer to attach the runtime inspector and step through your test.

Trust artifacts, not memory

Use Reference: Artifacts as the source of truth for where traces/results/metadata live.

Next

• Traces & Files
• Extension Debugging