Linaro Android

Qualify and automate Gtest based-tests

Registered by Zygmunt Krynicki

Why:

AOSP uses googletest (http://code.google.com/p/googletest/) a C++ testing framework for lots of the native (non-dalvik/java) test code. googletest has very regular test output and would be very simple to automate. We should understand what is the value of automating those tests by qualifying them (by describing what they test, how long does it take to execute, etc) and writing a common wrapper for them.

Where:
Most likely in lp:linaro-android-test as a new test (gtest) that takes parameters describing which executable to run and which parameters to pass to it (gtest-based tests can be ran selectively)

Who:
Zygmunt Krynicki (zyga)

Context:
The testing card

Blueprint information

Status:
Complete
Approver:
Zach Pfeffer
Priority:
Undefined
Drafter:
Zygmunt Krynicki
Direction:
Needs approval
Assignee:
Zygmunt Krynicki
Definition:
Obsolete
Series goal:
None
Implementation:
Implemented
Milestone target:
None
Started by
Zygmunt Krynicki
Completed by
Zygmunt Krynicki

Related branches

Sprints

Whiteboard

[2012-09-10 zkrynicki] This is pretty much implemented although not as described here.

(?)

Work Items

Work items:
Create spreadsheet with all native tests, their description, run parameters and ease of use: TODO
Attempt to run all native tests on a panda (locally): DONE
Add new stub test for lava-android-test: DONE
Add support for running the test with adb to capture return status: DONE
Add support for parsing output for fine grained test-case data: DONE
Land new lava-android-test branch to trunk: DONE
[doanac] Deploy new lava-android-test: TODO
Alter the jenkins script to support LAVA_GTEST_LIST (to define which tests to run): POSTPONED
Alter out test plans to run gtests on all builds: TODO

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.
Edit subscription

Subscribers

No subscribers.