Automated Android Testing
In this session we will talk about automated Android testing.
Description
------------------
Before each change is accepted it undergoes premerge testing. The tester, LAVA, runs a set of tests on a test build that contains the change.
To get the most out of the test loop, we would like to identify areas of improvement so that faults found in this loop can be efficiently analysed and fixed.
Agenda
------------
1. Introduce what we have and what's happened recently with reviewing, building and testing.
2. Open a discussion on improvements/new features
* What improvements can we make in LAVA
* What improvements can we make in Gerrit
* Speed ups/efficiencies.
Goals
--------
1. Discuss new tests
2. Plan for keeping a unit alive in a failed state
3. Plan for bootloader testing (JTAG)
4. Discuss the best way to capture and present test results for developers
Blueprint information
- Status:
- Complete
- Approver:
- Zach Pfeffer
- Priority:
- Essential
- Drafter:
- Frans Gifford
- Direction:
- Approved
- Assignee:
- Frans Gifford
- Definition:
- Approved
- Series goal:
- Accepted for 2011q4
- Implementation:
-
Implemented
- Milestone target:
-
connect-q4.11
- Started by
- Zach Pfeffer
- Completed by
- Zach Pfeffer
Whiteboard
Notes from session:
[fgiff]: Please add your slides
What improvements can we make in LAVA:
- [zyga/pfefferz/
- OpenOCD support as separate project
- Command line job generator
What improvements can we make in Gerrit:
- Fix problems with build failures caused by infrastructure issues
- Fix hardware -> no more hangs
- Better interoperability between people who use Gerrit and people who don't
- Bugs fixed in Gerrit commits
- Add groups (e.g. add android-team to review)
- Automatically add reviewers
- Improve process of how fast reviews happen
- Ability to batch commits
What improvements can we make in android-build:
- Investigate gerrit trigger plugin for Jenkins?
- Speed up builds (disable host dalvik?)
