test(mutation): mutate masking.py live (PII redaction)#110
Closed
brownjuly2003-code wants to merge 1 commit into
Closed
test(mutation): mutate masking.py live (PII redaction)#110brownjuly2003-code wants to merge 1 commit into
brownjuly2003-code wants to merge 1 commit into
Conversation
Extend the live mutation gate to src/serving/masking.py, the second module-clean serving surface (imports only hashlib / pathlib / sqlglot / yaml, no duckdb). Same pattern as sql_guard: mutated as a top-level `serving` package against a narrow duckdb-free test (tests/unit/test_masking_mutation.py) that pins every redaction strategy (full / hash / partial / passthrough / None) and every _partial_mask shape (email / phone / address / multi-word / single word), so a surviving mutant -- a cleartext-PII leak -- dies. threshold 0.80: the narrow test scores ~0.84 in a Linux mutmut run; masking is a much larger surface than sql_guard (config loading + every strategy), with more equivalent config-init mutants, so 0.80 catches redaction-logic regressions without chasing those. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
DORA Metrics
|
Owner
Author
|
Closing: masking mutates fine under direct mutmut (183 mutants, 153 killed in a Linux venv) but the real mutation_report runner only sees init covered on CI (mutate_only_covered_lines attributes 0 coverage to the redaction methods through the test fixture), so the gate scores 0% and would break the weekly job. Deferring until the coverage-attribution gap in the runner workspace is understood; sql_guard (PR #109) stands as the proven pattern. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Second module-clean serving surface added to the live mutation gate (after sql_guard).
masking.pyimports only hashlib/pathlib/sqlglot/yaml — mutated as a top-levelservingpackage against a narrow duckdb-free test pinning every redaction strategy and_partial_maskshape. A surviving mutant is a cleartext-PII leak.Verified via
mutation.ymlworkflow_dispatch (Python 3.11): masking scores ~0.84 (threshold 0.80). The remaining serving modules (query/auth) stay declared-only until each gets a duckdb-free test.🤖 Generated with Claude Code