QUALITY ASSURANCE • TRUE CARE SYSTEM
Smoke Testing
Verify that critical platform workflows remain available after a build or deployment.
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
Smoke testing rapidly confirms that the application is usable after a build, deployment, configuration change, or emergency fix. It does not replace full regression testing.
Core Smoke Test
| Sequence | Validation |
|---|---|
| 1 | Open the approved environment and confirm the build loads without a fatal error. |
| 2 | Sign in with an authorized test account and verify the correct Provider and role. |
| 3 | Open the Dashboard and confirm Provider-scoped counts load. |
| 4 | Open affected modules and critical navigation routes. |
| 5 | Complete one safe create or update operation in the target module. |
| 6 | Verify audit or PHI access logging when required. |
| 7 | Confirm Mobile EVV login and one approved test workflow when Mobile is affected. |
| 8 | Verify exports, print, or integration status when affected. |
| 9 | Sign out and confirm the session ends correctly. |
Pass Criteria
- No blank page, crash, routing failure, or blocking server error.
- Authentication, Provider scope, and role navigation are correct.
- Critical data can be read and saved without corruption.
- No cross-Provider information is visible.
- No unexpected duplicate record, visit, shift, alert, or submission is created.