The What, Why and How of Web Analytics Testing
summary
Tests analytics at the source using browser DevTools or a proxy to inspect requests, avoiding late-stage report surprises; uses an open source web analytics automation testing framework to add analytics asserts to functional tests and extends this for native Android by running a debug build with separate analytics bucket and parsing logcat to match events. Handles a real product with 1.75M installs and 13,000 device types, and flags SDK batching, volume and scale as key challenges.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 2:50What is Web Analytics
- 5:01IOT and Big Data
- 8:05What does this mean for testing
- 10:33How to test for analytics
- 12:56How to test analytics
- 16:27Testing at the source
- 18:50Challenges
- 23:01Web Analytics Automation Testing Framework
- 24:13Native Apps
- 28:03iOS
- 29:03AB Testing
- 30:01Functional Testing
- 32:18Scaling
- 34:18Why Analytics Testing
- 37:10Testing Approach
- 39:20Native App Perspective
related talks
07mHow ‘Product Analytics’ Helpful in Defining ‘Test Strategy’?
12mHow Usage Analytics Can Improve End User Experience?
26mMeasuring Developer Happiness: Analytics for Backstage
38mThe 15 Minute Model for Optimising Device Experiences
44mAndroid Benchmarking and other stories
31mMobile Project Analytics — Verify and Trust
29mA New Kind of Analytics: Actionable Performance Analysis
49mAll Levels of Performance Testing and Monitoring in Web Apps