Guides

Troubleshooting

Find out what went wrong when a Testlane command fails, from the error it printed or the symptom you see, and how to fix it.

When a command fails, this page helps you find out why and fix it. Testlane prints one error(E_…) line for every failure, often with a hint: that names the fix, and exits with a code of its own, so start from the error code when you have one, or from the symptom when you don't.

Start with doctor

doctor checks your tools, your config directory and every project you've set up, in one go:

testlane doctor
OK   git version: git 2.50.1
OK   gh (github cli): authenticated
OK   config dir: /home/you/.testlane
OK   state dir: /home/you/.local/state/testlane
OK   project my-project: config: schema-valid
OK   project my-project: repo: bare repo at /home/you/dev/testlane/my-project/repo
OK   project my-project: fetch refspec: remote.origin.fetch configured

Each line is one check, marked OK, WARN or FAIL. OK needs nothing from you. WARN means the project still works, but something is limited, like pull request titles and push-back without gh. FAIL means something is broken, and doctor exits with 1 when any check fails, so you can run it in CI too.

It checks your git version (2.38 or later), whether gh is installed and signed in, that the config directory can be read and the state directory written, and whether any lock was left behind. For each project, it checks the project file, the clone and its fetch refspec, the editor, core.hooksPath, any command that has the name of a built-in verb, whether its workspaces still match what's on disk, and the repository's .testlane.toml, if it ships one.

Errors by code

Each error prints one line on stderr, an optional hint: and exits with its code. Exit codes is the full reference.

Common situations

These come up often, and most of them don't have an error code of their own:

Where to go next

Here's where to go from here:

Copyright © 2026