API Testing
Audience
Developers, QA engineers, support engineers, security engineers, solution architects, and implementation partners.
Reference Content
This page records source-verified Workforce Scheduling API behavior and boundaries.
Summary
No dedicated Attendance Service unit/integration test project and no frontend automated shift-management test were found. Existing executable evidence consists of scripted API smoke, parity, backfill, gateway, and cutover checks.
Implemented scripted coverage
The smoke asset covers native shifts, weekly offs, policies, assignment creation, overlap rejection, effective-policy calculation, compatibility behavior, gateway routing, migration/backfill paths, parity, and cutover. The parity asset compares legacy and canonical shift/weekly-off output and optionally assignments. The go/no-go asset aggregates health, parity, ownership, backfill, and count checks.
Missing coverage
- Route-level authentication and authorization negative tests
- Header trust and cross-tenant isolation
- Every endpoint response/error shape
- Concurrent name and assignment-overlap writes
- Minimal-API binding edge cases
- DTO/OpenAPI snapshot contracts
- Unexpected-exception behavior
- Versioning/deprecation behavior
- Frontend shift and policy workflows
- Load, resilience, and recovery tests
Recommendation
Separate deterministic unit, database-backed integration, transport security, compatibility contract, gateway, and frontend suites. Existing scripts should remain transition evidence rather than the only regression layer.
Source References
microservices/scripts/smoke-attendance.ps1microservices/scripts/compare-attendance-shift-parity.ps1microservices/scripts/attendance-shift-cutover-go-no-go.ps1UI/salary-ui/apps/client-hrms-portal/src/pages/hr/PayrollFeaturePages.tsx
Related Articles
See Also
Keywords
- Workforce Scheduling API
- Shift endpoints
- Attendance policy API
Revision Information
- Status: Draft
- Last reviewed: 2026-07-20
- Next review: 2026-10-20