Here is the entire post-release testing arsenal. But we will only use what your product really needs.
Smoke Testing – a quick check to ensure that the release has not broken any critical functionality. Running key scenarios immediately after deployment.
Production Data Testing – verification of the correct display and processing of real user data in a production environment.
Accessibility Feedback Testing – collecting and analyzing feedback from users with special needs.
Production Monitoring – monitoring system stability using logs, metrics, alerts, APM tools (Datadog, New Relic, etc.).
Performance Monitoring – analysis of application performance after release: response time, download speed, behavior under load.
Localization Verification – verification of localization in a real environment: texts, formats, display in different languages.
Regression Testing – checking that bugs have not returned after release and that everything works as it did before release.
Error Monitoring & Logging Analysis – automatic collection of errors, log analysis, and tracing of bugs that have manifested themselves in real users.
Mobile Device Monitoring – testing application behavior on mobile devices after downloading from the App Store / Google Play (especially in real networks).
Hotfix Verification – verification of operational fixes after bugs are detected in production.
User Behavior Analysis – tracking clicks, navigation, and drops through tools (Google Analytics)
Crash Reporting – tracking crashes in mobile applications via Crashlytics, Sentry, and similar systems.
Bug Verification – verification that bugs discovered by users after release have been fixed.
A/B Testing (if the release includes flagged features) – testing different versions of functionality on real users to assess their impact.
Customer Support Feedback Analysis – analysis of tickets and complaints from users – identification of bugs, UX issues, and missed scenarios.
Sanity Testing – detailed verification of individual functions if complaints have been received or urgent changes have been made.
Feature Flag Testing – testing of features enabled by feature flags – correctness, rollback, impact on performance
Rollback Readiness Testing – testing the possibility and correctness of rollback (if critical problems arise).