Troubleshooting
The common problems, and the fix for each.
Coverage
A workflow run is green, but nothing appears in verifAIed
The artifact name on GitHub does not match the repository's Artifact name setting. Compare the two; case matters. See Repository settings.
The tests panel on a function's page is empty
Almost always junit.xml is missing. In CI, the artifact has to contain the file at its root with that exact name, which means your test runner needs its JUnit option switched on. From the CLI, pass the file with --junit; it is not picked up by itself.
Hit counts are 0, or a branch shows “Needs attention”
The coverage report does not say which test ran which line. For Python, run pytest with --cov-context=test and write the report with coverage json --show-contexts, or set show_contexts = true under [tool.coverage.json]. TypeScript and JavaScript coverage has no per-test detail, so hit counts are always 0 there.
functions_matched comes back 0 when your agent uploads
The file paths your agent sent do not match the paths in the coverage report. They must be exactly the same. Both are relative to the directory the tests ran from.
Paths show the wrong folder in a monorepo
verifAIed shows every path from the root of the repository, for example backend/app/foo.py. The CLI works the folder out from git. An agent uploading from a sub-directory through the upload_local_coverage tool can pass path_prefix, for example backend, to set it.
Browser tests
“No recorder connected”
Recording and running from the web need the studio running on your machine. Start it in your repository and leave it running:
verifaied test studio
“The connected studio is on” another branch
The Run buttons are off because the studio is on a different branch from the page you are looking at, so a run would land on the wrong branch. The studio follows the branch checked out where it runs. Either check out this page's branch there, or click Open that branch → to go to the studio's branch.
“the connected studio is too old — restart it after upgrading verifaied”
The studio is running an older CLI that cannot do what the page asked. Upgrade the CLI the way you installed it, then stop the studio and start it again:
uv tool upgrade verifaied
With pipx, the command is pipx upgrade verifaied.
A recording will not start: @playwright/test “is older than 1.60”
Recording needs @playwright/test 1.60 or later in your repository. Upgrade it and start the recording again. Running tests you already have is not affected: verifaied test run works on any version.
“the reset command from .verifaied/config.toml failed”
An environment's reset command runs before each test. When it exits with an error the run stops, and no test runs against a state that was not reset. The message ends with the exit code and the command; run that command yourself to see why it fails. See Environments, variables and secrets.