Juice: Create a Logger Unit Test
Why?
The logger 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 logger.
Where will the work get put?
In a private git.
Blueprint information
- Status:
- Complete
- Approver:
- Zach Pfeffer
- Priority:
- High
- Drafter:
- appalanaidu bade
- Direction:
- Approved
- Assignee:
- appalanaidu bade
- Definition:
- Approved
- Series goal:
- Accepted for juice
- Implementation:
-
Implemented
- Milestone target:
-
m2
- Started by
- appalanaidu bade
- Completed by
- Jakub Pavelek
Related branches
Related bugs
Sprints
Whiteboard
Meta:
Duration: 2w
Headline: We now have a logger unit test
Roadmap id: CARD-335
Acceptance: A userspace logger unit-test that tests all aspects of the logger is built and the git is delivered to an integration engineer for build inclusion.
Notes:
[2013/1/16 pfefferz] Shifting remaining WIs to 13.03.
Work Items
Work items for 13.01:
Write a test spec in the test plan from Zach Pfeffer: DONE
Have test plan review by Zach Pfeffer and John Stultz: DONE
Start implementing the test according to the test-plan: DONE
Work items for 13.02:
Implement the test according to the test-plan, initial implementation due by 2013/2/8: DONE
Integrate review comments: DONE
Update the test plan from Zach Pfeffer with how to run the tests: DONE
Write up instructions to run the test manually and include the tests in the test plan from Zach Pfeffer: 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: DONE
Send git to Axel: DONE
[fagerstedt-axel] Integrate unit test into private git repo: DONE
Work items for 13.03:
Work with QA to include this in the weekly testing (seen in build #180 testing as four tests): DONE
Dependency tree
* Blueprints in grey have been implemented.
