Verify research SQL and read-only permissions in isolated PostgreSQL CI
This commit is contained in:
+10
-1
@@ -75,4 +75,13 @@ given name, family name and suffix; null abstracts/dates remain null. Publicatio
|
||||
status comes from the latest observed decision, using decision date and ID as
|
||||
tie-breakers, and stays unknown when no decision exists. Unit checks cover
|
||||
author shapes, bound user values and schema qualification; real PostgreSQL
|
||||
integration checks remain pending the migration.
|
||||
corpus checks remain pending the migration.
|
||||
|
||||
The existing `deploy/check-schema.sh` also loads the synthetic fixture in
|
||||
`internal/research/testdata/corpus.sql` inside its disposable PostgreSQL
|
||||
container (`--network none`, no host port). The research test process receives a
|
||||
separate SELECT-only fixture role via `RESEARCH_TEST_DATABASE_URL`. These
|
||||
integration checks execute real SQL for filtering, stable paging, nullable
|
||||
content, source/tag/identifier joins, latest decision tie-breakers, permission
|
||||
denial and SQL-backed HTTP routes. They never connect to the shared migration
|
||||
instance and do not establish full-corpus performance or live-data correctness.
|
||||
|
||||
Reference in New Issue
Block a user