Troubleshoot Glade
Troubleshooting
Start with the symptom you recognize. Confirm project context before changing Apex source or local data.
Glade cannot find my project
Confirm the shell is inside the Salesforce DX project, then initialize and recheck the project-aware environment:
test -f sfdx-project.json
glade init --project . --yes
glade doctor --project .If the first command fails, move to the directory that owns sfdx-project.json. Continue with the first local check.
glade doctor fails
Read the first failed status row. A project failure means the working directory or --project path is wrong. A parser or toolchain failure is an installation problem. Re-run glade version, then follow Installation.
A test is not discovered
Run the project test inventory before adding a class selector:
glade test --project .
glade test --project . --class <YourTestClass>Use a class that exists in the active package directories. See Run one Apex test.
Local and Salesforce results differ
Record the exact Glade command and result, then check the capability in What runs locally. Hosted services and exact production behavior remain Salesforce validation. Report a reproducible mismatch with the smallest source, metadata, and data fixture that shows it.
VS Code cannot find the Glade binary
Run glade editor doctor vscode in a terminal where glade version succeeds. Restart VS Code after changing PATH. See Use Glade in VS Code.
A breakpoint is not hit
First prove the selected test runs locally. Then confirm the launch points at the same project and class. Follow Debug Apex with breakpoints.
A local sf target is missing
Start and authorize the named local target again. The isolated-shell and cleanup rules are in Set up a Glade org and import data with sf.
A plugin is not restored in CI
Commit the plugin lock file, use the same Glade version locally and in CI, and follow Plugin lock files and CI. Plugins are separate executables; a base Glade install does not restore them implicitly.
Still blocked
Include glade version, glade doctor --project ., the exact command, stable error code, and the smallest reproducible project state in a GitHub issue.