Unified Telemetry/Status reports/Android/April 7 2016
From MozillaWiki
Contents
UT for Android status report April 7, 2016, 2015
Overall Project Health
Last week: Green
This week: Green
Project summary
- Fixes for production issues now being validated, default search now in nightly
Exec Summary
- Q2 - Using UT in firefox android to make business decisions, including populating KPI dashboard.
Accomplished for Last Period
- timeline of core ping implementation as WIP
- Client ID fix uplifted to beta
- defaultsearch in nightly, validation looking good so far
- client id race condition in PR
- uploader design WIP
Planned for Next Period
Validation:
- Waiting to see data for fixes as it comes back in
- Planning to engage Mobile QA with an eye to network packet sniffing as validation effort.
- ongoing sprint based work
Risks and items to retire
Dashboards and consumers:
- Dashboard form core pings (need min requirements)
- PM input
- Significance of abnormal session and search counts for first rev.
Validation:
- automated tests
- manual QA
- mobile team has in-house and SoftVision QA
- scope of v0 ping version is not be appropriate for heavy test effort
- manual QA will happen from v3 on
- Android Nightly has small population, so:
- Sanity-check on Nightly
- use Beta for validation
- update latency to beta ~2 weeks to 90% of population
- server-side analysis
- quality checks for ordering of pings, etc. and verifying the data looks sane
- sanity checks at volume (look for large gaps etc)
- validate against adjust data?
- we should get to an ongoing "health of data" report from there
- QA & analysis work needs to be defined and scoped/packed
- schema validation
- pipeline-side schema validation support is on the way
- pipeline team may be interested to start this with the "core" ping
