On 5 April 2012 05:14, Le.chi Thu <[email protected]> wrote: > Thanks Paul. > > TEMA uses monkey runner to fire events to target. TEMA uses hierarchy > viewer API to extract the UI tree (not as an image) > > STE is considering open source our test framework named UTF. > > Here is short feature list of UTF. > > * Written in Python > * Test logic is run on host and communicate with target via ADB for > Android or serial port for Linux. > * The framework take care of host logging and targets logging (such at > adb logcat). > * The framework initialize the targets and deployment of apk, resource files > * The framework include a modified UI lib from TEMA for ui driven > tests for Android > * The framework allow test case to listen for a pattern of data on the > target logs > * The framework provide test case console / shell interface (pexpect > like interface) > * The framework provide test case configuration API (read data from ini file) > > We will have a decision next week within STE how to process with open > sourcing UTF. I will then provide you more info about the UTF by then.
Does the framework get upgraded for each Android release? > BR > > /Chi Thu > On 5 April 2012 11:56, Paul Larson <[email protected]> wrote: >> Apparently you can actually inspect the ui, look for text in it, etc. rather >> than just taking screenshots and comparing them. >> >> >> On Wed, Apr 4, 2012 at 3:42 PM, Zach Pfeffer <[email protected]> >> wrote: >>> >>> I think I'd rather just focus on monkey runner stuff. Chi Thu, what >>> doe TEMA give us that Monkey runner doesn't? >>> >>> On 28 March 2012 07:05, Le.chi Thu <[email protected]> wrote: >>> > I will talk with you about the tema. >>> > >>> > BR >>> > >>> > /Chi Thu >>> > >>> > On 27 March 2012 22:07, Paul Larson <[email protected]> wrote: >>> >> Hi Zach, I think the main thing we were looking for feedback from you >>> >> on is >>> >> this tema test, and whether you consider it to be useful beyond what >>> >> monkeyrunner already provides. There seems to be some overlap. >>> >> >>> >> >>> >> On Tue, Mar 27, 2012 at 10:01 AM, Zach Pfeffer >>> >> <[email protected]> >>> >> wrote: >>> >>> >>> >>> On 23 March 2012 08:07, Le.chi Thu <[email protected]> wrote: >>> >>> > sorry not include the link to blueprints. >>> >>> > >>> >>> > Here they are : >>> >>> > >>> >>> > >>> >>> > >>> >>> > https://blueprints.launchpad.net/lava-scheduler/+spec/manually-health-check >>> >>> > >>> >>> > >>> >>> > https://blueprints.launchpad.net/lava-test/+spec/linaro-validation-ste-kernel-testsuite >>> >>> > >>> >>> > >>> >>> > https://blueprints.launchpad.net/lava-scheduler/+spec/health-check-job-vexpress >>> >>> > >>> >>> > >>> >>> > https://blueprints.launchpad.net/lava-test/+spec/ui-drive-test-for-android >>> >>> >>> >>> Whatever lands in the Android build should land across all targets at >>> >>> the platform level. The tests should also be integrated into the build >>> >>> so that people can run them manually. >>> >>> >>> >>> I think the first 3 BPs should be joined by other BPs that track >>> >>> health checks on the remaining targets. >>> >>> >>> >>> It looks like >>> >>> >>> >>> https://blueprints.launchpad.net/lava-test/+spec/ui-drive-test-for-android >>> >>> can be integrated into the build. We can put together a new git for >>> >>> it. Does: >>> >>> >>> >>> git://android.git.linaro.org/test/linaro/android/tema.git >>> >>> >>> >>> sound good? >>> >>> >>> >>> >>> >>> > BR >>> >>> > >>> >>> > /Chi Thu >>> >>> > >>> >>> > On 23 March 2012 11:56, Fathi Boudra <[email protected]> >>> >>> > wrote: >>> >>> >> On 23 March 2012 12:51, Alexander Sack <[email protected]> wrote: >>> >>> >>> On Thu, Mar 22, 2012 at 10:22:00PM -0500, Paul Larson wrote: >>> >>> >>>> On Thu, Mar 22, 2012 at 9:26 AM, Le.chi Thu >>> >>> >>>> <[email protected]> >>> >>> >>>> wrote: >>> >>> >>>> > Here is the blueprints I would like to work with in next cycle >>> >>> >>>> > and >>> >>> >>>> > the >>> >>> >>>> > highest first >>> >>> >>>> > >>> >>> >>>> > * health-check-job-vexpress (very small task) >>> >>> >>>> > * Include STE kernel test suite in LAVA and CI >>> >>> >>>> > >>> >>> >>>> The above two are good ones, I know the STE kernel suite has some >>> >>> >>>> issues to >>> >>> >>>> sort out wrt building though. >>> >>> >>> >>> >>> >>> Do we already have a blueprint with details about inclusion of the >>> >>> >>> STE >>> >>> >>> test suite in the backlog? in particular what is this "building" >>> >>> >>> problem about... >>> >>> >> >>> >>> >> Here's the blueprint: >>> >>> >> >>> >>> >> >>> >>> >> https://blueprints.launchpad.net/lava-test/+spec/linaro-validation-ste-kernel-testsuite >>> >>> >>> >>> >>> >>> >>> >>> -- >>> >>> Zach Pfeffer >>> >>> Android Platform Team Lead, Linaro Platform Teams >>> >>> Linaro.org | Open source software for ARM SoCs >>> >>> Follow Linaro: http://www.facebook.com/pages/Linaro >>> >>> http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog >>> >> >>> >> >>> >>> >>> >>> -- >>> Zach Pfeffer >>> Android Platform Team Lead, Linaro Platform Teams >>> Linaro.org | Open source software for ARM SoCs >>> Follow Linaro: http://www.facebook.com/pages/Linaro >>> http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog >> >> -- Zach Pfeffer Android Platform Team Lead, Linaro Platform Teams Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog _______________________________________________ linaro-validation mailing list [email protected] http://lists.linaro.org/mailman/listinfo/linaro-validation
