Testing Architecture

Summary

The strongest verified automated lifecycle evidence is script-based Recruitment smoke coverage, supplemented by Employee smoke coverage. Dedicated onboarding/offboarding unit, integration, architecture, exit-flow, and frontend component test suites were not found in the inspected source.

Audience

Developers, QA, support, and solution architects assessing change risk.

Verified test flow

Coverage matrix

Layer	Evidence	Boundary
Recruitment lifecycle smoke	Offer, acceptance idempotence, onboarding move/status/completion, candidate status, events, compatibility, reports	Script-based end-to-end checks
Employee smoke	Employee profile and lifecycle integration	Separate service script
Domain unit tests	No dedicated relevant project found	Missing evidence
Persistence integration tests	No dedicated relevant project found	Missing evidence
Gateway dual-path contract tests	No dedicated suite found	Missing evidence
Exit/offboarding automation	No dedicated test found	Missing evidence
Frontend component tests	No relevant tests found	Missing evidence
Security and tenant isolation	No dedicated lifecycle suite found	Missing evidence

Recommended seams

The layered Recruitment code exposes useful seams at repository, tenant-context, audit/timeline, employee gateway, workflow gateway, unit-of-work, and message transport boundaries. Recommended coverage should exercise domain transitions independently, persistence tenant filters, outbox atomicity, Employee failure/retry behavior, compatibility side-effect parity, direct-service authorization, and monolith exit partial-failure handling.

No commands, environments, hosts, ports, test identifiers, or credentials are reproduced here. Epic 14.3 will document API contracts separately.

Requires confirmation

• Which smoke suites are mandatory release gates and in which environments.
• Test data cleanup and tenant isolation strategy.
• Required parity matrix before Recruitment compatibility cutover.
• Ownership for exit/offboarding and frontend automated coverage.

Source References

• microservices/scripts/smoke-recruitment.ps1
• microservices/scripts/smoke-employee.ps1
• microservices/src/recruitment-service/Application/Commands/OnboardingCommands.cs
• microservices/src/recruitment-service/Infrastructure/RecruitmentDbContext.cs
• Controllers/HrOperationsController.cs

Related Articles

• Commands, queries, and validation
• Compatibility and transition
• Authentication and tenant context

See Also

• Logging and observability
• Technical limitations

Keywords

• Smoke testing
• Contract testing
• Test coverage gap

Revision Information

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