Test-Case Library Code Path Analysis

Registered by Zach Pfeffer on 2013-01-07

What?
A write up detailing how to perform a full library code-path analysis for a given test-case.

Why?
We should be able to answer the question, "what libraries does a test-case exercise and to what extent does it exercise these libraries."

Context?
Part of our general platform effort.

What gets produced?
A write up on a wiki detailing how to perform this analysis for libraries.

Where will the work get put?
https://wiki.linaro.org/Platform/Android/HowTos

Blueprint information

Status:
Not started
Approver:
Jakub Pavelek
Priority:
Undefined
Drafter:
Zach Pfeffer
Direction:
Needs approval
Assignee:
None
Definition:
Pending Approval
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

Notes:
[2013/1/7 pfefferz] Please put notes here.

Meta:
Duration: 1w
Headline: Methodology to analyze library code paths completed and posted
Roadmap id: <TBD, something about general test methodology improvement>
Acceptance: A writeup on a methodology that allows a developer or tester to create report detailing what libraries a particular test exercised and what code paths in the libraries were exercized.

(?)

Work Items

Work items:
Investigate any existing methodologies for performing library analysis of a test-case and write up pointers to each methodology and what the methodology produces (Vishal may have some good insights here based on his benchmarking work): TODO
Create or customize a methodology that testers or developers can use on an Android build to characterize a test case and document the test case: TODO
Use that methodology to characterize: https://wiki.linaro.org/Platform/QA/TestCases/Android#browser-app_-_dwm and save the characterization with the test case (ensure that the characterization is pinned to a particular pinned-manifest.xml): TODO

This blueprint contains Public information 
Everyone can see this information.