Mobile/Testing
< Mobile
Jump to navigation
Jump to search
Status
Overview
standalone | production | native UI | number running | |
---|---|---|---|---|
reftests | yes | yes | no | 3557/6113 |
mochitests | yes | yes | yes | 17873/230492 |
browser chrome | no | yes | no | 422/422 |
xpcshell | yes | no | yes | 848/1202 |
js reftests | no | yes | no | 54570/55357 |
crash tests | yes | yes | no | 1880/1888 |
talos | no | yes | yes | 9/9 |
Reftests
- over half the tests are not run on mobile
- most of this is due to not running large directories of tests
- somebody needs to go in and get more details as to what is not running.
- does running tests locally work? I find a lot of failures when I don't have the proper resolution and use the --ignore-window-size flag.
Mochitests
- currently running 11 directories
- last week releng had 16 more directories running in staging which are green (m5-8), those should be turned on this week
- layout/style has 96000+ tests and :mw22 is looking at cleaning those tests up
- some require scrollbars and we don't have those on mobile
- 1 has a e10s requirement which isn't an obvious fix
- content/* tests have patches to run with e10s and on mobile bug 668283
- seems to be blocked on bug 621363
Browser Chrome
browser-chrome test bugs (Broken out of Mochitests because of special requirements) the requires to be run out of the package-tests directory. When doing a 'make package-tests', we create a tests.jar file which we copy to the device (in the profile directory) and run the tests from there.
XPCShell
Patches landed: developers can run xpcshell on Android via ADB. About 2/3 of the tests pass; bugs opened for the remainder: xpcshell test bugs
JS Reftests
- we already run the majority of these in production
- we need to create a link to the jstests.list file so we can run these on a developer machine
- we should document the commented out tests with more details
Crash tests
- almost all are running, we should look into the tests we have turned off in the manifest files and document them better.
Talos
- we don't run tp5, but we have tp4m.
- we need to turn off ts, txul and replace with ts_paint and tpaint
- tpan/tzoom/tp4m are failing frequently bug 662936
Status Meetings
There will be weekly meetings to discuss the current status of testing on Mobile and coordinate the required work between teams. Details
- Wednesdays @ 10:30am PST/PDT
- Meeting in Warp Core
- Vidyo in Warp Core
- #mobile for back channel
Notes
Q1
2010 Q4
- 12/28/11
- 12/21/11
- 12/14/11
- 12/07/11
- 11/30/11
- 11/23/11
- 11/16/11
- 11/09/11
- 11/02/11
- 10/26/11
- 10/19/11
- 10/12/11
- 10/05/11
Q3