Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[swtbot-dev] 答复:Re: Measuring code coverage with SWTBot headless

Hi:
   That's great news to me. I'll try them tomorrow.
 
   Thanks a lot for your help!
 
Regards
Xing Yun


At 2011-12-02 16:27:15,"Mickael Istria" <mickael.istria@xxxxxxxxxxxxxx> wrote:
Hi,

Having code coverage using Jacoco is just about setting a -Djava.agent=... system property when starting your tests. I highly recommand it. Also, it you are interested, I made some work on setting up a Tycho build for SWTBot, including code coverage.
You can track it and comment it here: https://bugs.eclipse.org/bugs/show_bug.cgi?id=359024

Regards

On 02/12/2011 00:25, xraynaud wrote:
Hi,

Perhaps you can have a look on http://www.eclemma.org/

Xavier Raynaud

On Thu, 1 Dec 2011 20:31:33 +0100, 邢云 <mouzonherry@xxxxxxx> wrote:
Hi guys:
                I hope this is the right place to ask.

My question:

     Is there any documentation on how to do the test coverage with
SWTBot
     headless?

I have:
                  PDE Build system + SWTBot headless   to do build and
                  test automation. It works.

My problem:
                 I have Clover integrated with PDE Build system.
Currently
                 I cannot get clover report from the execution of SWTBot
                 headless.

                 However, it was a kick-start. I’m still working on it.


-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------Other
suggestions:

                There’s a problem with the ant script presented in
                screencast:
               
http://download.eclipse.org/technology/swtbot/docs/videos/beginners/SWTBotHeadlessTestingForNovices/
                                                <property name="os"
                                                value="win32"/>
                                                <property name="ws"
                                                value="win32"/> (in the
                                                screencast, it is:
                                                value=”${workspace}”, it
                                                doesn’t work)
                                                <property name="arch"
                                                value="x86"/>

                And, it would be better to notify user that the property
                names cannot be changed, such as:
                                                               
<property
                                                               
name="eclipse-home"
                                                                value="
"
                                                                />
                                                               
<property
                                                               
name="plugin-name"
                                                                value="
"
                                                                />
                                                               
<property
                                                               
name="test-classname"
                                                                value="
"
                                                                />


                That’s all.

                You guys have made great work and SWTBot headless does
                solve my problem!

Regards
Xing Yun
_______________________________________________
swtbot-dev mailing list
swtbot-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/swtbot-dev


--

Mickael Istria
R&D Engineer, Eclipse Plug-in RCP Developer

PetalsLink - Open Source SOA

My blog - My Tweets




Back to the top