Development Seeding
Audience
Developers, QA and support engineers, data reviewers, implementation partners, solution architects, privacy reviewers and security reviewers.
Reference Content
Summary
Development seeders exist for Recruitment, Employee, Payroll, Leave and Asset; Notification has a default-template seeder. No Attendance development seeder was found. The compatibility initializer also populates foundational configuration/permissions.
Inventory
| Context | Source-backed mechanism | Lifecycle relevance |
|---|---|---|
| Recruitment | Development seeder | Recruitment demonstration data |
| Employee | Development seeder | Employee demonstration data |
| Payroll | Development seeder | Payroll configuration/profile support |
| Attendance | No development seeder found | Requires explicit test setup |
| Leave | Development seeder | Leave configuration/profile support |
| Asset | Development seeder | Asset demonstration data |
| Notification | Default-template seeder | Delivery templates |
| Compatibility | Schema initializer population | Foundation configuration and permissions |
Safety boundary
Seed values are intentionally excluded because they can expose internal assumptions or personal-looking data. Seeders and initializers were inspected but not executed.
Environment controls
Seeder invocation is application/environment dependent. Development-only intent must be enforced by startup configuration and deployment policy; file naming alone is not a production safeguard.
Test design
Automated database tests should create isolated, non-personal fixtures through approved test infrastructure and dispose of them through the same harness. Production databases must never be a seeding target.
Not proven
A single cross-context seed manifest, deterministic lifecycle scenario version, production guardrail test and seed rollback strategy were not found.
Requires confirmation
Unless explicitly confirmed above, production migration governance, rollback, reconciliation, retention, privacy, performance, concurrency and operational ownership require confirmation.
Source References
microservices/src/recruitment-service/Infrastructure/DevelopmentSeeder.csmicroservices/src/employee-service/Infrastructure/DevelopmentSeeder.csmicroservices/src/notification-service/Seed/DefaultTemplateSeeder.cs
Related Articles
See Also
Keywords
- Onboarding database
- Offboarding database
- Lifecycle persistence
Revision Information
- Status: Draft
- Last reviewed: 2026-07-20
- Review cycle: Quarterly