Merge lp://qastaging/~zyga/lava-android-test/blackbox into lp://qastaging/lava-android-test

Proposed by Zygmunt Krynicki
Status: Merged
Merged at revision: 205
Proposed branch: lp://qastaging/~zyga/lava-android-test/blackbox
Merge into: lp://qastaging/lava-android-test
Diff against target: 493 lines (+489/-0)
1 file modified
lava_android_test/test_definitions/blackbox.py (+489/-0)
To merge this branch: bzr merge lp://qastaging/~zyga/lava-android-test/blackbox
Reviewer Review Type Date Requested Status
Andy Doan (community) Approve
Linaro Validation Team Pending
Review via email: mp+121299@code.qastaging.launchpad.net

Description of the change

Integration with the blackbox tests for android.

This is _not_ a typical test. Please read the implementation and especially all the comments to understand the decisions made.

To post a comment you must log in.
Revision history for this message
Yongqin Liu (liuyq0307) wrote :

from this file itself, it's no problem.
but I still feel that make it a new sub command(like run-blackbox) in the commands.py
will make the source more readable.
although that needs to modify more files (including lava-dispatcher) instead of only this one file.

And also suggest adding a provider in the provider.py to support such tests that only need to run and get the test result.
no need to use the parser to parse the output.

and maybe this is just a temporary place to integrate the blackbox test,
since I can't see how the blackbox will be in the future, so please also ask Andy to review this MP.

Revision history for this message
Zygmunt Krynicki (zyga) wrote :

W dniu 29.08.2012 08:34, Yongqin Liu pisze:
> from this file itself, it's no problem.
> but I still feel that make it a new sub command(like run-blackbox) in the commands.py
> will make the source more readable.
> although that needs to modify more files (including lava-dispatcher) instead of only this one file.
>
> And also suggest adding a provider in the provider.py to support such tests that only need to run and get the test result.
> no need to use the parser to parse the output.

The only long term solution is to fix the API mistakes and remove all
other subcommands. There is no justification for having all those
subcommands. All of that are tests, they should have single install/run
interface.

> and maybe this is just a temporary place to integrate the blackbox test,
> since I can't see how the blackbox will be in the future, so please also ask Andy to review this MP.

OK

Thanks
ZK

Revision history for this message
Andy Doan (doanac) wrote :

Seems like some of the code isn't that necessary:

debuggable_* - cool, but now that the feature works is it needed?

SuperAdb/AdbMixin - seems like you could pretty much just add a new listdir helper

However, that's nothing major and its isolated. Also, as Yongqin said, the blackbox stuff will eventually move us to something else, so lets get this in and see it work!

review: Approve
Revision history for this message
Zygmunt Krynicki (zyga) wrote :

W dniu 29.08.2012 17:52, Andy Doan pisze:
> Review: Approve
>
> Seems like some of the code isn't that necessary:
>
> debuggable_* - cool, but now that the feature works is it needed?

No, it's not needed but it's still a cool thing (since l-a-t swallows
most exceptions) for analyzing problems. Perhaps I could just move it to
some utils.py module?

> SuperAdb/AdbMixin - seems like you could pretty much just add a new listdir helper

Yes, that behaves much like os.listdir() and has more predictable
behavior. It's just a helper that does parsing essentially :-)

> However, that's nothing major and its isolated. Also, as Yongqin said, the blackbox stuff will eventually move us to something else, so lets get this in and see it work!

I don't know how it will evolve over time. My current intent is to
ensure we can continue to harvest data from l-b with l-a-t, and in near
future with l-t. Once the rest of the framework solidifies and matures
we could simplify the interaction but I don't suspect we'll go away form
the simple usefulness of adb-managed communication. It simply works very
well and has little complexity.

Thanks
ZK

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
The diff is not available at this time. You can reload the page or download it.

Subscribers

People subscribed via source and target branches