Debugging

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

Start with one failing file


glubean run tests/users.test.ts --verbose

--verbose prints trace lines, assertion details, logs, metrics, and compact request/response body previews to the console.

Narrow the scope


glubean run tests/users.test.ts --filter "create-user"
glubean run tests/users.test.ts --pick "edge,invalid"
glubean run --only-id get-user-42
glubean run --only-id search-row --row 3

--filter matches test name or ID. --pick selects specific test.pick() examples. --only-id selects exact expanded IDs, and --row isolates one test.each row when paired with a single --only-id.

Get more detail on disk


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

--emit-full-trace writes full HTTP headers and bodies into trace files under .glubean/traces/.

Attach a debugger


glubean run tests/users.test.ts --inspect-brk

This pauses execution until a debugger (Chrome DevTools or VS Code) attaches. In VS Code/Cursor, you can also use Debug Test from the gutter or Test Explorer.

Check result files

After a run, inspect .glubean/last-run.result.json for structured output. See Result Files for the format.

Rerun the last failures


glubean run --rerun-failed

This reads .glubean/last-run.result.json and runs only the failed tests from the previous functional run.