LAVA: Integrate Ashmem Unit Test
Why?
Ashmem 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 against the required Android builds.
Where will the work get put?
In a private git.
Blueprint information
- Status:
- Complete
- Approver:
- Zach Pfeffer
- Priority:
- High
- Drafter:
- Axel Fagerstedt
- Direction:
- Approved
- Assignee:
- Axel Fagerstedt
- Definition:
- Approved
- Series goal:
- Accepted for juice
- Implementation:
- Implemented
- Milestone target:
- m1
- Started by
- Axel Fagerstedt
- Completed by
- Zach Pfeffer
Related branches
Related bugs
Sprints
Whiteboard
Notes:
[2012/12/18 pfefferz] Please put notes here.
[2013/1/28] basic test is done, expanded test is in progress.
Meta:
Duration: 2w
Headline: The basic ashmem unit test and the expanded ashmem unit test have been automated
Roadmap id: CARD-334
Acceptance:
1. The basic ashmem test is moved to the private repo and automated
2. The expanded ashmem test is moved to the private repo and automated
Work Items
Work items for 13.01:
Work with Dmitry 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 testplan available from Zach Pfeffert: DONE
Work with Vishal to push the basic Ashmem tests to the private repo: DONE
Modify the manifest to automatically ithe basic ashmem test and the expanded ashmem test in both the required Android manifests by 2013/1/14: DONE
Work with Andy Doan to write blackbox wrappers for the ashmem unit tests 2013/1/21: DONE
Ensure the tests run on the required Android builds (basic): DONE
Dependency tree
* Blueprints in grey have been implemented.