Skip to main content

Attendance Smoke Testing

Summary​

The Attendance smoke script exercises core Attendance, Time Office, gateway, outbox-adjacent, snapshot, backfill, and compatibility behaviors in isolated test conditions.

Audience​

  • QA engineers, backend developers, release engineers, and DevOps/SRE

Prerequisites​

Use an approved disposable environment with synthetic tenant/employee data and isolated databases. Review script parameters and evidence destinations without publishing configuration values.

Procedure​

  1. Establish service/process health and safe test context.
  2. Exercise Attendance save, pending, approval/rejection, summary, punch, reopen and snapshot behavior.
  3. Exercise Shift, weekly-off, policy, assignment, audit/timeline and effective-policy behavior.
  4. Exercise compatibility, shadow/direct and gateway route expectations.
  5. Exercise supported backfill dry-run/apply/idempotency/resume validation where prerequisites are isolated.
  6. Retain pass/fail output, correlation context and sanitized logs.

Validation or Expected Result​

Every assertion passes; no real employee/customer data is used; isolated resources are cleaned by the script’s supported lifecycle; failures identify the affected capability and stop go/no-go approval.

Troubleshooting​

Classify failure as startup/dependency, Attendance domain, Time Office, gateway/routing, backfill/schema, or cleanup. Escalate with sanitized output; do not rerun destructive portions against shared or production infrastructure.

Source References​

  • microservices/scripts/smoke-attendance.ps1
  • microservices/src/attendance-service/Program.cs

See Also​

Keywords​

  • Attendance operations
  • Support
  • Reliability

Revision Information​

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