Firefox OS/Performance/Automation/FPS: Difference between revisions
< Firefox OS | Performance | Automation
Jump to navigation
Jump to search
m (Mlee moved page FirefoxOS/Performance/Automation Testing/FPS to FirefoxOS/Performance/Automation/FPS) |
m (Lakrits moved page FirefoxOS/Performance/Automation/FPS to Firefox OS/Performance/Automation/FPS: The official spelling of "Firefox OS" leaves a space between the two parts of the name. It's easier to find a page if the spelling of its name is...) |
(No difference)
| |
Latest revision as of 13:59, 1 February 2015
FPS Measurement and CI Roadmap
- Goal: Daily high-speed camera measurement of FPS in critical areas all actively developed branches with comparisons against "waterline" numbers, with notifications of improvements and regressions.
- Method: Eideticker - high speed camera measurement
- Frequency: Daily
- Targets
- Nightly builds of all branches that have active development
- Various app screens and continuous actions in or between screens
- Production/reference devices
- Comparisons: Must be able to set "waterlines" to compare results against. Examples are: previous release, chipset vendor reference numbers, target numbers from Mozilla UX performance guidelines.
Teams
- FxOS Perf Team
- Automation Team
- Release Engineering (?)
TBD
- Enumerate all test scenarios and workloads (eg, Homescreen, scrolling Gallery, scrolling/panning web content, etc) which need to be measured
- Which device(s) to measure
- Need other teams to correct & update the roadmap items below
Roadmap
| TASK | TEAM | OWNER | STATUS |
| High-speed camera measurement of FPS on device(s) | |||
| Automation of measurement | |||
| Automated builds to be measured | |||
| Automatedly test nightly builds | |||
| Report results to Datazilla | |||
| Per-test multiple waterline support | |||
| Notifications of improvement/regression over x% |