test.failed

A test failed under jadpo test, or among a package's own tests under jadpo package check.

Area 14, Tools; not declinable; the next step is usually the agent's.

Why Jadpo refuses it

A test says what the code should do, so one that fails means the code and the test disagree. The run fails, exiting 1, so CI and a coding agent never read a failed run as a pass. Its screen reports each failure under its own rule, such as test.assertion_failed, with the values in the assertion and the command that reruns it; test.failed is the run's own, in --json's diagnostics, beside each test's report in data.tests. Jadpo doesn't decide which side is wrong: that is what the code is for.

What it looks like

A project whose library says when a todo is overdue, with one test:

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)}

A new test says a todo is overdue at its due time, where the code says only after it. The output below was copied from a run rather than checked, since each run's order seed is chosen at random:

cat >> domains/planning/libraries/due_dates.test.jadpo <<'EOF2'test "a todo is overdue once its due time comes" {    var due: DueAt = "2026-01-15T12:00:00Z"    var now: DueAt = "2026-01-15T12:00:00Z"    assert due_dates.is_overdue(due, now)}EOF2jadpo test

FAIL  a todo is overdue once its due time comes --> domains/planning/libraries/due_dates.test.jadpo:12  assert due_dates.is_overdue(due, now)         |                    |    |         false                |    "2026-01-15T12:00:00Z"                              "2026-01-15T12:00:00Z"  rule: test.assertion_failed  rerun: jadpo test domains/planning/libraries/due_dates.test.jadpo:12 --seed 97309test failed: 1 failed, 1 passed, 2 pure tests

With --json, the same run's diagnostics hold test.failed: "1 of 2 tests failed", whose next step is "Fix each failure, then run jadpo test --failed", marked agent. (agent) at the end of the next: line means your coding agent can make the fix itself.

How to fix it

The question is which is right, the test or the code.

If the code is right, and a todo is overdue only after its due time, correct the test to say so:

test "a todo is overdue once its due time has passed" {    var due: DueAt = "2026-01-15T12:00:00Z"    var now: DueAt = "2026-01-15T12:00:01Z"    assert due_dates.is_overdue(due, now)}

Then rerun what failed:

jadpo test --failed

Both tests pass.

If the test is right, and a todo is overdue from its due time on, change the code:

library due_dates {    ...    function is_overdue(due: DueAt, now: DueAt) -> Overdue {        return Overdue(due <= now)    }}

jadpo test --failed then passes, and every reminder that checks is_overdue goes out at the due time rather than after it.

Related

• jadpo test
• Running tests
• Writing a test