Diagnostics

When something is not working, the Diagnose command and the tips below help you find the root cause quickly.

Glubean: Diagnose

Run Glubean: Diagnose from the Command Palette. The extension checks four areas and writes results to the Output Channel:

1. Runtime — Node.js version, CLI installation status and version.
2. Project status — package.json presence, @glubean/sdk dependency.
3. Test discovery — how many test files and test cases were found.
4. Current file — whether the active file is a test file, its parse result.

If problems are detected, the output includes specific suggestions, such as initializing the project with npx glubean init, installing project dependencies, or updating the package version used by the project.

Common problems

Tests are not discovered

• Check the file extension. The extension’s Test Explorer recognizes .test.ts, .test.js, and .test.mjs files.
• Check the export. Tests must be exported: export const myTest = test(...).
• Check glubean.autoDiscover. If set to false, tests are only parsed when you open the file.

Contract and workflow files are source-of-truth assets, but they are not the same editor discovery surface as raw test() files. Run them through MCP, the CLI, package scripts, or CI when you want the full project check.

Play button does not appear

• The file must match *.test.ts, *.test.js, or *.test.mjs.
• Ensure the extension is installed and activated (check the Extensions sidebar).

Scratch Mode type errors

Scratch Mode skips TypeScript compilation. Use .test.js (not .test.ts) for scratch files to avoid type-checking issues.

Environment variables not loaded

• Verify the .env file is in the project root (same level as package.json).
• Check which environment is selected in the status bar — it might be pointing to a different .env file.
• Secret variables must be in .env.secrets (or the matching .env.{name}.secrets), not the regular .env file.

Result Viewer does not open

• Extension history is stored in .glubean/results/; full CLI/project runs also write .glubean/last-run.result.json. If both are missing, there is nothing to show yet.
• Check that the run actually completed (look at the Test Results panel for errors).

CLI status bar

The status bar shows the Glubean CLI installation status (only visible in Glubean projects):

The extension should work from the project and npx path. You do not need to install the Glubean CLI globally.

What’s next?

• Commands & Settings — Full command and configuration reference
• Quick Start — Start fresh if your setup is broken