Include Android device configuration in test output

[Google Code Exporter]

The included patch writes a bunch of properties from the Android device 
configuration to the XML report. The device and OS identification properties 
should be useful in any case. The screen configuration entries are a bit 
questionable, because these may change during the test run; you may want to 
strip these from the patch. I think they're useful to have.

I had to change the targetSdkVersion to 16 to reveal some of the latest 
constants like DisplayMetrics.DENSITY_XXHIGH. These constants will not fail at 
runtime on an older device because primitive constants are compiled into the 
class file (just like newer VERSION_CODES in a typical SDK_INT check).

Original issue reported on code.google.com by barend.garvelink on 17 Jul 2013 at 6:44

Attachments:

• the-missing-android-xml-junit-test-runner-properties.patch

[Google Code Exporter]

Thanks for that. The patch is applied now. Very useful. Sorry for so late 
patching, been pretty busy or absent recently.

Original comment by [e-mail] on 29 Aug 2013 at 5:20

• Changed state: Fixed
• Added labels: Type-Enhancement
• Removed labels: Type-Defect