QUALITY ASSURANCE • TRUE CARE SYSTEM
Regression Testing
Confirm that a focused change does not damage existing production workflows.
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
Regression testing confirms that a focused change does not damage other workflows that depend on the same records, services, permissions, or calculations.
Dependency-Based Regression
| Changed area | Required related checks |
|---|---|
| Schedule | Mobile calendar, backup alerts, shift ownership, Visit Maintenance, authorization, reports, payroll, billing, HIPAA logs. |
| Mobile check-in/out | Visit creation, duplicate prevention, GPS, call log, actual time, units, payroll hours, billing readiness, Sandata payload. |
| Individual | Authorization, scheduling, reports, Mobile EVV, billing readiness, PHI access history, Provider isolation. |
| Employee | Role access, schedule assignment, Mobile login, payroll rate, DSP readiness, audit logs, inactive employee exclusion. |
| Billing | Visit Maintenance decisions, units, rates, batch creation, Sandata sequence, submission history, PromISe worksheet. |
| HIPAA/Audit | Normal application behavior, actor/target identity, Provider scope, IP/device capture, performance, export. |
Regression Rules
- Protect all functionality that was already passing before the change.
- Compare the changed file with the last known good version when a regression appears.
- Test both intended and failure paths.
- Use production-like structures without exposing real PHI.
- Re-run high-risk regression after conflict resolution or dependency updates.