Monkeyrunner Tests for Common Android Usage

Registered by Zach Pfeffer on 2012-03-05

All Android testing will be done using the Android Test Framework:

http://developer.android.com/guide/topics/testing/testing_android.html

Android specific tests will be organized under test/biglittle/apps and be included in

git://android.git.linaro.org/test/biglittle/apps.git

These tests will use monkeyrunner:

http://developer.android.com/guide/developing/tools/monkeyrunner_concepts.html

To run the following scenarios (all tests pass if the test completes) while a daemon auto switches the CPU between big and LITTLE states.

Switch back and forth between the default browser and maps
Switch back and forth between AngryBirds and the default browser
Switch back and forth between a 3-D game and the default browser
Suspend to SWFI
Wake from SWFI
Full suspend
Wake from full suspend
Play a local audio clip against software decode
Play a local audio clip against hardware decode
Play a local video against software decode
Play a local video against hardware decode
Play AngryBirds
Play a 3-D game
Make and complete a call
Check email
Do navigation
Do navigation and select a place to eat
Run 0xbench
Scroll a static webpage using the built-in browser
Scroll a page with included video using software decode using the built-in browser
Scroll a page with included video using hardware decode using the built-in browser
Play a software decoded YouTube clip
Play a hardware decode YouTube clip
Use Google Hangouts
Post a facebook update

The tests will be runnable on their own and be included in each build across all targets.

Blueprint information

Status:
Complete
Approver:
Zach Pfeffer
Priority:
High
Drafter:
Zach Pfeffer
Direction:
Approved
Assignee:
tianhongwang
Definition:
Approved
Series goal:
Accepted for 2012q1
Implementation:
Implemented
Milestone target:
milestone icon 12.03
Started by
Zach Pfeffer on 2012-03-28
Completed by
Zach Pfeffer on 2012-03-28

Related branches

Sprints

Whiteboard

Notes:
[2012/2/28 pfefferz] Put notes here.
[2012/03/14 liuyq0307] Each test should have two parts: executing the test and checking the test result, Execution will be a little easier, but for the result checking with image comparison in monkeyrunner, it seems a little not much flexible. Should we consider a more accurate and flexible method?

Meta:
Roadmap id: ANDROID2012-Q1-TEST
Headline: Common Android usage tests available for all targets
Acceptance: A selection of tests form the description have been implemented

(?)

Work Items

Work items:
Investigate the existing Android test framework: DONE
Submit a test to Gerrit: DONE
Implement: Switch back and forth between the default browser and maps: DONE
Implement: Switch back and forth between AngryBirds and the default browser: DONE
Implement: Switch back and forth between a 3-D game and the default browser: DONE
Implement: Play AngryBirds: DONE
Implement: Play a 3-D game: DONE
Implement: Do navigation: DONE
Implement: Do navigation and select a place to eat: DONE
Implement: Run 0xbench: DONE
Make and complete a call: DONE

This blueprint contains Public information 
Everyone can see this information.