Analytics defects rarely stop an app release, but they can quietly make weeks of product data unusable. Treating instrumentation as part of acceptance criteria keeps measurement aligned with the experience.
Test complete journeys
Run clean installs on supported iOS and Android versions. Check event names, timestamps, identity transitions and required properties at each step. Include cancellation, retry and error paths—not only the happy path.
Watch for duplication
Repeated taps, background transitions and screen re-renders commonly fire events twice. Compare raw event streams with the visible action and confirm that server-side and client-side events cannot overlap unexpectedly.
Record the result
Keep a lightweight QA log with build number, environment, device and evidence. When a metric changes after release, this record helps the team distinguish user behaviour from instrumentation drift.