Skip to main content

Tests: internal/infra/pg

internal/infra/pg · 291 tests

Each test is named for the property it holds, and runs against a real deployment: there is no mock of the database and no arm that skips when it is absent. The sentence is the test's name read back; the name is what go test -run takes.

anchorlayout_qualification_test.go

anchorlimits_test.go

anchorplans_test.go

  • Anchor query plansTestAnchorQueryPlans. These are reproducible plan diagnostics, not production latency benchmarks.

artifactcontent_test.go

artifacterasure_test.go

artifactfailure_test.go

artifactprivileges_test.go

artifactstore_test.go

auditactivity_test.go

  • The ledger is counted by window bucket operation and projectTestTheLedgerIsCountedByWindowBucketOperationAndProject. The console's activity is the ledger counted, and counted exactly: this window against the one of the same length before it, cut into buckets aligned to the window's start, by operation busiest first and by project busiest first — and narrowed to one project when asked, with the instance's own operations kept out of the project ranking.

auditseal_test.go

chunkrecovery_test.go

citationstore_test.go

claimreplay_test.go

connectionslots_test.go

  • Connection exhaustion is recognised from the code and from the connect errorTestConnectionExhaustionIsRecognisedFromTheCodeAndFromTheConnectError. ── Connection exhaustion is recognised two ways ────────────────────────────────────────────── The condition arrives two ways and both have to be recognised.

correctionrefusal_test.go

correctionsource_test.go

embedding_live_test.go

embeddingbuild_test.go

embeddingcatchup_test.go

embeddingcutover_test.go

embeddingfailure_test.go

embeddinggeneration_test.go

embeddingownership_test.go

embeddingpartition_test.go

embeddingrefusal_test.go

embeddingsearch_test.go

entityembedding_test.go

entityembeddingfailure_test.go

entityinspection_test.go

entitynames_test.go

entitynamesfailure_test.go

entityrecovery_test.go

entityrecoveryfailure_test.go

erasure_test.go

extractionpin_test.go

extractionpinfailure_test.go

extractionpinreadfailure_test.go

factexpiry_test.go

factgeneration_test.go

facthistory_test.go

factreceipt_test.go

factreceiptfailure_test.go

factsupportconcurrency_test.go

factsupportrecovery_test.go

feedbackplans_test.go

feedbackstore_test.go

formationrecovery_test.go

generationfailure_test.go

generationrecovery_test.go

generationtemporal_test.go

ingestionbudget_test.go

ingestionprivileges_test.go

integrityrollback_test.go

knowledgeclock_test.go

messagewindow_test.go

observationadmission_test.go

operationalhealth_test.go

purgedentityrecovery_test.go

rebuildjob_test.go

rebuildjobfinish_test.go

rebuildstaleness_test.go

  • A rebuild says what it left behind and says nothing when it left nothingTestARebuildSaysWhatItLeftBehindAndSaysNothingWhenItLeftNothing. ── A rebuild says what it left behind ──────────────────────────────────────────────────────── A rebuild publishes a new interpretation and finishes.
  • A staleness read that cannot count refuses rather than reporting noneTestAStalenessReadThatCannotCountRefusesRatherThanReportingNone. When a table it counts is gone, the staleness read fails rather than reporting zero.

rebuildvisibility_test.go

recallevidence_test.go

recallplans_test.go

receiptsilence_test.go

recordassertion_test.go

recordcorrection_test.go

recordplans_test.go

recordretraction_test.go

recordstore_test.go

rejectedreplay_test.go

reportembedding_quality_test.go

reportembedding_test.go

reportembeddingfailure_test.go

reportfreshness_test.go

reportprovenance_test.go

reportwriter_test.go

  • A report says what wrote it and is rewritten when the writer changesTestAReportSaysWhatWroteItAndIsRewrittenWhenTheWriterChanges. ── A report carries what wrote it ──────────────────────────────────────────────────────────── A report is a model's prose written under a particular prompt, and until now nothing recorded which.

retractionfailure_test.go

retractionlifecycle_test.go

retryfingerprint_test.go

segmentstore_test.go

  • A segment is registered to every turn it covers and erasure reaches itTestASegmentIsRegisteredToEveryTurnItCoversAndErasureReachesIt. A segment is written with a registration per covered turn, in one transaction; a second segment over the same range is refused; a range whose turns moved is refused; and an erasure of the subject removes their segments through the registrations and leaves another subject's.

sharedevidence_test.go

subjectconcurrency_test.go

subjectfailure_test.go

subjectretention_test.go

subjectstore_test.go

vectorlayout_qualification_test.go

writepath_test.go