Stable readiness prerequisites — test coverage sufficiency and evidence (tests ↔ behaviours mapping + test result statement)

[albertoramosmonagas]

To progress the Population Density Data API towards a Stable (v1.0) release, we need to address two CAMARA stable-readiness prerequisites currently marked as “under review”:

1. Enhanced test documentation (mapping tests → behaviours)
   We need a clear mapping between the repository’s tests and the expected API behaviours (feature-level outcomes). The goal is to make it explicit what is covered, what is not, and where gaps exist (e.g., sync vs async flows, error cases, privacy/k-anonymity behaviour, partial area support, etc.).

2. Test Result Statement
   We need an explicit statement (with traceable evidence) that at least one member has executed the repository’s tests successfully against a real implementation.

Objective of this discussion

• Align within the working group on whether the current test suite and documentation are sufficient for Stable readiness.
• Identify any missing behavioural coverage and agree on a minimal, pragmatic uplift plan to close gaps before proposing v1.0.
• Agree what constitutes acceptable “evidence” for the test result statement (e.g., CI logs, implementation environment notes, reproducibility criteria, version/tag, date, and maintainer sign-off).

Proposed outcomes

• Decision: “Current coverage is sufficient” vs “Coverage uplift required”.
• Definition of Done for:
  • Tests ↔ behaviours mapping documentation
  • Test Result Statement (where it lives, what it includes, and who signs it)

Context
These items are intended to unblock the Stable (v1.0) track. This discussion is about test adequacy and documentation/evidence, not about changing the API scope.

CC: @camaraproject/population-density-data_codeowners