Closed
Bug 1425322
Opened 7 years ago
Closed 6 years ago
[meta] Android emulator unit test modernization
Categories
(Firefox for Android Graveyard :: Testing, enhancement, P1)
Tracking
(firefox59 affected)
RESOLVED
WORKSFORME
Tracking | Status | |
---|---|---|
firefox59 | --- | affected |
People
(Reporter: gbrown, Assigned: gbrown)
References
(Blocks 1 open bug)
Details
(Keywords: meta)
Our emulator unit tests currently run against Android 4.3 (or 4.2) using emulator binaries from the sdk circa api 18. There are various barriers to running tests in a modern environment, like Android 7.0. There are various advantages to running tests in a modern environment (relevance, more features, potential performance improvements).
Assignee | ||
Updated•7 years ago
|
Priority: -- → P1
Assignee | ||
Updated•7 years ago
|
Assignee | ||
Updated•7 years ago
|
Updated•7 years ago
|
Assignee | ||
Updated•7 years ago
|
Depends on: geckoview_mochitest
Assignee | ||
Comment 1•6 years ago
|
||
This bug has served its purpose, and tracked a lot of work in 2018. Today we have an android-em-7.0-x86 test platform with fast emulators on packet.net, and the android-hw-* test platforms for performance and special purpose testing on hardware. geckoview test apps are explicitly supported. We can even (finally!) run web-platform tests on android.
There's more to do -- greening more test suites, possibly reducing traditional aws emulator tests, etc. -- but we've done more than we set out to do - yeah!
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WORKSFORME
Updated•4 years ago
|
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•