test.database_unavailable

The tests that need a database couldn't run, because PostgreSQL for the tests couldn't be started or reached.

Area 14, Tooling; not declinable; the next step is usually the human's.

Why Jadpo refuses it

An action, route or schedule test runs against a real database, so with no server there is nothing for it to run on. Nothing in your project is wrong, and no test failed: telling a coding agent to fix the tests would send it after a problem that isn't in them. So the run stops once, before any test, and says so in one error rather than in each test that needed the database.

Jadpo doesn't step out of a sandbox or install anything by itself. What is allowed to run on your machine is yours to decide.

What it looks like

A project with tables and tests, run where PostgreSQL can't make shared memory, as inside some sandboxes. This output is copied rather than checked, since an ordinary machine never raises this error:

(human) at the end of the next: line tells your coding agent to stop and ask you which fix you want, because the choice is yours to make: it decides what may run on your machine and where. With --json this is the one diagnostic in the document, so an agent reading only the top level sees it. jadpo test --full gives everything PostgreSQL printed.

The other two forms differ in what they ask of you. On a machine with no PostgreSQL, the error is No PostgreSQL for the tests, and its next step is to install it. When JADPO_TEST_DATABASE_URL names a server that can't be used, the error is The PostgreSQL server for the tests can't be used, and its next step is to check that server. The address is never printed, since it may hold a password.

When some of the tests chosen need no database, an impact: line says that jadpo test --kind pure still runs them.

How to fix it

If a sandbox is in the way, run the tests outside it:

jadpo test

PostgreSQL can make its shared memory there, so the server starts and the tests run.

If you want the tests on a server of your own, name it:

JADPO_TEST_DATABASE_URL=postgresql://postgres@localhost:5432/postgres jadpo test

The tests' databases are made on that server, so jadpo test starts none.

If PostgreSQL isn't installed, install it, then check that its tools are on your PATH:

initdb --version

jadpo test starts its disposable server from those tools.

Your last run's failures are left as they were, so jadpo test --failed still reruns them.

Related

• The test database
• jadpo test