audit-tests

Auditing event sourcing test coverage involves systematically evaluating serialization/deserialization tests, aggregate replay scenarios, and projection rebuilds to identify real failure-mode gaps. This process surfaces brittle coverage and validates event version migrations before production.

Testing GEDCOM import export equivalence requires checking import → export → re-import cycles to detect data loss. You validate Unicode and non-standard tag handling to ensure GEDCOM processing maintains data fidelity across complex genealogical structures.

Yes, the test audit process works with Go and Svelte repositories by focusing on internal/ test packages, event store code, internal/gedcom and internal/domain modules, and API endpoint tests to find missing or brittle coverage in those specific structures.

You verify API contract validation and pagination by checking API responses against OpenAPI expectations and confirming database parity across SQLite and PostgreSQL. This ensures API responses and pagination conform to specifications across both database backends.

Integration tests report high coverage but miss real world failures because they often lack cross-feature lifecycle scenarios like create → update → query → delete. A systematic test audit identifies missing boundary tests, fragile assertions, and incomplete cross-feature integration flows.

From a test quality audit you get a scored audit report, prioritized findings with evidence, up to five issue-ready tickets, and manual verification steps. This actionable output surfaces real failure-mode risks hidden by high coverage metrics.