Looks like you answered your own question, but yes, passing the "-r" flag gets you more parseable results. I don't believe the on device test runner records per-test execution times.
There is some existing code for parsing the output of adb shell am instrument -r in the Android source tree at development/testrunner and development/tools/ddms/libs/ddmlib/src/com/android/ddmlib/testrunner On Tue, Oct 6, 2009 at 11:27 AM, markwhitney <[email protected]> wrote: > > For reference to others, it turns out that passing the "-r" flag to > instrument produces more easily parseable results. It would still be > nice to get a full report with things like test runtimes though. > > On Oct 6, 9:21 am, markwhitney <[email protected]> wrote: >> Is there a way to get more easily parseable output from a test suite >> of ActivityUnitTestCases and ActivityInstrumentationTestCase2s? >> Possibly some extras passed to "adb am instrument"? >> >> The output of "am instrument" is fine for manual test runs, but I am >> looking for something more structured so that I can feed it into a >> continuous integration system. Maybe something like the XML reports >> produced by JUnit? Since the Android test framework is based on >> JUnit, is there a way to turn on such features? Or does this output >> already exist and I was looking in the wrong place on the filesystem? >> >> Note, I am not really looking for EMMA coverage reports (unless that >> also produces detailed test reports?), just unit test results. >> >> Thanks. > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
