core tests coverage report 0%

by James Wang » Sat, 12 Dec 2009 16:48:53 GMT


Sponsored Links
 We ran core tests by the command "/development/testrunner/runtest.py  -
v --coverage core" and got coverage report successfully. But the
reports says all are 0%.
We ran apidemos and got coverage report which looks good.

Below is the console output for core tests:
-------------------------------------------------------------------------------------
No private recovery resources for TARGET_DEVICE dream-open
make:  `/usr/forCurl/android1.6r1' make: `files' 
make:  `/usr/forCurl/android1.6r1' Syncing to device...
about to run adb  sync
syncing /system...
0 files pushed. 377 files skipped.
syncing /data...
0 files pushed. 8 files skipped.

Waiting for device package manager...
about to run adb  wait-for-device
about to run adb  shell pm path android
about to run adb  shell cat init.rc | grep BOOTCLASSPATH | grep
emma.jar
Waiting for instrumentation to be present
about to run adb  shell pm list instrumentation | grep android.core/
android.test.InstrumentationTestRunner
Running in coverage mode, suppressing test output
am instrument -e class 'android.core.CoreTests' -e coverage 'true' -r -
w android.core/android.test.InstrumentationTestRunner
about to run adb  shell am instrument -e class
'android.core.CoreTests' -e coverage 'true' -r -w android.core/
android.test.InstrumentationTestRunner
Failure in android.webkit.CookieTest:testPath:
junit.framework.AssertionFailedError
        at android.webkit.CookieTest.testPath(CookieTest.java:191)
        at java.lang.reflect.Method.invokeNative(Native Method)
        at android.test.AndroidTestRunner.runTest(AndroidTestRunner.java:164)
        at android.test.AndroidTestRunner.runTest(AndroidTestRunner.java:151)
        at android.test.InstrumentationTestRunner.onStart
(InstrumentationTestRunner.java:425)
        at android.app.Instrumentation$InstrumentationThread.run
(Instrumentation.java:1520)


Tests run: 312, Failures: 1, Errors: 0
about to run adb  shell ls /data/data/android.core/files/coverage.ec
about to run adb  pull /data/data/android.core/files/coverage.ec /usr/
forCurl/android1.6r1/out/emma/framework/core/core.ec
EMMA: processing input files ...
EMMA: 2 file(s) read and merged in 503 ms
EMMA: writing [html] report to [/usr/forCurl/android1.6r1/out/emma/
framework/core/core.html] ...
Coverage report generated at /usr/forCurl/android1.6r1/out/emma/
framework/core/core.html
----------------------------------------------------------------

So I wonder why core tests's coverage report says 0% and how can I
make the report make sense.

Thanks in advance.

James

--



core tests coverage report 0%

by James Wang » Mon, 14 Dec 2009 09:03:30 GMT


 Hello, nobody had run core tests? Anybody can help me? Please!

--


Sponsored Links


Other Threads

1. How to use do xml c14n in android?

i find c14n support in libxml2, but not able to use it in java.
so, anyone help me? or i have to write jni myself to use it?

thanks

-- 
Bear ^O^

-- 

2. Can recognizer use a file for audio input?

I have been planning a test of that very action. I doubt the
recognition quality will be very good but I will post my results.
Certainly, performing the recognition on a prerecorded file would be
better but it doesn't appear possible within the confines of the SDK.
Hopefully I am just missing something though.




-- 

3. How to update G1 firmware version to 2.0?

4. Where can I catch a point that is assured to be called when a Service is destroied

5. Question about unit testing a seek bar's events

6. Help with Map

7. Getting an address from the contacts