Can JUnit Plugin tests be profiled? [message #111054] |
Fri, 31 August 2007 18:34 |
Eclipse User |
|
|
|
Originally posted by: mlevison.gmail.com
We run our tests as "JUnit Plug-in Tests" so that we can access the
filesystem and things like Display. However as I go to do code coverage
work I struggling to make it work.
Can I profile tests that are run as Plugin tests? I think this bug:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=75029
is telling me no.
Is there a trick or do we just have to guess at our code coverage?
Cheers
Mark Levison
|
|
|
Re: Can JUnit Plugin tests be profiled? [message #111065 is a reply to message #111054] |
Fri, 31 August 2007 20:06 |
Eclipse User |
|
|
|
Originally posted by: mlevison.gmail.com
Mark Levison wrote:
> We run our tests as "JUnit Plug-in Tests" so that we can access the
> filesystem and things like Display. However as I go to do code coverage
> work I struggling to make it work.
Ok I figure the first part out - apparently my unstated goal of the day
- make a fool of myself in public.
Just for the record all I needed to do was open the Profile Dialog and
it gave me all sort of options.
Problem #2 I'm only seeing profile data for my test plugin not for the
code under test. The code in the test plugin and primary plugin share
the same name space (although the test plugin is not currently a
fragment). Even though it should be necessary I've mucked around with
the default filter to include all the possibly relevant code. Finally
code from other plugins is covered. Is my problem merely that my test
plugin isn't a fragment?
Problem #3 Running under Java 1.5 I don't seem to have an option to
generate code coverage - just Execution Time Analysis. When I go to the
Profiling perspective I can't find any options to get coverage statistics.
Cheers
Mark Levison
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.01905 seconds