History log of /development/testrunner/test_defs/native_test.py
Revision Date Author Comments
13a2fcf30d46a05f750ab18cb165167678b1fc14 11-Feb-2010 Nicolas Catania <niko@google.com> Added gtest to the list. cd to /sdcard before running native tests.

Some test need to be run in a place where they can write on the disk.
I know we should stop using /sdcard but until I see the new document
explaining how the launcher can access the playground, we are going
to keep it that way.
2c8ead32c7ebf08db568e2e9d5dbb3738ac69797 13-Nov-2009 Jean-Baptiste Queru <jbq@google.com> eclair snapshot
e00595bdbe62793778744ecaf4e95981d50724c6 22-Oct-2009 Brett Chabot <brettchabot@android.com> Remove runtest dependency on current dir being build top.

This change is necessary to support relative path based args.
924c0898792f4e14eb87a91a8e30d7138fb68be0 21-Oct-2009 Brett Chabot <brettchabot@android.com> Refactor runtest test_defs to allow programmatic creation.

Previously a test definition could only be created via xml.
Also fix some minor lint warnings.
12ad9fb10e1be799fa47a56ee1f1429b761db6e6 14-Aug-2009 Xia Wang <xiaw@google.com> 1. Add .c extension to native_test.py so that native test in C can also be picked up by testrunner.
2. Add netkeystore_test into continuous test cycle.
bf7863ec271cad3a8636bf7569963e7b3debaa51 30-Jun-2009 Brett Chabot <brettchabot@google.com> runtest: Remove run_command -> android_build dependency.

This is desired because run_command is used by puppetmaster which should have
no dependency on android build system.
3ae5f8a399ef9b4e930b988040f86f403e27c7f0 28-Jun-2009 Brett Chabot <brettchabot@google.com> Fix relative class path arg handling in runtest, and some lint errors.
764d3fa70d42a79e2ee999b790e69fc55f12bf61 26-Jun-2009 Brett Chabot <brettchabot@google.com> Add support for running host java tests to runtest.

With this change, also refactored runtest as follows: Modified the
test suite schema and python implementation to have an inheritance
structure. Each test type has its own python module, which will
also handle the logic of running the test.