Re: Code Coverage

[Colin Alworth]

> I haven't been using maven to run my tests in the past (because I don't
want them package into the war and increasing the size of the war) now I'm
struggling to get maven to build and run my tests at all. They're in a
separate folder outside of src.

I guess I don't understand this part - if maven doesn't know about the test
sources, it makes a certain amount of sense that mvn emma:emma does
nothing. Additionally, if those sources are reported to maven as test
sources, they should never make it to the compiled war.

The standard maven project setup for a war project looks a little like
this, give or take (with added bits for GWT), including a single test class:
project/
  pom.xml
  src/
main/
  webapp/
index.html
WEB-INF/...
  java/
com/company/project/
  Project.gwt.xml
  server/...
  client/...
  shared/...
test/
  java/
com/company/project/client/MyTest.java

The important details here are that the test sources are not in the
src/main/java tree at all, so maven should never be building them into the
war file. Its possible your IDE (esp if that IDE is eclipse...) is cheating
a bit, but no maven process will make that mistake.

With this standard setup, the emma:emma goal seems to behave on maven 2.2
or so. Can you clarify on how you are setting your project up, and perhaps
make/share a sample project? I'll see if I can find/share a sample on
github that demonstrates working emma coverage, given these basic setup
details.



On Wed, Mar 13, 2013 at 10:57 AM, darkling  wrote:

> Do you mean you're using the surefire test goal or the gwt:test goal?
>
> I've spent a few days trying to get either working without much luck. I
> haven't been using maven to run my tests in the past (because I don't want
> them package into the war and increasing the size of the war) now I'm
> struggling to get maven to build and run my tests at all. They're in a
> separate folder outside of src.
>
> Which maven goal approach did you take to running emma?
> Thanks
>
>
> On Friday, March 8, 2013 6:13:11 PM UTC-5, Colin Alworth wrote:
>>
>> We've been using the Maven2 emma:emma goal, with no modifications at all
>> - seems to behave correctly with htmlunit in dev mode, both for traditional
>> junit tests and GWTTestCases. No changes to the pom, just executing
>> emma:emma with maven 2.2.1 on our project.
>>
>> On Thursday, March 7, 2013 11:01:37 AM UTC-6, darkling wrote:
>>>
>>> Does anyone have any recent experience working with a code coverage tool
>>> and GWT? I heard that emma worked so I downloaded the eclipse emma plugin
>>> and gave it a whirl. The problem is it only seems to tell me that no line
>>> of mine was ever touched. I tried running it on my nonGWT code and it seems
>>> to work fine. But GWT gives me no answers. I read a post saying that the
>>> emma approach doesn't work with the latest version of GWT (I am using 2.4)
>>> can anyone confirm or deny this?
>>> Thanks
>>>
>>>

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Code Coverage

[darkling]

Do you mean you're using the surefire test goal or the gwt:test goal?

I've spent a few days trying to get either working without much luck. I 
haven't been using maven to run my tests in the past (because I don't want 
them package into the war and increasing the size of the war) now I'm 
struggling to get maven to build and run my tests at all. They're in a 
separate folder outside of src.

Which maven goal approach did you take to running emma?
Thanks

On Friday, March 8, 2013 6:13:11 PM UTC-5, Colin Alworth wrote:
>
> We've been using the Maven2 emma:emma goal, with no modifications at all - 
> seems to behave correctly with htmlunit in dev mode, both for traditional 
> junit tests and GWTTestCases. No changes to the pom, just executing 
> emma:emma with maven 2.2.1 on our project.
>
> On Thursday, March 7, 2013 11:01:37 AM UTC-6, darkling wrote:
>>
>> Does anyone have any recent experience working with a code coverage tool 
>> and GWT? I heard that emma worked so I downloaded the eclipse emma plugin 
>> and gave it a whirl. The problem is it only seems to tell me that no line 
>> of mine was ever touched. I tried running it on my nonGWT code and it seems 
>> to work fine. But GWT gives me no answers. I read a post saying that the 
>> emma approach doesn't work with the latest version of GWT (I am using 2.4) 
>> can anyone confirm or deny this?
>> Thanks
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Code Coverage

[Colin Alworth]

We've been using the Maven2 emma:emma goal, with no modifications at all - 
seems to behave correctly with htmlunit in dev mode, both for traditional 
junit tests and GWTTestCases. No changes to the pom, just executing 
emma:emma with maven 2.2.1 on our project.

On Thursday, March 7, 2013 11:01:37 AM UTC-6, darkling wrote:
>
> Does anyone have any recent experience working with a code coverage tool 
> and GWT? I heard that emma worked so I downloaded the eclipse emma plugin 
> and gave it a whirl. The problem is it only seems to tell me that no line 
> of mine was ever touched. I tried running it on my nonGWT code and it seems 
> to work fine. But GWT gives me no answers. I read a post saying that the 
> emma approach doesn't work with the latest version of GWT (I am using 2.4) 
> can anyone confirm or deny this?
> Thanks
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Code Coverage

[Thomas Broyer]

JBoss has a jacoco-gwt-maven-plugin but I haven't tried it.

On Thursday, March 7, 2013 6:01:37 PM UTC+1, darkling wrote:
>
> Does anyone have any recent experience working with a code coverage tool 
> and GWT? I heard that emma worked so I downloaded the eclipse emma plugin 
> and gave it a whirl. The problem is it only seems to tell me that no line 
> of mine was ever touched. I tried running it on my nonGWT code and it seems 
> to work fine. But GWT gives me no answers. I read a post saying that the 
> emma approach doesn't work with the latest version of GWT (I am using 2.4) 
> can anyone confirm or deny this?
> Thanks
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Code Coverage

[darkling]

I did but it didn't work for me. Did it work for you?
Thanks

On Thursday, March 7, 2013 12:07:33 PM UTC-5, Jens wrote:
>
> Have you used the patched GWT emma version?
>
> Take a look at: 
> https://developers.google.com/web-toolkit/doc/latest/DevGuideTestingCoverage
>
> -- J.
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Code Coverage

[Jens]

Have you used the patched GWT emma version?

Take a look at: 
https://developers.google.com/web-toolkit/doc/latest/DevGuideTestingCoverage

-- J.


-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Code Coverage

[darkling]

Does anyone have any recent experience working with a code coverage tool 
and GWT? I heard that emma worked so I downloaded the eclipse emma plugin 
and gave it a whirl. The problem is it only seems to tell me that no line 
of mine was ever touched. I tried running it on my nonGWT code and it seems 
to work fine. But GWT gives me no answers. I read a post saying that the 
emma approach doesn't work with the latest version of GWT (I am using 2.4) 
can anyone confirm or deny this?
Thanks

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Code Coverage : How to integrate selenium,cobertura with gwt client project for code coverage report.

[Darsha Sai]

Hi,

I am using gwt client application.

I interested in selenium automated test case in my project.

I want to use cobertura for code coverage in my project with Selenium
auto mated test case .

How can integrate these two tools for my gwt client project ?

Thanks in advance.

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

Re: Code Coverage : How to configure cobertura and selenium with Gwt Client project for code coverage

[Joseph Lust]

Dodo,

We get around that by setting unique id's on elements using a 'debugId' for 
components that need to be individually tested. This helps prevent making 
brittle tests that depend on a very long XPath that will break if any class 
is renames or div moved.

You can set them in the UiBinder as just debugId="value" up to GWT 2.3, 
there after you need to programmaticly set them in the Java side.

Sincerely,
Joe

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-web-toolkit/-/evYs4N0PhOwJ.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: Code Coverage : How to configure cobertura and selenium with Gwt Client project for code coverage

[Joseph Lust]

Thomas,

Thanks for the tip. I'll rebuild GWT and Emma when I get home with these 
flags tonight.

Sincerely,
Joseph

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-web-toolkit/-/rZfbTCi2cZMJ.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: Code Coverage : How to configure cobertura and selenium with Gwt Client project for code coverage

[dodo dard]

I've work with GWT and Selenium separately, But to make Selenium 
work, basically you have set and unique id to the component that you want 
to test.  But then for Cobertura, I dont know

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-web-toolkit/-/Zk0JsB6ysD8J.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: Code Coverage : How to configure cobertura and selenium with Gwt Client project for code coverage

[Thomas Broyer]

I never used it. I know GWT can be built with EMMA enabled for the tests 
(ant -Demma.enabled=true), I haven't run it for a while but I believe it 
still works.
The patch is here, with the instructions for re-building EMMA in the 
README.txt: 
http://code.google.com/p/google-web-toolkit/source/browse/tools/redist/emma/

On Wednesday, March 28, 2012 4:58:17 AM UTC+2, Joseph Lust wrote:
>
> Thomas,
>
> Have you ever used the patched Emma plugin? I've got the Emma 2.1.0.201 
> installed while the 'patched' version is 2.0.5312. I tried swapping things 
> out like the docs suggested to no avail. Curious if anyone else has made 
> that work in Indigo (Ubuntu 11.10).
>
> I've long used Emma with pure Java, but it does not work on GWTTestCase. I 
> can run the case or suite with *RunAs>GWT JUnit Test*, but using Emma or 
> *Coverage 
> As > JUnit Test *always throws:
>
> com.google.gwt.junit.JUnitFatalLaunchException: The test class 
> 'com.myPkg.myClass' was not found in module 'com.myPkg.MyModule'; no 
> compilation unit for that type was seen
> at 
> com.google.gwt.junit.JUnitShell.checkTestClassInCurrentModule(JUnitShell.java:743)
> at com.google.gwt.junit.JUnitShell.runTestImpl(JUnitShell.java:1346)
> at com.google.gwt.junit.JUnitShell.runTestImpl(JUnitShell.java:1309)
> at com.google.gwt.junit.JUnitShell.runTest(JUnitShell.java:653)
> at com.google.gwt.junit.client.GWTTestCase.runTest(GWTTestCase.java:441)
> at junit.framework.TestCase.runBare(TestCase.java:134)
> at junit.framework.TestResult$1.protect(TestResult.java:110)
> at junit.framework.TestResult.runProtected(TestResult.java:128)
> at junit.framework.TestResult.run(TestResult.java:113)
> at junit.framework.TestCase.run(TestCase.java:124)
> at com.google.gwt.junit.client.GWTTestCase.run(GWTTestCase.java:296)
> at junit.framework.TestSuite.runTest(TestSuite.java:243)
> at junit.framework.TestSuite.run(TestSuite.java:238)
> at junit.framework.TestSuite.runTest(TestSuite.java:243)
> at junit.framework.TestSuite.run(TestSuite.java:238)
> at 
> org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:130)
> at 
> org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
> at 
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
> at 
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
> at 
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
> at 
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)
>
> Perhaps the patch needs to be updated? I can build it myself, but did not 
> see a reference to the patch on the Google 
> page
> .
>
>
> Sincerely,
> Joseph
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-web-toolkit/-/0CmrSzKe2HQJ.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: Code Coverage : How to configure cobertura and selenium with Gwt Client project for code coverage

[Joseph Lust]

Thomas,

Have you ever used the patched Emma plugin? I've got the Emma 2.1.0.201 
installed while the 'patched' version is 2.0.5312. I tried swapping things 
out like the docs suggested to no avail. Curious if anyone else has made 
that work in Indigo (Ubuntu 11.10).

I've long used Emma with pure Java, but it does not work on GWTTestCase. I 
can run the case or suite with *RunAs>GWT JUnit Test*, but using Emma or 
*Coverage 
As > JUnit Test *always throws:

com.google.gwt.junit.JUnitFatalLaunchException: The test class 
'com.myPkg.myClass' was not found in module 'com.myPkg.MyModule'; no 
compilation unit for that type was seen
at 
com.google.gwt.junit.JUnitShell.checkTestClassInCurrentModule(JUnitShell.java:743)
at com.google.gwt.junit.JUnitShell.runTestImpl(JUnitShell.java:1346)
at com.google.gwt.junit.JUnitShell.runTestImpl(JUnitShell.java:1309)
at com.google.gwt.junit.JUnitShell.runTest(JUnitShell.java:653)
at com.google.gwt.junit.client.GWTTestCase.runTest(GWTTestCase.java:441)
at junit.framework.TestCase.runBare(TestCase.java:134)
at junit.framework.TestResult$1.protect(TestResult.java:110)
at junit.framework.TestResult.runProtected(TestResult.java:128)
at junit.framework.TestResult.run(TestResult.java:113)
at junit.framework.TestCase.run(TestCase.java:124)
at com.google.gwt.junit.client.GWTTestCase.run(GWTTestCase.java:296)
at junit.framework.TestSuite.runTest(TestSuite.java:243)
at junit.framework.TestSuite.run(TestSuite.java:238)
at junit.framework.TestSuite.runTest(TestSuite.java:243)
at junit.framework.TestSuite.run(TestSuite.java:238)
at 
org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:130)
at 
org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
at 
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
at 
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
at 
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
at 
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)

Perhaps the patch needs to be updated? I can build it myself, but did not 
see a reference to the patch on the Google 
page
.


Sincerely,
Joseph

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-web-toolkit/-/vYsbjwrXaM8J.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: Code Coverage : How to configure cobertura and selenium with Gwt Client project for code coverage

[Thomas Broyer]

On Monday, March 26, 2012 2:47:49 PM UTC+2, Sun Raise wrote:
>
> Hi, 
>
> I am using GWT client side project. 
>
> I am interesting selenium automated test case in my project. 
>
> For code coverage i want to use cobertura. 
>
>
> How to configure these 2 tools in gwt client ? 
>
> Its it possible or not ?
>

AFAIK, only EMMA (a *patched* version of EMMA) can be used for measuring 
code coverage in client code.
See 
https://developers.google.com/web-toolkit/doc/latest/DevGuideTestingCoverage

As for Selenium, I'm sorry, I never took the time to use it. IIUC, you'd 
have to launch the DevMode with EMMA-enhanced classes, and then point your 
browser (controlled by Selenium) to it to run the tests.

If you use Maven, you'd launch the DevMode in the pre-integration-test 
phase and run the selenium tests in the integration-test phase; then stop 
the DevMode in the post-integration-test phase and process the EMMA reports 
and test reports in the verify phase. The gwt-maven-plugin could have 
helped you launch the DevMode, but AFAIK it's blocking, so it actually 
won't help.

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-web-toolkit/-/A6C1R3e4MnIJ.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Code Coverage : How to configure cobertura and selenium with Gwt Client project for code coverage

[Sun Raise]

Hi,

I am using GWT client side project.

I am interesting selenium automated test case in my project.

For code coverage i want to use cobertura.


How to configure these 2 tools in gwt client ?

Its it possible or not ?

Thanks

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

Re: Cobertura code coverage with HtmlUnit/DevMode

[Damien Picard]

After reading the CompilingClassLoader source code, especially its
findClassBytes method, I see that the bytecode is generated on-the-fly by
the DevMode ; if Emma is available, the loader tries to load instrumented
bytecode from the disk (EmmaStrategy) and replace, if possible (no JSO or
JSNI, instrumented class available, ...), the jdt generated bytecode by this
one.

As a matter of fact, this bytecode has to be compatible with jdt-compiled
one, because it has to be executed with some jdt-compiled unit.
So, the only way to make Cobertura code coverage available is to create a
patch for CompilingClassLoader which looks like the Emma one, and doing the
same stuff.
In order to don't have to map anonymous types and JSNI method between JDT
and Javac bytecode, maybe Cobertura can instrument JDT bytecode. But I will
look for this later.

And I will try to replace Cobertura with Emma before trying this :p

2011/5/10 Damien Picard 

> I do, and it seems that the Emma distribution is patched in order to fix a
> classpath issue (according to README.txt).
>
> README.txt :
> *emma-multiclassloader-fix.patch: the patch to the emma src to
> get aroud the classloader issue.
> *
> But I can't find where the DevMode .class files are instrumented.
> According to Emma's GWT documentation, launching devmode (i.e. ant
> devmode), seems to generate all classes files to a desired path. I will try
> to instrument these files and launching the test with this classpath in a
> maven goal.
>
> Hope this will work !
>
>
> 2011/5/10 Thomas Broyer 
>
>> GWT already supports EMMA for code coverage, did you look at how it works?
>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Google Web Toolkit" group.
>> To post to this group, send email to google-web-toolkit@googlegroups.com.
>> To unsubscribe from this group, send email to
>> google-web-toolkit+unsubscr...@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/google-web-toolkit?hl=en.
>>
>
>
>
> --
> Damien Picard
> Axeiya Services : http://axeiya.com/
> gwt-ckeditor : http://code.google.com/p/gwt-ckeditor/
> Mon livre sur GWT : http://axeiya.com/index.php/ouvrage-gwt.html
>
>


-- 
Damien Picard
Axeiya Services : http://axeiya.com/
gwt-ckeditor : http://code.google.com/p/gwt-ckeditor/
Mon livre sur GWT : http://axeiya.com/index.php/ouvrage-gwt.html

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

Re: Cobertura code coverage with HtmlUnit/DevMode

[Damien Picard]

I do, and it seems that the Emma distribution is patched in order to fix a
classpath issue (according to README.txt).

README.txt :
*emma-multiclassloader-fix.patch: the patch to the emma src to
get aroud the classloader issue.
*
But I can't find where the DevMode .class files are instrumented.
According to Emma's GWT documentation, launching devmode (i.e. ant devmode),
seems to generate all classes files to a desired path. I will try to
instrument these files and launching the test with this classpath in a maven
goal.

Hope this will work !

2011/5/10 Thomas Broyer 

> GWT already supports EMMA for code coverage, did you look at how it works?
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google Web Toolkit" group.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> To unsubscribe from this group, send email to
> google-web-toolkit+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-web-toolkit?hl=en.
>



-- 
Damien Picard
Axeiya Services : http://axeiya.com/
gwt-ckeditor : http://code.google.com/p/gwt-ckeditor/
Mon livre sur GWT : http://axeiya.com/index.php/ouvrage-gwt.html

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

Re: Cobertura code coverage with HtmlUnit/DevMode

[Thomas Broyer]

GWT already supports EMMA for code coverage, did you look at how it works?

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

Cobertura code coverage with HtmlUnit/DevMode

[Damien Picard]

Hi,

I'm trying to generate code coverage report with Cobertura on GWTTestCases.
To do that, I would like to run these tests with the standard GWTRunner with
HtmlUnit.

As the Cobertura documentation says, the coverture is calculated using
instrumentations added to .class files in a first step, and then by using
this instrumented code in the tests.
As the GWT documentation says, the tests are, by default, launched in the
DevMode, which uses real .class files to execute the tests ; except for
Javascript native code (JSNI) that is transfered to the browser by the
DevMode (In this case, HtmlUnit will handle this code).

So, I think I could have code coverage on these DevMode .class files if I
can instrument them with Cobertura. I've seen that the Cobertura
instrumentation path can be given as a parameter to the instrumentation
step, and I would like to point the cobertura instrumentation step at the
.class files generated by the DevMode.

But, after reading the DevMode source code, it seems that .class files are
generated dynamically (with jdt) and added on-the-fly to the class loader.

Is there a way to generate DevMode .class files ahead of time, allowing me
to try an instrumentation with Cobertura ?

Thank in advance.

-- 
Damien Picard
Axeiya Services : http://axeiya.com/
gwt-ckeditor : http://code.google.com/p/gwt-ckeditor/
Mon livre sur GWT : http://axeiya.com/index.php/ouvrage-gwt.html

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

Problem of collecting GWT client Code coverage

[Qi Zhang]

We are trying to use the emma library to measure the code coverage of gwt
client code, our test case is driven by Selenium RC.

But we observed that some event handler code is never covered although we
are pretty sure the event is triggered and handled.

We did some hack to GWT source code and add some print code at
com.google.gwt.dev.shell.EmmaStrategy.java.

It is surprising that the PreinstrumentedEmmaStrategy did not select the
emma instrumented class sometimes, because the timestamp check failed.

(source code is newer than the instrumented code).

I suspect there is some bug there, but I am not sure.

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

Re: GWT 2.0 and EclEmma code coverage

[Nir Feldman]

I am facing the same issue exactly.

On Jan 28, 10:09 am, CVdS  wrote:
> Hi All,
>
> Did someone manage to correctly run EclEmma code coverage with GWT
> 2.0?
>
> I tried it many times with Eclipse 3.5, with both EclEmma 1.3.2 and
> 1.4.3, both updated (with emma.jar published on the GWT site) and not,
> the results are always the same:
>
> The console says something like
> [WARN]
> com.crofthawk.mgmt.Management.JUnit:com.crofthawk.mgmt.gwt.GwtTestAdminsMan 
> agementViewImpl.testShowErrorMessage
> is being retried, retry attempt = 1
> ...for every test and I have the following stack trace:
>
> java.lang.RuntimeException: Remote test failed at 78.106.163.8 /
> Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.1) Gecko/
> 2008070208 Firefox/3.0.1
>         at com.google.gwt.junit.JUnitShell.processTestResult(JUnitShell.java:
> 1083)
>         at com.google.gwt.junit.JUnitShell.runTestImpl(JUnitShell.java:1203)
>         at com.google.gwt.junit.JUnitShell.runTestImpl(JUnitShell.java:1198)
>         at com.google.gwt.junit.JUnitShell.runTestImpl(JUnitShell.java:1198)
>         at com.google.gwt.junit.JUnitShell.runTestImpl(JUnitShell.java:1104)
>         at com.google.gwt.junit.JUnitShell.runTest(JUnitShell.java:523)
>         at com.google.gwt.junit.client.GWTTestCase.runTest(GWTTestCase.java:
> 406)
>         at junit.framework.TestCase.runBare(TestCase.java:134)
>         at junit.framework.TestResult$1.protect(TestResult.java:110)
>         at junit.framework.TestResult.runProtected(TestResult.java:128)
>         at junit.framework.TestResult.run(TestResult.java:113)
>         at junit.framework.TestCase.run(TestCase.java:124)
>         at com.google.gwt.junit.client.GWTTestCase.run(GWTTestCase.java:282)
>         at junit.framework.TestSuite.runTest(TestSuite.java:232)
>         at junit.framework.TestSuite.run(TestSuite.java:227)
>         at org.junit.internal.runners.JUnit38ClassRunner.run
> (JUnit38ClassRunner.java:83)
>         at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run
> (JUnit4TestReference.java:46)
>         at org.eclipse.jdt.internal.junit.runner.TestExecution.run
> (TestExecution.java:38)
>         at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests
> (RemoteTestRunner.java:467)
>         at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests
> (RemoteTestRunner.java:683)
>         at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run
> (RemoteTestRunner.java:390)
>         at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main
> (RemoteTestRunner.java:197)
> Caused by: java.lang.NullPointerException
>         at com.google.gwt.dev.shell.CompilingClassLoader
> $MyInstanceMethodOracle.findOriginalDeclaringClass
> (CompilingClassLoader.java:409)
>         at com.google.gwt.dev.shell.rewrite.RewriteRefsToJsoClasses
> $MyMethodAdapter.visitMethodInsn(RewriteRefsToJsoClasses.java:83)
>         at com.google.gwt.dev.asm.ClassReader.accept(ClassReader.java:1371)
>         at com.google.gwt.dev.asm.ClassReader.accept(ClassReader.java:420)
>         at com.google.gwt.dev.shell.rewrite.HostedModeClassRewriter.rewrite
> (HostedModeClassRewriter.java:244)
>         at com.google.gwt.dev.shell.CompilingClassLoader.findClassBytes
> (CompilingClassLoader.java:1157)
>         at com.google.gwt.dev.shell.CompilingClassLoader.findClass
> (CompilingClassLoader.java:985)
>         at java.lang.ClassLoader.loadClass(ClassLoader.java:303)
>         at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
>         at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:316)
>         at java.lang.ClassLoader.defineClass1(Native Method)
>         at java.lang.ClassLoader.defineClass(ClassLoader.java:616)
>         at java.lang.ClassLoader.defineClass(ClassLoader.java:462)
>         at com.google.gwt.dev.shell.CompilingClassLoader.findClass
> (CompilingClassLoader.java:1011)
>         at java.lang.ClassLoader.loadClass(ClassLoader.java:303)
>         at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
>         at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:316)
>         at java.lang.ClassLoader.defineClass1(Native Method)
>         at java.lang.ClassLoader.defineClass(ClassLoader.java:616)
>         at java.lang.ClassLoader.defineClass(ClassLoader.java:462)
>         at com.google.gwt.dev.shell.CompilingClassLoader.findClass
> (CompilingClassLoader.java:1011)
>         at java.lang.ClassLoader.loadClass(ClassLoader.java:303)
>         at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
>         at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:316)
>         at java.lang.ClassLoader.defineClass1(Native Method)
>         at java.lang.ClassLoa

GWT 2.0 and EclEmma code coverage

[CVdS]

Hi All,

Did someone manage to correctly run EclEmma code coverage with GWT
2.0?

I tried it many times with Eclipse 3.5, with both EclEmma 1.3.2 and
1.4.3, both updated (with emma.jar published on the GWT site) and not,
the results are always the same:

The console says something like
[WARN]
com.crofthawk.mgmt.Management.JUnit:com.crofthawk.mgmt.gwt.GwtTestAdminsManagementViewImpl.testShowErrorMessage
is being retried, retry attempt = 1
...for every test and I have the following stack trace:

java.lang.RuntimeException: Remote test failed at 78.106.163.8 /
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.1) Gecko/
2008070208 Firefox/3.0.1
at com.google.gwt.junit.JUnitShell.processTestResult(JUnitShell.java:
1083)
at com.google.gwt.junit.JUnitShell.runTestImpl(JUnitShell.java:1203)
at com.google.gwt.junit.JUnitShell.runTestImpl(JUnitShell.java:1198)
at com.google.gwt.junit.JUnitShell.runTestImpl(JUnitShell.java:1198)
at com.google.gwt.junit.JUnitShell.runTestImpl(JUnitShell.java:1104)
at com.google.gwt.junit.JUnitShell.runTest(JUnitShell.java:523)
at com.google.gwt.junit.client.GWTTestCase.runTest(GWTTestCase.java:
406)
at junit.framework.TestCase.runBare(TestCase.java:134)
at junit.framework.TestResult$1.protect(TestResult.java:110)
at junit.framework.TestResult.runProtected(TestResult.java:128)
at junit.framework.TestResult.run(TestResult.java:113)
at junit.framework.TestCase.run(TestCase.java:124)
at com.google.gwt.junit.client.GWTTestCase.run(GWTTestCase.java:282)
at junit.framework.TestSuite.runTest(TestSuite.java:232)
at junit.framework.TestSuite.run(TestSuite.java:227)
at org.junit.internal.runners.JUnit38ClassRunner.run
(JUnit38ClassRunner.java:83)
at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run
(JUnit4TestReference.java:46)
at org.eclipse.jdt.internal.junit.runner.TestExecution.run
(TestExecution.java:38)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests
(RemoteTestRunner.java:467)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests
(RemoteTestRunner.java:683)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run
(RemoteTestRunner.java:390)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main
(RemoteTestRunner.java:197)
Caused by: java.lang.NullPointerException
at com.google.gwt.dev.shell.CompilingClassLoader
$MyInstanceMethodOracle.findOriginalDeclaringClass
(CompilingClassLoader.java:409)
at com.google.gwt.dev.shell.rewrite.RewriteRefsToJsoClasses
$MyMethodAdapter.visitMethodInsn(RewriteRefsToJsoClasses.java:83)
at com.google.gwt.dev.asm.ClassReader.accept(ClassReader.java:1371)
at com.google.gwt.dev.asm.ClassReader.accept(ClassReader.java:420)
at com.google.gwt.dev.shell.rewrite.HostedModeClassRewriter.rewrite
(HostedModeClassRewriter.java:244)
at com.google.gwt.dev.shell.CompilingClassLoader.findClassBytes
(CompilingClassLoader.java:1157)
at com.google.gwt.dev.shell.CompilingClassLoader.findClass
(CompilingClassLoader.java:985)
at java.lang.ClassLoader.loadClass(ClassLoader.java:303)
at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:316)
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:616)
at java.lang.ClassLoader.defineClass(ClassLoader.java:462)
at com.google.gwt.dev.shell.CompilingClassLoader.findClass
(CompilingClassLoader.java:1011)
at java.lang.ClassLoader.loadClass(ClassLoader.java:303)
at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:316)
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:616)
at java.lang.ClassLoader.defineClass(ClassLoader.java:462)
at com.google.gwt.dev.shell.CompilingClassLoader.findClass
(CompilingClassLoader.java:1011)
at java.lang.ClassLoader.loadClass(ClassLoader.java:303)
at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:316)
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:616)
at java.lang.ClassLoader.defineClass(ClassLoader.java:462)
at com.google.gwt.dev.shell.CompilingClassLoader.findClass
(CompilingClassLoader.java:1011)
at java.lang.ClassLoader.loadClass(ClassLoader.java:303)
at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:316)
at java.lang.ClassLoader.defineClass1(Native Method)
at

Re: Code coverage for GWT

[Arthur Kalmenson]

AFAIK only Emma currently covers GWTTestCases. We use it with Sonar and it
works well.

All the best,
--
Arthur Kalmenson


On Tue, Nov 24, 2009 at 12:38 AM, Feldman, Nir  wrote:

>  Do both fully support GWT (including coverage for GWTTestCase)?
>
>
>
> *From:* davisf...@gmail.com [mailto:davisf...@gmail.com] *On Behalf Of *Davis
> Ford
> *Sent:* Monday, November 23, 2009 8:27 PM
> *To:* google-web-toolkit@googlegroups.com
> *Subject:* Re: Code coverage for GWT
>
>
>
> I like maven-emma-plugin or maven-cobertura-plugin
>
> On Mon, Nov 23, 2009 at 9:23 AM, Nir Feldman  wrote:
>
> Hi,
> I want to have a code coverage for a GWT client built using maven.
> what plugin is the most recommended?
>
> Nir
>
> --
>
> You received this message because you are subscribed to the Google Groups
> "Google Web Toolkit" group.
> To post to this group, send email to google-web-tool...@googlegroups.com.
> To unsubscribe from this group, send email to
> google-web-toolkit+unsubscr...@googlegroups.com
> .
> For more options, visit this group at
> http://groups.google.com/group/google-web-toolkit?hl=.
>
>
>
>
> --
> Zeno Consulting, Inc.
> home: http://www.zenoconsulting.biz
> blog: http://zenoconsulting.wikidot.com
> p: 248.894.4922
> f: 313.884.2977
>
> --
>
> You received this message because you are subscribed to the Google Groups
> "Google Web Toolkit" group.
> To post to this group, send email to google-web-tool...@googlegroups.com.
> To unsubscribe from this group, send email to
> google-web-toolkit+unsubscr...@googlegroups.com
> .
> For more options, visit this group at
> http://groups.google.com/group/google-web-toolkit?hl=.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google Web Toolkit" group.
> To post to this group, send email to google-web-tool...@googlegroups.com.
> To unsubscribe from this group, send email to
> google-web-toolkit+unsubscr...@googlegroups.com
> .
> For more options, visit this group at
> http://groups.google.com/group/google-web-toolkit?hl=en.
>
-- 

You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.

To post to this group, send email to google-web-tool...@googlegroups.com.

To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com.

For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.

GWTTestCase Code Coverage

[Feldman, Nir]

Can someone provide a simple tutorial of how to do set up and use EclEmma to 
run the
tests and get the coverage report?
Thanks.


[cid:image001.gif@01CA7728.C61320E0]

Nir Feldman
Release Control R&D Team Leader
Hewlett-Packard Company

+972-3-5399896   Phone
+972-54-7213833 Cell
+972-3-5331617 Fax
nir.feld...@hp.com



--

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


<>

RE: Code coverage for GWT

[Feldman, Nir]

Do both fully support GWT (including coverage for GWTTestCase)?

From: davisf...@gmail.com [mailto:davisf...@gmail.com] On Behalf Of Davis Ford
Sent: Monday, November 23, 2009 8:27 PM
To: google-web-toolkit@googlegroups.com
Subject: Re: Code coverage for GWT

I like maven-emma-plugin or maven-cobertura-plugin
On Mon, Nov 23, 2009 at 9:23 AM, Nir Feldman 
mailto:nir.feld...@hp.com>> wrote:
Hi,
I want to have a code coverage for a GWT client built using maven.
what plugin is the most recommended?

Nir

--

You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to 
google-web-toolkit@googlegroups.com<mailto:google-web-toolkit@googlegroups.com>.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com<mailto:google-web-toolkit%2bunsubscr...@googlegroups.com>.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=.




--
Zeno Consulting, Inc.
home: http://www.zenoconsulting.biz
blog: http://zenoconsulting.wikidot.com
p: 248.894.4922
f: 313.884.2977

--
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to google-web-tool...@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=.

--

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

Re: Code coverage for GWT

[Davis Ford]

I like maven-emma-plugin or maven-cobertura-plugin

On Mon, Nov 23, 2009 at 9:23 AM, Nir Feldman  wrote:

> Hi,
> I want to have a code coverage for a GWT client built using maven.
> what plugin is the most recommended?
>
> Nir
>
> --
>
> You received this message because you are subscribed to the Google Groups
> "Google Web Toolkit" group.
> To post to this group, send email to google-web-tool...@googlegroups.com.
> To unsubscribe from this group, send email to
> google-web-toolkit+unsubscr...@googlegroups.com
> .
> For more options, visit this group at
> http://groups.google.com/group/google-web-toolkit?hl=.
>
>
>


-- 
Zeno Consulting, Inc.
home: http://www.zenoconsulting.biz
blog: http://zenoconsulting.wikidot.com
p: 248.894.4922
f: 313.884.2977

--

You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to google-web-tool...@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=.

Code coverage for GWT

[Nir Feldman]

Hi,
I want to have a code coverage for a GWT client built using maven.
what plugin is the most recommended?

Nir

--

You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to google-web-tool...@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=.

Re: Clover code coverage

[Arthur Kalmenson]

Is no one using Clover?

--
Arthur Kalmenson



On Tue, Jul 7, 2009 at 9:50 AM, Arthur Kalmenson wrote:
> Hello everyone,
>
> We're currently using Clover for our code coverage tool and I've been
> wanting to get code coverage from GWTTestCases. We try to avoid using
> GWTTestCase and mainly focus on unit testing with TestNG, however, to
> ensure GIN injections work we need to use GWTTestCase.
>
> Has anyone been able to figure out how to get code coverage for
> GWTTestCases? I get run errors because Clover instruments the GWT
> source code and the instrumented Clover packages, etc can't be
> compiled into JS.
>
> Thank you in advance.
>
> Best regards,
> --
> Arthur Kalmenson
>

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

Clover code coverage

[Arthur Kalmenson]

Hello everyone,

We're currently using Clover for our code coverage tool and I've been
wanting to get code coverage from GWTTestCases. We try to avoid using
GWTTestCase and mainly focus on unit testing with TestNG, however, to
ensure GIN injections work we need to use GWTTestCase.

Has anyone been able to figure out how to get code coverage for
GWTTestCases? I get run errors because Clover instruments the GWT
source code and the instrumented Clover packages, etc can't be
compiled into JS.

Thank you in advance.

Best regards,
--
Arthur Kalmenson

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

Re: Code Coverage with EclEmma

[Sumit Chandel]

Hi Matt,
Are you building the latest version of GWT from the SVN trunk?

The team has only just recently added better support for Emma, but it is
still under development. The plan is to try and get this ready for either a
coming milestone or final release, but until then you're likely to encounter
issues running code coverage reports. Some improvements have been added even
past the 1.6 milestone, so if you would like to give Emma support another
try to see how it's shaping up, you should build from the latest in trunk
and run with that.

As far as I know, you should still be able to use Ant or Maven or any other
build system along with Emma code coverage in your GWT applications.

Hope that helps,
-Sumit Chandel

On Tue, Feb 3, 2009 at 3:04 PM, Matt Raible  wrote:

>
> I'm trying to get code coverage support for my GWT project. AFAICT, I
> can't use anything from Maven or Ant, I have to use the EclEmma plugin
> as described in the following issue:
>
> http://code.google.com/p/google-web-toolkit/issues/detail?id=779
>
> I'm using Eclipse 3.3 with the latest version of EclEmma with the JAR
> from tools/redist/emma in my plugins directory.
>
> I can run tests from Eclipse and they all pass. However, the coverage
> shows up as if my GWT classes aren't being tested. Furthermore, my
> "test" classes are showing up with good coverage and I don't believe
> they should be included at all.
>
> Any advice or howto I can use?
>
> Thanks,
>
> Matt
> >
>

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

Code Coverage with EclEmma

[Matt Raible]

I'm trying to get code coverage support for my GWT project. AFAICT, I
can't use anything from Maven or Ant, I have to use the EclEmma plugin
as described in the following issue:

http://code.google.com/p/google-web-toolkit/issues/detail?id=779

I'm using Eclipse 3.3 with the latest version of EclEmma with the JAR
from tools/redist/emma in my plugins directory.

I can run tests from Eclipse and they all pass. However, the coverage
shows up as if my GWT classes aren't being tested. Furthermore, my
"test" classes are showing up with good coverage and I don't believe
they should be included at all.

Any advice or howto I can use?

Thanks,

Matt
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to Google-Web-Toolkit@googlegroups.com
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~--~~~~--~~--~--~---