Structural assertions MUST be made from the state a schema has, for every dialect, and run by a driver.
Enforced (check): .github: cd commons/data && bun run verify — suite/assertions.test.ts: the structure a schema's state says is held on each dialect, by a driver and by one query that returns TAP lines, and what a database lacks or has otherwise is a failing line that names it
A difference between a database and the state MUST be a failing line that names what is wrong.
Enforced (check): .github: cd commons/data && bun run verify — suite/assertions.test.ts: the structure a schema's state says is held on each dialect, by a driver and by one query that returns TAP lines, and what a database lacks or has otherwise is a failing line that names it
Assertions MUST be written as pgTAP scripts and run by the pgTAP extension.
Enforced (check): .github: cd commons/data && bun run verify — suite/assertions.test.ts: rows are held in any order and compared as sets, a statement that must fail passes only where it is refused and changes nothing where it is not, and the query that gives TAP says a statement that must fail was skipped
TAP version 14 MUST be values, text and readable back.
Enforced (check): .github: cd commons/data && bun run verify — suite/assertions.test.ts: TAP is values that are written as TAP version 14 and read back, with a skipped test counted apart from a failure
rows and fails assertions of one's own MUST run in every dialect.
Enforced (check): .github: cd commons/data && bun run verify — suite/assertions.test.ts: the assertions are a pgTAP script that the pgTAP extension runs in PostgreSQL, giving the same results as the query and the driver