Firefox OS/Performance/Automation/Launch Latency

Launch Latency

Summary

Measures elapsed time from the first launch of an application to a series of defined startup events.

Precision

TBD

Scenarios

Launch each of the following apps from a cold state:

• Browser
• Camera
• Contacts
• Dialer
• Email
• Gallery
• Marketplace
• Settings
• SMS

Report the time elapsed to the following events:

• moz-chrome-dom-loaded
• moz-chrome-interactive
• moz-app-visually-complete
• moz-content-interative
• moz-app-loaded

Dashboards

This should be a serious of links to dashboards per branch, device, and test. Unfortunately, Datazilla doesn't seem to allow direct linking without embedding revisions and other time-specific artifacts in the URL. This is a real problem.

2.0

Test	Flame
startup_>_moz-chrome-dom-loaded	Yes
startup_>_moz-chrome-interactive	Yes
startup_>_moz-app-visually-complete	Yes
startup_>_moz-content-interative	Yes
startup_>_moz-app-loaded	Yes

Procedure

This needs more detail.

1. Clear app from memory
2. Inject launch command
3. Monitor app events for each of the five events under Scenarios
4. Time elapsed is the time between that event and start time?

Roadmap

Overview

• Lead: Eli Perelman
• Metabug: TBD

Milestone 1: Design

	Target Release	Test Design	Validity Review
All	TBD	Bug	Bug

Milestone 2: Test

	Target Release	Instrumentation	Workloads	Single-run test	Results Review
Browser	TBD	Bug	Bug	Bug	Bug
Camera	TBD	Bug	Bug	Bug	Bug
Contacts	TBD	Bug	Bug	Bug	Bug
Dialer	TBD	Bug	Bug	Bug	Bug
Email	TBD	Bug	Bug	Bug	Bug
Gallery	TBD	Bug	Bug	Bug	Bug
Marketplace	TBD	Bug	Bug	Bug	Bug
Settings	TBD	Bug	Bug	Bug	Bug
SMS	TBD	Bug	Bug	Bug	Bug

Milestone 3: Publish

	Target Release	Published Results	Documentation
Browser	TBD	Bug	Bug
Camera	TBD	Bug	Bug
Contacts	TBD	Bug	Bug
Dialer	TBD	Bug	Bug
Email	TBD	Bug	Bug
Gallery	TBD	Bug	Bug
Marketplace	TBD	Bug	Bug
Settings	TBD	Bug	Bug
SMS	TBD	Bug	Bug

template