Hi Brett
On Oct 27, 6:18 pm, Brett Chabot brettcha...@android.com wrote:
Hi all:
In case you missed its mention in the release notes, I just wanted to point
out that version 3 of the Android SDK tools, and the Android 2.0 platform
5. Run 'ant coverage'
I'm trying this with 1.6r1 SDK
Hi all:
In case you missed its mention in the release notes, I just wanted to point
out that version 3 of the Android SDK tools, and the Android 2.0 platform
now support code coverage through the ant build system. In addition there
are a couple new commands in SDK tools version 3: 'android
Hi all,
Here are the steps how to create an emma instrumented APK in SDK!!!
(emma.jar is required !!!) You don't need to use android source tree
anymore.
- compile the source code
- instrument the code with emma
- generate android byte code
- create APK
- sign it
To run the test you have to
On Thu, Aug 27, 2009 at 7:53 PM, duykhamduyk...@gmail.com wrote:
Hi guys,
Many thanks for your supports, it's now working with automatic test.
(adb shell am instrument ...) :) But, I have some questions that,
1. Is there a way to get EMMA code coverage with manual test? I mean,
we can
Hi Santosh,
When you are starting the emulator it is ok to stop the booting
process, because there is no emma.jar file installed on the system.
The emulator tries to find the missing file every ~5 secs. So if you
are executing the adb remount and adb sync it will continue booting
up. (it
Hi guys,
Many thanks for your supports, it's now working with automatic test.
(adb shell am instrument ...) :) But, I have some questions that,
1. Is there a way to get EMMA code coverage with manual test? I mean,
we can test android by ourselves and after that, get the coverage
report for
Hi,
After starting the emulator,
i tried adb sync
but i am getting the error like device offline...
can you plz help me in this
Thanks
Santosh
On Aug 26, 6:39 am, santosh kumar santosh.1...@gmail.com wrote:
Hi All,
I have few questions about this.. plz clarify me..
i want to generate
Santosh
After starting the emualtor...do
#adb shell Once you can get to the console(it may take few secondsyou
will get device offline initially),
exit from adb shell;do adb remount and then adb sync
regards
Haritha
On Wed, Aug 26, 2009 at 12:07 AM, santosh kumar
Hi All,
what changes you have been done to vold.conf?
and i followed the steps of gobor..
but for me also, emulator is getting stucked..
can you plz help me..
On Aug 25, 2:23 am, Haritha hari.andr...@gmail.com wrote:
thanks everyone for posting info on emma coverage.I was also able to
hi
i was not facing any issues with emulator.Only thing was my coverage.ec file
was empty as my sdcard is not recognised.with the following steps the issues
was resolved.If possible post the logcat o/p and also the steps followed.
1) edit system/core/rootdir/Android.mk so that the copy_from
Hi All,
I have few questions about this.. plz clarify me..
i want to generate code coverage for apidemos only...
first i changed init.rc then i followed every thing which is mentioned
in gobor mail..
one thing i am not understanding... when i start the emulator,
emulator is getting stucked
Just to follow that up, I was able to get it working as well for a
custom project (thanks Gabor!). I had to make some minor changes to
the instructions to get it all to work for me, particularly with the
SDCard on cupcake. If folks are interested, here's what I did:
hey Gabor,
thanks a lot for your help.
Actually i tried reproducing the same steps, it is working fine till
emulator starts, it launches emulator but it does not shows the home
screen
i tried steps after that, doing adb remount and adb sync, it pushes
all the neccessay files into the emulator,
Thanks Gabor, indeed it's a very useful information.
Am getting an error while building the project, it says:
make: *** [out/host/linux-x86/obj/EXECUTABLES/emulator_intermediates/
android/skin/window.o] Error 1
seems some problem with emulator skin.
Have you faced this, or else can you let me
has anyone stuck with the problem on android OS not booting while
launching emulator showing error that can not specify non '.' in your
classpath,
unable to launch dalvikvm
On Aug 20, 6:08 pm, Gabor gabor.andr...@googlemail.com wrote:
Hi All,
Finally, the emmacodecoveragemeasurement is
thanks everyone for posting info on emma coverage.I was also able to
generate coverage reports for custom tests with necessary changes to
vold.conf.
regards
Haritha
On Aug 20, 6:08 am, Gabor gabor.andr...@googlemail.com wrote:
Hi All,
Finally, the emma code coverage measurement is working for
Hi All,
Finally, the emma code coverage measurement is working for me (for a
custom project). So here are the steps what you need to make it work
(I have tested it, with Java 1.5 on Ubuntu 8.04):
mkdir android-src
cd android-src
repo init -u git://android.git.kernel.org/platform/manifest.git -b
Comments inclosed
On Tue, Aug 18, 2009 at 9:16 PM, duykhamduyk...@gmail.com wrote:
Hi Brett,
Thanks for your help. But, for me, there's something not clearly, so
that I need more supports from you.
1. Firstly, as you said,
Before doing a build, set
export EMMA_INSTRUMENT=true
a. Did
Hi Brett,
Thanks for your help. But, for me, there's something not clearly, so
that I need more supports from you.
1. Firstly, as you said,
Before doing a build, set
export EMMA_INSTRUMENT=true
a. Did you mean doing a build is building entire source code of
Android or just re-making images?
Haritha,
I think you got the issue of SD card. It is not writable, so that the
coverage.ec can not be saved into SDcard.
You can get more detail about this issue here:
https://review.source.android.com/#change,9452
Hope this helps.
BR.
Haritha のメッセージ:
Brett
first of all thanks for all the
Brett
first of all thanks for all the information on Emma coverage.
I have written my own instrument testcase for Setting app and added
these to /packages/apps/Settings/tests/
with export EMMA_INSTRUEMNT=true;and mmm packages/apps/Setting
coverage.em,Settings.apk,SettingsTests.apk are generated.
Hi Brett,
Thanks a lot for all the info provided!!! I was missing some of the steps
you mentioned, that is why it was not working well over here. Even knowing
that the EMMA support is quite preliminary, I will certainly give it a try.
UT + code coverage are really important to help us obtain
+ android-platform
Its great to see people interested in EMMA code coverage on Android.
However, note that EMMA code coverage support on Android is currently quite
preliminary. Its not supported from within the SDK yet. The support that is
in place is for apps and tests that are part of the
Hi Deeps,
Nice to hear that you are making progress. Are you using only the SDK, or
are you building the entire android source code? Maybe your code is not
instrumented to generate the coverage statistics and this would be why you
are getting 0% of code coverage. Are you using the emma.jar
Thanks a lot Felipe.
Yeah..I have included emma.jar in the build path of my application.
I have the android latest release 1.5 sdk.. However, my application
has 1.1 target. I tried using Android JUnit and found all my test
cases are executed.
And also throu command prompt i followed the syntax
Felipe,
Atlast i am half way through in getting the coverage file. But..I dont
see any required output in that file.
I created a sdcard. Then i run my Instrumentation with the following
command,
# am instrument -e coverage true -w com.app.exam.tests/
android.test.InstrumentationTestRunner
Felipe Ramos,
Did u end up somewhere..? I am not able to go ahead with this..
deeps
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to
Hi deeps,
I'm stuck on the point where I need to run the instrumented tests on
the emulator. I could not find a way yet to make the emulator believe
that the emma.jar is already installed on it.
Also, I don't know if there is a way of enabling EMMA instrumentation
using the SDK. I have not
Hi everyone
I discovered a way of getting the android code instrumented, using the
full source from google.
On the project Android.mk I added the line EMMA_INSTRUMENT:=true and
voilá, it instrumented the code. Now I'm facing problems to run the
instrumented code. Although emma.jar is inside the
Hi guys,
I don't know if this thread is still active, but I spent some hours
trying to make the EMMA instrumented code generation works.
I actually came pretty close of getting it, I think. You can use the
EMMA_INSTRUMENT:=true on the project Android.mk file to turn on the
EMMA instrumentation
1. did you download and set classpath for emma.jar?
2. after that, you could get coverage.ec file.
But it's not right file for coverage report in my test. Perhaps other
things need to be done.
currently I don't know how to get an emma instrumented build, which is
needed for coverage test.
On
I as well am looking to understand how o build an emma instrumented test.
I am unable to find any information on EMMA through SDK or through the web.
Maybe the three of us can pool our resources and keep this thread alive to
a.) get noticed, b.) get some code coverage.
For those catching on:
32 matches
Mail list logo
