redesign lava-android-test to use some common parts of lava-test
Comment from one review:
> Could we consider depending on lava-test and reuse the TestArtifacts class defined
> there? I know this is a long topic so we can postpone this discussion but I
> want to reverse the trend so that we go towards unified APIs for both host-
> driven (lava-android-test, upcoming lava-uboot-test) and target-driven (lava-
> test) frameworks.
Yes, I agree this, especial we will have more similar test tools.
There are some common parts between lava-test and lava-android-test now.
And probably can can abstract like this.
lava-tools
^
|
lava-test-base
^ ^ ^
| | |
Linux Android Others
Blueprint information
- Status:
- Complete
- Approver:
- Andy Doan
- Priority:
- Undefined
- Drafter:
- Yongqin Liu
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Obsolete
- Series goal:
- Accepted for trunk
- Implementation:
- Unknown
- Milestone target:
- None
- Started by
- Completed by
- Michael Hudson-Doyle
Whiteboard
<plars> also he has an action to finish drafting https:/
<plars> which is in progress, and could possibly land this month
<plars> zyga: I think you've looked at the work in progress for that change
<zyga> plars, huh
<plars> do you agree it could land this release?
<zyga> plars, all I saw was a blueprint that's empty
<plars> zyga: this is for the work to split out the common pieces between lava-test and lava-android-test
<fabo> plars: so https:/
<zyga> plars, I don't think we are going to see that this cycle
<plars> zyga: I thought you had reviewed some code for it also
<plars> ok
maybe not
<zyga> plars, not on that
plars, that's not started IMO
plars, and
plars, the only way it can happen in the shape of that blueprint
plars, is to start really working on lava-something-test that would allow us to touch bootloaders
plars, so hosted but non-android framework
otherwise it's going to be a silly redesign where we need to re-do it after we go back to bootloader tests
<plars> zyga: yes, I think we need to talk a lot about it
<zyga> but I still see the need to cleanup lava-android-test
it's probably bit-roted a bit since it forked lots of old lava-test
<plars> no doubt
<zyga> anyway 0.02
[zyga, 2012-04-11] useful lava-tool branch waits for a merge request, please review it if possible
Meta:
Headline: extract the common part of lava-android-test and lava-test
Acceptance: lava-test and lava-android-test are based on the same common part, and the common part can be used for other lava-xxx-test.
Work Items
Work items:
Investigate the common part of lava-android-test and lava-test: TODO
Investigate about lava-uboot-test: TODO
Design the common part: TODO
Implement the common part: TODO
Remove linaro-json from lava-android-test: DONE
Integrate into lava-tool's lava command: TODO
Remove linaro-json from lava-test: TODO
Add provider for test like lava-test, should merge this twos: TODO
Modify to use lava-vcs for both lava-xxx tools: TODO