Skip to main content

Database Testing Guide

Audience​

Developers, QA and support engineers, data reviewers, implementation partners, solution architects, privacy reviewers and security reviewers.

Reference Content​

Summary​

Source includes Recruitment and Employee smoke coverage, but no complete automated cross-context onboarding/offboarding database suite was found. This page defines evidence-based test targets without providing operational database commands.

Existing evidence​

The Recruitment smoke script covers offer actions, onboarding movement/completion, candidate Joined state, outbox evidence, compatibility behavior, Employee integration and joining reports. The Employee smoke script covers Employee Service behavior. No equivalent offboarding persistence smoke suite was found.

Required scenarios​

  • Tenant isolation for every repository, including explicit filter bypass paths.
  • Candidate/Offer/Employee child cascade behavior and logical-reference validation.
  • Duplicate completion, approval/rejection, rollback and access-revocation races.
  • Employee commit followed by Recruitment failure, with reconciliation assertion.
  • Consumer redelivery, out-of-order events and unique processed-event behavior.
  • Compatibility versus extracted route selection with no accidental cross-store assumption.
  • Exit approval with blocking assets to confirm the current missing gate.
  • Notification failure after local lifecycle commit.
  • Migration upgrade from each supported release and compatibility initializer idempotence.
  • Retention/cleanup behavior once policy is implemented.

Isolation and safety​

Use disposable test stores, synthetic non-personal data and per-test tenant boundaries. Database-dependent scripts were not executed during this documentation epic.

Exit criteria​

Passing tests must prove local state, evidence records and delivery intent separately. A single successful API response is insufficient proof of cross-context completion.

Requires confirmation​

Unless explicitly confirmed above, production migration governance, rollback, reconciliation, retention, privacy, performance, concurrency and operational ownership require confirmation.

Source References​

  • microservices/scripts/smoke-recruitment.ps1
  • microservices/scripts/smoke-employee.ps1

See Also​

Keywords​

  • Onboarding database
  • Offboarding database
  • Lifecycle persistence

Revision Information​

  • Status: Draft
  • Last reviewed: 2026-07-20
  • Review cycle: Quarterly