Port marionette-js-runner to emulators



6 years ago
2 years ago


(Reporter: gaye, Unassigned)


Firefox Tracking Flags

(Not tracked)


(Whiteboard: [runner][emulator])

IIRC the comms and systemsfe teams were interested in writing ui tests that use the extended capabilities of emulators.
Pretty sure Aus has done work on this already. Adding him to the CC list.
That's great!
If we have this, we might not need to write mock objects for testing things anymore.
I have few questions for this.

The tests might run slowly on emulator.
Is the performance of emulator a issue?
I could check that with Vicamo later.

And the emulator will run on Travis, right?

Aus says it runs "fast enough" (but I'm ni?'ing him here just in case), but I guess we'll see. That was part of my original idea about starting to write piecemeal simulators for things like RIL/sensors/etc outside of the emulator, but at this point it's all untested so I figured we'd go with what's done first and expand from there if needed.

Yes, the end goal is having this working on Travis. This was originally a requirement for us in august of last year when we started the operator variant work with the idea that nothing shipped without integration tests run per-build, it's just taken a long time to get things through.
Flags: needinfo?(aus)
The performance of the emulator is workable. It's not ideal when it's running in VM though, but, none of the tests timeout because the emulator runs too slow (afaik, and we use it on tbpl).

Locally, this won't be an issue as the emulator will be running natively when on Linux or OS X.
Flags: needinfo?(aus)
Depends on: 994764
Whiteboard: [runner][emulator]
Doesn't really depend on Bug 994764, but it may be positively affected by it
Bulk closed as part of https://bugzilla.mozilla.org/show_bug.cgi?id=1422750
Closed: 2 years ago
Resolution: --- → INCOMPLETE
Product: Testing → Testing Graveyard
You need to log in before you can comment on or make changes to this bug.