summaryrefslogtreecommitdiffstats
path: root/tools/dalvik_jtreg/java/dalvik/jtreg/Driver.java
Commit message (Collapse)AuthorAgeFilesLines
* Rename dalvik_jtreg to dalvik_runner.Jesse Wilson2009-12-171-205/+0
| | | | Now that it runs caliper and JUnit, the old name was awful clumsy.
* Cleaning up after each test to avoid exhausting disk space.Jesse Wilson2009-12-171-14/+25
| | | | Moving tests to the local sdcard.
* Adding some debugging to help figure out why our tests aren't completing.Jesse Wilson2009-12-161-1/+15
|
* Making helper threads daemons in the jtreg runner.Jesse Wilson2009-12-161-3/+1
| | | | | Fixing a bug where we were attempting to execute errord out tests. And renaming the testClasses to a testClasspath.
* Support running caliper with the jtreg runner. This is an early first look;Jesse Wilson2009-12-101-8/+14
| | | | we'll need to fix a few things before the UI for this is nice.
* More jtreg+JUnit love. Getting JUnit to work off-device.Jesse Wilson2009-12-021-1/+2
| | | | Also fixing the number of threads used by the driver.
* JUnit support for jtreg runner. This makes it so that a single commandJesse Wilson2009-12-021-0/+175
will compile a focused set of tests, install them on the device, and run them. There are still some features missing in the current test runner: - it requires JUnit to be compiled manually "mmm external/junit". I'm trying to figure out why our build system cannot find it. - it requires the full test suite already be on the device. This is necessary for the support test files and annotations. I intend to create a follow up change to move those into a smaller target. For now "mmm dalvik snod" will build these. - JUnit test expectations are at the class level, not the method level. I don't yet have a mechanism to introspect the .java file from JUnit to get its method-level detail. - jtreg tests can only be run as a directory, not as a single test.