Create a Binder Unit Test
Why?
The binder is a key component in Android and any changes to it should be unit-tested.
Context?
Android kernel upstreaming and development.
What gets produced?
A unit-test that tests binder.
Where will the work get put?
In a private git.
Blueprint information
- Status:
- Complete
- Approver:
- Zach Pfeffer
- Priority:
- High
- Drafter:
- Zach Pfeffer
- Direction:
- Approved
- Assignee:
- appalanaidu bade
- Definition:
- Approved
- Series goal:
- Accepted for juice
- Implementation:
-
Implemented
- Milestone target:
-
m1
- Started by
- appalanaidu bade
- Completed by
- appalanaidu bade
Related branches
Related bugs
Sprints
Whiteboard
Notes:
[2012/11/16 pfefferz] Please put notes here.
[2013/01/22 appala] changed test case steps in test plan and QA team is able to execute it
Meta:
Duration: 2w
Headline: We now have a binder unit test
Roadmap id: CARD-334
Acceptance: The following is produced:
1. A userspace binder unit-test that tests all aspects of the binder
2. A possible in-kernel unit-tests that tests all internal aspects of the binder
Work Items
Work items:
Put contents of draft into the test plan from Zach Pfeffer: DONE
Update the test plan from Zach Pfeffer with how to run the tests: DONE
compile existing AOSP binder test application by the 2013/1/14 and not break the build (Amit Pundir can help): DONE
Integrate the tests into the relavent Android build: DONE
Test in the relavent Android build: DONE
Enumerate the parts of the user-space unit-test in this BP: DONE
Work with QA to include this in the weekly testing: DONE
Monitor issues and work with the kernel team at Android through John Stultz to fix issues: DONE
Test that the code is in the build and generally works by 2013/1/20: DONE
Dependency tree
* Blueprints in grey have been implemented.
