LAVA: Integrate Binder Unit Test
Why?
Binder is a key component in Android and any changes to it should be unit-tested. To ensure the changes are tested the test should be integrated into LAVA.
Context?
Android kernel upstreaming and development.
What gets produced?
A test case that LAVA will run for all required Android builds.
Where will the work get put?
Stock binder native benchmark test is used. Test result will be available on respective Android build page.
Blueprint information
- Status:
- Complete
- Approver:
- Zach Pfeffer
- Priority:
- High
- Drafter:
- Amit Pundir
- Direction:
- Approved
- Assignee:
- Amit Pundir
- Definition:
- Approved
- Series goal:
- Accepted for juice
- Implementation:
-
Implemented
- Milestone target:
-
m1
- Started by
- Amit Pundir
- Completed by
- Amit Pundir
Related branches
Related bugs
Sprints
Whiteboard
Notes:
[2012/12/18 pfefferz] Please put notes here.
[2013/1/15 pfeffez] The goal is to add a "binder" test to LAVA
You would add, "binder" to:
LAVA_TEST_
so it becomes:
LAVA_TEST_
in
https:/
[2013/1/15 pfefferz] Added 2 more WIs related to LAVA and automation.
[2013/1/21 pundiramit] Pushed "shell-binder" test in lava-android-test.
[2013/1/25 pundiramit] blackbox wrapper for binder test need to move to next cycle since linaro-
Meta:
Duration: 2w
Headline: The binder unit test has been automated
Roadmap id: CARD-334
Acceptance:
1. The stock binder native benchmark test has been automated.
Work Items
Work items for 13.01:
Work with Appala to find out where his tests are, how to run them and what a successful run looks like: DONE
Make sure this info is in the the test plan available from Zach Pfeffer: DONE
Work with Andy Doan to write blackbox wrappers for the binder unit tests: DONE
Ensure the tests run on the required Android builds: DONE
Fix execution mode so LAVA can run binder: DONE
Use 10 as a default, but allow the user to pass in the iteration count into LAVA (YongQin should know how to do this): DONE
Dependency tree
* Blueprints in grey have been implemented.
