Closed Bug 920097 Opened 11 years ago Closed 11 years ago

eideticker does not account for initial delay when launching apps

Categories

(Testing Graveyard :: Eideticker, defect)

Product:
Testing Graveyard
Component:
Eideticker
Platform:
ARM
Gonk (Firefox OS)
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: bkelly, Unassigned)

References

Details

(Keywords: perf, Whiteboard: [c=automation p= s=2013.10.25 u=]) 

While investigating v1.2 launch times we noticed that the eideticker movies have about a 1-second delay before the app actually launches.  In comparison, tapping on the screen seems to start the launch immediately.

This also jives with the end numbers we are seeing from eideticker vs. manual tests.  Manual tests show up around 2-seconds for launch while eideticker showed around 3-seconds.

From talking with Will, it sounds like simulating touch events using orangutan (sp?) might result in less artificial latency than the current marionette launch mechanism.
Yep, bug 888103 has been filed to deal with this problem. I'll mark that as a dependency here, although almost certainly the solution proposed there is what we want (and will fix this).
Depends on: 888103
Keywords: perf
Whiteboard: [c=automation p= s= u=]
this is fixed now that bug 888103 has landed
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Whiteboard: [c=automation p= s= u=] → [c=automation p= s=2013.10.25 u=]
Product: Testing → Testing Graveyard
You need to log in before you can comment on or make changes to this bug.