Skip to content

Add regression test for schema stale data and CI coverage enforcement #38

@jakebromberg

Description

@jakebromberg

The schema fix in #36 / PR #37 changed CREATE TABLE IF NOT EXISTS to DROP TABLE ... CASCADE + CREATE TABLE. A regression test is needed to prevent this from being reintroduced.

Additionally, CI should enforce a minimum coverage threshold to prevent coverage regressions.

Changes

  1. Add test_schema_clears_stale_data_on_rerun: inserts data, re-runs schema, verifies tables are empty
  2. Update CI test-postgres job to run all tests (unit + integration) with --cov-fail-under=80

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions