Yes Marc, you're right. Exceptions went off now. 

On the other hand, made below changes and ran Jenkins job,

Case-1: Removed <jacoco:coverage> </jacoco:coverage> and ran the script

Case-2: Removed <jacoco:agent property="agentvmparam" 
destfile="X:/.../.../.../.../jacoco.exec" includes="my.company.*" output="file" 
dumponexit="true" classdumpdir="X:/.../.../.../.../jclasses"/> and ran the build

Both the above cases resulted in same old result. Am I missing anything here? 

Request other group members who've succeeded in getting code coverage for 
selenium UI tests to provide insight into this issue.

Thanks

-- 
You received this message because you are subscribed to the Google Groups 
"JaCoCo and EclEmma Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jacoco/5095105a-d1c9-441a-9b12-3d96acfadba9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to