[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linaro-validation
Subject:    [Linaro-validation] Android black-box testing with lava-blackbox (aka android-lava-wrapper)
From:       michael.hudson () linaro ! org (Michael Hudson-Doyle)
Date:       2012-08-27 23:13:52
Message-ID: 87ehmsgc7j.fsf () canonical ! com
[Download RAW message or body]

Zygmunt Krynicki <zygmunt.krynicki at linaro.org> writes:

> On Mon, Aug 27, 2012 at 1:08 AM, Michael Hudson-Doyle
> <michael.hudson at linaro.org> wrote:
> > Zygmunt Krynicki <zygmunt.krynicki at linaro.org> writes:
> > 
> > > Hey everyone.
> > > 
> > > I'd like to interest you in my progress on black-box testing for Android.
> > 
> > I am certainly interested!
> > 
> > > The relevant code lives in:
> > > 
> > > 1) Github: https://github.com/zyga/android-lava-wrapper/tree/develop
> > > 
> > > Note that the develop branch will soon land to master. Currently master
> > > is an unusable older copy. I will also rename this repository to
> > > lava-blackbox or lava-android-blackbox (to be determined later)
> > > 
> > > 2) Launchpad:
> > > https://code.launchpad.net/~zkrynicki/lava-android-test/blackbox
> > > 
> > > This branch is almost ready to land. I will finish the details tomorrow
> > > or on Monday.
> > 
> > Hum.  This is both more and less blackboxy than I was envisioning:
> > 
> > More: because it produces the bundles on the device in C, rather than on
> > the host in Python.
> > 
> > Less: because it is still driven by ADB and so relies on communication
> > between host and device when booted into the test image.
> 
> This is only so that it is integrated with the current infrastructure.
> The real point is the lava-blackbox executable. How it gets started is
> currently unspecified (so I use lava-android-test to run it) but I
> suspect that in near future it will be adapted to auto-start on boot
> in certain images.

Ah.  OK.

> > Is changing this latter part in the roadmap?  Because if not, I'm not
> > entirely sure I understand the point of this work, I'm afraid.  If it
> > is -- and the slightly bodgy way of joining it in to lava-android-test
> > is just a stepping stone -- then: yay!
> 
> Actually it became related to black box testing evolutionary, not by
> strict design. I was just implementing my blueprint about adding some
> of the AOSP tests to LAVA. I thought that I could very well implement
> it in a way that is closer to blackbox ideas so future migration is
> less costly.

That makes sense too :)

Cheers,
mwh

> > > The project history and up-to-date status is in this blueprint:
> > > 
> > > https://blueprints.launchpad.net/linaro-android/+spec/aosp-tests-on-jb
> > > 
> > > You can observe the latest results I've produced this way here:
> > > 
> > > http://validation.linaro.org/lava-server/dashboard/streams/anonymous/zyga/bundles/a2e3b9a9ff3181152c7e5ac074162e88fccc2eeb/
> > >  
> > > Best regards
> > > ZK
> > 
> > Cheers,
> > mwh
> 
> Thanks
> ZK


[prev in list] [next in list] [prev in thread] [next in thread]