test.no_tests
A jadpo test command found no test to run: the project has none, or none matches the path, line, name, kind or --failed it gives.
Area 14, Tools; not declinable; the next step is usually the agent's.
Why Jadpo refuses it
A run of no tests would pass, and "tested: 0 passed" reads like a green
run. A misspelt --name, a file that holds no test, or --failed
before any run would then look like success while nothing was checked.
So a jadpo test that selects nothing fails, and says what the
selection left out.
What it looks like
A project with one test file:
domains/planning/libraries/due_dates.test.jadpo:
use planning/types { DueAt }test "a todo due yesterday is overdue" { var due: DueAt = "2026-01-14T12:00:00Z" var now: DueAt = "2026-01-15T12:00:00Z" assert due_dates.is_overdue(due, now)}
No test's name has the text --name gives:
jadpo test --name tomorrow error No test's name contains tomorrow
- reason
- The one test's name doesn't contain this text.
- next
- Check the spelling, or leave out
--nameto run every test (agent) - rule
- test.
no_ tests - help
- https://jadpo.
dev/docs/errors/test. no_ tests
(agent) at the end of the next: line means your coding agent can make the fix itself.
--failed before any run has no failures to rerun:
jadpo test --failederror There's no last run to rerun
- reason
jadpo testkeeps the failures of each run inbuild/test/last-run.json, and there isn't one yet.- next
- Run
jadpo testfirst, thenjadpo test --failed(agent) - rule
- test.
no_ tests - help
- https://jadpo.
dev/docs/errors/test. no_ tests
A path, a line or a --kind that holds no test is refused the same
way, with where the tests are.
How to fix it
If you meant some of the tests, give text their names hold:
jadpo test --name overdueThe test whose name holds overdue runs.
If you meant every test, leave the selection out:
jadpo testEvery test in the project runs, and its failures are kept for
--failed.
Related
Markdown for agents: /docs/errors/test.no_tests.md.Built from Jadpo main at aee2e8f.