Logo QF-Test

Finding valuable answers
in the Mailing List Archive.

 

Free Trial  Download  Buy

Thomas Max, QF-Test training and support

Use the full-text search on our web site to find helpful tips on the mailing list.

Thomas Max, 
Sr. Software Engineer & Trainer, QFS

2017 up to now  | 2016 | 2015 | 2014 | 2013 | 2012 | 2011 | 2010 | 2009 | 2008 | 2007

(older archive entries before 2007 are not shown here, but included in the onsite-search)

Mailing List - Entries of 2007


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [QF-Test] code coverage


  • Subject: Re: [QF-Test] code coverage
  • From: "Michaelis, Mark" <mark.michaelis@?.com>
  • Date: Thu, 6 Dec 2007 08:25:31 +0100

Hello Huawei,

 

I used EMMA with another GUI-Testtool (before we migrated to QF-Test). It’s a long time since I did so, so I don’t remember all. I just remember that there are two ways to instrument the application. Both ways don’t need the source code. One way is to instrument the classes/jars just before test execution, the other is to instrument “on the fly” as stated on the EMMA webpage (http://emma.sourceforge.net/).

 

I recommend instrumentation before test execution as this is remarkable faster than “on the fly”. There is only a problem if you have to deal with signed jars as of course Java will detect that the JARs got modified. In this case (as far as I know) you have to use “on the fly” instrumentation.

 

But may I recommend a different approach? Well, I’ll just do it: I don’t think it’s useful to get Code Coverage results for GUI-Tests. At least when I tried this approach I got aware that our GUI simply has neither direct nor indirect access to some pieces of code. Of course this might differ from application to application.

 

I would suggest to use Unit-Tests instead (JUnit/TestNG) to get a good code coverage.

 

What would be useful from my point of view would be a feature request to QFS: Have “GUI Element Coverage”. E. g. I would like to ensure that I have tested every menu-entry, every toolbar-button, etc. This would help me very much to see how much of an application window has been covered by GUI-Tests.

 

Kind Regards

            Mark

 

 

--

Mark Michaelis
Software Engineer Quality Assurance

CoreMedia
Ludwig-Erhard-Str. 18
20459
Hamburg, Germany
www.coremedia.com 

--------------------------------------------------------
CoreMedia AG
Executive Board: Sören Stamer (CEO), Dr. Klemens Kleiminger (CFO)
Supervisory Board: Prof. Dr. Joachim Schmidt (Chairman)
Trade Register: Amtsgericht Hamburg, HR B 76277

--------------------------------------------------------

 

 

From: qftest-list-bounces@?.de [mailto:qftest-list-bounces@?.de] On Behalf Of Huawei Luo
Sent: Wednesday, December 05, 2007 10:04 PM
To: qftest-list@?.de
Subject: [QF-Test] code coverage

 

Hi, does anyone have the experience with using code coverage tool – EMMA – together with qf-test? I read couple of posts in the list, and need to make clear several things.

 

My application is an Eclipse application, my qftest suite are all against binary, i.e. I don’t build source code. So how to use EMMA to get the code coverage of qft test suites?

 

Thanks and Regards

Huawei

 


Videos Downloads Documentation Buy Free Trial