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. contacts.extensions

Hi guys,
I'm trying to extend the contacts by adding additional fields to
contacts.people using contacts.extensions. My only problem is that have no
idea how to query the contacts.people using a join with contacts.extensions.
I'm not trying to modify/extend the contacts provider.

One very very ugly solution would be to query on contacts.extensions and
using the person ids to query the contacts.people (manual join) ... The idea
is to create an ListActivity which displays only the extended contacts.

I would like to be able to create a content provider that uses directly the
contacts.db (from the content provider) where i could use my join queries...
but from what I know this is not possible.

Do the content providers support joins? Or is there another way to create
this kind of joins?

One more thing... How can I use Contacts.People.Extensions?

Thanks

--~--~---------~--~----~------------~-------~--~----~

2. Spinner setSelection(int) problem

Hi all,
I have a spinner in a dialog. Calling spinner.setSelection(int)
correctly sets the spinner just after opening the app. If I reopen the
dialog after making another spinner.setSelection(int) call, the
spinner shows the first item regardless of the selection being set,
BUT...

clicking on the spinner shows that the correct value is selected in
the list of options (green dot next to the item). Weird huh? Sometimes
when this happens, the spinner is cutting off parts of the text. Has
anyone else seen this happen?
--~--~---------~--~----~------------~-------~--~----~

3. Implementing a custom Suggestions Provider

4. How to get image file from Google Chart API

5. Playing Audio in web apps on Android

6. Saving images from MMS

7. Any Android Suggestion Page