Loading content
Lightweight verification of critical functions after small changes to ensure basic system stability.
Sanity Testing is a lightweight verification practice executed after small code or environment changes to quickly confirm core functionality. It prevents wasting effort on deep regression runs when basic failures exist. Sanity tests are focused, fast, often automatable and typically integrated into CI pipelines to provide rapid feedback to developers and delivery processes.
Measures average time required to run the sanity tests.
Share of builds where sanity tests fail.
Time between build start and availability of sanity test results.
Sanity suite checks the health endpoint, basic authentication and DB connectivity after deployment.
After container start, core APIs and configuration values are validated to detect startup failures early.
Automated sanity tests verify that login, navigation and core dialogs are reachable.
Identify critical paths and minimal test cases.
Implement automated sanity scripts and integrate them into CI jobs.
Define clear thresholds and notification processes for failures.
Monitor and maintain the suite regularly to reduce flakiness.