Closed
Bug 1015391
Opened 11 years ago
Closed 10 years ago
[Template App] Implement new startup loading events
Categories
(Firefox OS Graveyard :: Gaia::PerformanceTest, defect, P2)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: Eli, Unassigned)
References
Details
(Keywords: perf, Whiteboard: [c=automation p=2 s= u=])
+++ This bug was initially created as a clone of Bug #837668 +++
We need to measure when the template app is usable by the user. For that we'll need to send an event (the moment is specific to the app) to |window| that the performance test will be able to receive.
The events for implementation are outlined in bug 996038.
Reporter | ||
Comment 1•11 years ago
|
||
Bug 996038 introduces new events outlining the phases of application startup. Each of these 5 events needs to be implemented.
Summary: [Template App] "ready to use" perf measurement → [Template App] Implement new startup loading events
Reporter | ||
Updated•11 years ago
|
Assignee: nobody → eperelman
Whiteboard: [c=automation p= s= u=] → [c=automation p=2 s= u=]
Reporter | ||
Comment 2•11 years ago
|
||
As an FYI, this implementation needs to land in 2.0 as it is important for meeting release performance acceptance criteria.
https://wiki.mozilla.org/FirefoxOS/Performance/Release_Acceptance
Updated•11 years ago
|
Status: NEW → ASSIGNED
Reporter | ||
Updated•11 years ago
|
Assignee: eperelman → nobody
Reporter | ||
Comment 3•10 years ago
|
||
Template app is being replaced by test-startup-limit for performance testing.
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•