Closed Bug 916368 Opened 11 years ago Closed 9 years ago

Get gaia-ui-tests running on emulators on TBPL

Categories

(Firefox OS Graveyard :: Gaia, defect, P2)

defect

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: jgriffin, Assigned: davehunt)

References

Details

(Keywords: ateam-b2g-task, Whiteboard: [gaia-ui-test])

We need to get gaia-ui-tests running on emulators on TBPL. Our current test coverage with emulators does not tell us when Gaia breaks on device builds, and running a set of gaia-ui-tests on emulators will give us some level of protection against this. We may need a different subset of tests on emulators than we run against b2g desktop builds.
I've already started working on this and do far have the unit tests passing locally.
Assignee: nobody → dave.hunt
Status: NEW → ASSIGNED
(In reply to Dave Hunt (:davehunt) from comment #1) > I've already started working on this and do far have the unit tests passing > locally. What's the ETA of getting a mozharness script to run this so that we can run this on TBPL? Ideally we can just modify the existing emulator mozharness scripts to add in this test run. The existing emulator test run script is here: http://mxr.mozilla.org/build/source/mozharness/scripts/b2g_emulator_unittest.py
Flags: needinfo?(dave.hunt)
I haven't been able to work on this in the last couple of weeks due to other priorities. As I had it, the unit tests were all passing when run individually but when run together the emulator often crashed. I was going to investigate restarting the emulator between tests to see if that made them more robust.
Flags: needinfo?(dave.hunt)
Whiteboard: [gaia-ui-test]
Depends on: 941015
Depends on: 946644
Depends on: 946649
Depends on: 968418
Depends on: 979512
Depends on: 979584
Depends on: 987045
Depends on: 987049
Keywords: ateam-b2g-task
Priority: -- → P2
See Also: → 1111503
If tests are going to run on emulator, it's much more likely they'll be the MarionetteJS tests now.
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.