Skip to main content

Database Testing

Audience​

Developers, database engineers, QA engineers, support engineers, security engineers, solution architects, and implementation partners.

Reference Content​

This page records source-verified Workforce Scheduling persistence behavior and boundaries.

Summary​

No dedicated mapping, repository, migration, or persistence integration test project was found for Attendance or Leave. Existing evidence is script- and backfill-validator-based.

Implemented evidence​

The Attendance smoke asset exercises canonical persistence through APIs, compatibility behavior, assignments, effective resolution, backfill, parity, and cutover. The backfill validator compares source/target counts and mapped attributes and detects assignment mismatches. Separate parity and cutover assets compare legacy and canonical state.

Missing coverage​

  • Model mapping and snapshot assertions
  • Migration-upgrade tests from supported prior states
  • Repository tests against the real provider
  • Query-filter and privileged-bypass isolation tests
  • Unique-constraint and cascade tests
  • Multi-save partial-failure tests
  • Concurrent duplicate and overlap tests
  • Seeder idempotency tests
  • Retention and cleanup tests
  • Backup/restore and performance tests

Classification​

Database testing is Partial and transition-focused.

Source References​

  • microservices/scripts/smoke-attendance.ps1
  • microservices/scripts/compare-attendance-shift-parity.ps1
  • microservices/scripts/attendance-shift-cutover-go-no-go.ps1
  • microservices/src/attendance-service/Backfill/ShiftPolicyBackfillValidator.cs

See Also​

Keywords​

  • Workforce Scheduling database
  • Shift persistence
  • Attendance policy storage

Revision Information​

  • Status: Draft
  • Last reviewed: 2026-07-20
  • Next review: 2026-10-20