Wednesday, July 13, 2011

[android-developers] Re: Error: Failed to generate emma coverage.

You build is probably not instrumented and thus why coverage
information is not generated.
Chapter 10 of Android Application Testing Guide (http://
www.packtpub.com/android-application-testing-guide/book) includes a
step-by-step guide of getting your build instrumented and generating
code coverage.
Hope this helps.

On Jul 12, 6:25 am, erinwon <erin...@gmail.com> wrote:
> Recently I am in a android development group and in charge of the test
> work.
> I do my test work automatically under the robotium framework. In order
> to get code coverage for my Robotium tests, I use ant to make this
> under the instruction ofhttp://code.google.com/p/robotium/wiki/QuestionsAndAnswers#How_can_I_...
> andhttp://dev.10086.cn/cmdn/wiki/index.php?edition-view-5456-1.html
> (sorry, this page is in Chinese).
>
> Step by step, I passed the "ant debug" and "ant run-tests"
> successfully. I almost achieved the result ,yeh!
> However when I runned "ant coverage" and everything seems went
> smoothly, the tragedy happend finally.
> The hints as follows:
>
>  [exec] Error: Failed to generate emma coverage.
>  [echo] Downloading coverage file into project directory...
>  [exec] remote object '/data/data/com.appleJuice/files/coverage.ec'
> does not exist
>
> PS: the test  are successfully passed and the test_rules.xml under the
> android sdk is no problem
>
> The information about the emma of android test is very limit in the
> Internet and I get no help
> Here is my last resort. Help!!!

--
Have you read my blog ?
http://dtmilano.blogspot.com
android junit tests ui linux cult thin clients

--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

No comments:

Post a Comment