Mobile/Testing/12 28 11: Difference between revisions
Jump to navigation
Jump to search
Line 18: | Line 18: | ||
== S1/S2 Automation == | == S1/S2 Automation == | ||
* Wrote [http://cmtalbert.wordpress.com/2011/12/27/cross-browser-startup-automation/ blog post] on current status yesterday | |||
** Update: nexus* phones have completed all the data for the birch data. They are now working on the mozill-central builds from Dec. 6 to the present. Once the samsung and droid pro finish their birch runs, they will start on those as well. | |||
** I was also able to reduce the timeout on the nexus phones and it is speeding up the per-test time by 50%. | |||
= Round Table = | = Round Table = |
Revision as of 18:59, 28 December 2011
Previous Action Items
- dougt fixed naoki's bugs
- mfinkle to investigate automated test writer
- joel/geoff to review/add to [how to write a robotium test]
Status reports
Dev team
Rel Eng
- landed bug 711367 (--nativeUI)
- working on bug 712422 (--bootstrap)
A Team
- orange rate: [spreadsheet]
- robotium patches are reviewed, ironing out issues with try server
- waiting on --bootstrap flag to land
S1/S2 Automation
- Wrote blog post on current status yesterday
- Update: nexus* phones have completed all the data for the birch data. They are now working on the mozill-central builds from Dec. 6 to the present. Once the samsung and droid pro finish their birch runs, they will start on those as well.
- I was also able to reduce the timeout on the nexus phones and it is speeding up the per-test time by 50%.
Round Table
- Q1 work items?
- integrate and support robotium for talos/browser-chrome replacement
- support other automation/harnesses?
Action Items
- joel/geoff to review/add to [how to write a robotium test]
- joel/bear to get robobotium stuff in place so QA can start practicing/reviewing