QUALITY ASSURANCE • TRUE CARE SYSTEM
Test Automation
Use automation to improve repeatability, speed, coverage, and release confidence.
Protected-data and QA evidence notice
QA artifacts may contain workforce identity, Provider configuration, PHI, GPS, visit, payroll, billing, audit, or integration evidence. Public documentation and shared test evidence must use synthetic, demonstration, or properly redacted information. Never place production passwords, tokens, full SSNs, bank account numbers, or unnecessary PHI in screenshots, tickets, automated test output, or repositories.
Purpose
Test Automation improves repeatability and release confidence for stable, high-value workflows. Automation complements—not replaces—manual exploratory, usability, compliance, and risk-based testing.
Automation Layers
| Layer | Recommended coverage |
|---|---|
| Unit tests | Calculations, parsers, validation, mapping, status transitions, utilities. |
| Service tests | Provider scoping, business rules, authorization, and database interactions. |
| API tests | Authentication, roles, validation, status codes, isolation, idempotency, failure handling. |
| Integration tests | Schedule-to-Visit, Visit-to-Payroll, Visit-to-Billing, Billing-to-Sandata, application-to-audit. |
| UI tests | Critical user journeys, navigation, forms, filters, save behavior, error and empty states. |
| Mobile tests | Login, permissions, calendar, check-in/out, GPS, notes, alerts, shift coverage. |
| Security tests | Unauthorized routes, identifier tampering, cross-tenant access, unsafe input, file upload. |
| Release smoke | Small stable set that confirms deployment health. |
Automation Design Rules
- Use deterministic data and avoid production records.
- Keep Provider, role, environment, and expected state explicit.
- Do not hide failures with broad retries.
- Make tests independent and safe to re-run.
- Capture useful failure evidence without secrets or PHI.
- Treat flaky tests as quality issues.