Checks that actually catch what they should
Testing confirms each rule fires when it should and stays silent when it shouldn't, rather than assuming the logic works as written.
What's included
What gets tested
- Each programmed check run against known-good data to confirm it stays silent when it should
- Each check run against known-bad data to confirm it fires with the correct query text
- Boundary and edge-case values tested at the limits of each range or format rule, not just the middle of the range
- Cross-form and cross-visit checks tested with realistic multi-visit mock-subject scenarios
- Round-one findings logged and fixed, then confirmed closed in a dedicated round-two retest
Paired with SAS checks
Runs alongside SAS check UAT so both layers of validation are confirmed together before launch.
← Back to Data Management
More in Database Build