Re: [classlib] [testing] Coverage (was Re: 37% of total test execution time is spent in a single test)

[Vladimir Ivanov]

On 10/6/06, Geir Magnusson Jr. <[EMAIL PROTECTED]> wrote:


>
> - 'cc' - for cruise control script (and move current stuff to this dir);
>
> - 'coverage' - for coverage scripts (It will nice if somebody also
placed
> here data from issue 564);
>
> - 'japi' - for script to run 'japi'-tool.

Agreed on all three.




It will fine if somebody do it :). We have updated version of CC (
HARMONY-995 ) and coverage
scripts (HARMONY-564  ). I
hope we will have a japi script soon.

Now I'm going to:

- improve notification for CC to include txt files (output of cunit and
smoke tests for DRLVM);

- add imageio/print/applet modules to coverage script.

I hope, it will be small updated to 'buildtest' module instead of
reattach to jira a whole scripts again.



thanks, Vladimir

Do we have a japi script?


geir

>
>
>
> Seems, that directory 'tests' also should be created in this module to
> place non-unit tests when we will have one.
>
>
>
> thanks, Vladimir
>

-
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [classlib] [testing] Coverage (was Re: 37% of total test execution time is spent in a single test)

[Vladimir Ivanov]

On 10/6/06, Mark Hindess <[EMAIL PROTECTED]> wrote:


>
> Agreed on all three. Do we have a japi script?

I have one but it's a little specific to the wrapper we use for the
builds that report to the -commits list.  But I can provide it if
it will help.




If this script requires some updates I am volunteer to implement it :)

thanks, Vladimir




-Mark.

> > Seems, that directory 'tests' also should be created in this module to
> > place non-unit tests when we will have one.
> >
> >
> >
> > thanks, Vladimir
> >
>
> -
> Terms of use : http://incubator.apache.org/harmony/mailing.html
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>



-
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [classlib] [testing] Coverage (was Re: 37% of total test execution time is spent in a single test)

[Geir Magnusson Jr.]

Thanks - maybe someone can massage that to fit with what we're building...

Mark Hindess wrote:

On 6 October 2006 at 9:41, "Geir Magnusson Jr." <[EMAIL PROTECTED]> wrote:


Vladimir Ivanov wrote:

While nobody objects :) the right place for coverage scripts is 'buildtest'
module.

Seems, that this module should be a little bit reorder: new top level
directories should be created:

- 'cc' - for cruise control script (and move current stuff to this dir);

- 'coverage' - for coverage scripts (It will nice if somebody also placed
here data from issue 564);

- 'japi' - for script to run 'japi'-tool.

Agreed on all three. Do we have a japi script?


I have one but it's a little specific to the wrapper we use for the 
builds that report to the -commits list.  But I can provide it if

it will help.

-Mark.


Seems, that directory 'tests' also should be created in this module to
place non-unit tests when we will have one.



thanks, Vladimir


-
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





-
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



-
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [classlib] [testing] Coverage (was Re: 37% of total test execution time is spent in a single test)

[Mark Hindess]

On 6 October 2006 at 9:41, "Geir Magnusson Jr." <[EMAIL PROTECTED]> wrote:
> 
> 
> Vladimir Ivanov wrote:
> > While nobody objects :) the right place for coverage scripts is 'buildtest'
> > module.
> > 
> > Seems, that this module should be a little bit reorder: new top level
> > directories should be created:
> > 
> > - 'cc' - for cruise control script (and move current stuff to this dir);
> > 
> > - 'coverage' - for coverage scripts (It will nice if somebody also placed
> > here data from issue 564);
> > 
> > - 'japi' - for script to run 'japi'-tool.
> 
> Agreed on all three. Do we have a japi script?

I have one but it's a little specific to the wrapper we use for the 
builds that report to the -commits list.  But I can provide it if
it will help.

-Mark.

> > Seems, that directory 'tests' also should be created in this module to
> > place non-unit tests when we will have one.
> > 
> > 
> > 
> > thanks, Vladimir
> > 
> 
> -
> Terms of use : http://incubator.apache.org/harmony/mailing.html
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 



-
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [classlib] [testing] Coverage (was Re: 37% of total test execution time is spent in a single test)

[Geir Magnusson Jr.]

Vladimir Ivanov wrote:

While nobody objects :) the right place for coverage scripts is 'buildtest'
module.

Seems, that this module should be a little bit reorder: new top level
directories should be created:

- 'cc' - for cruise control script (and move current stuff to this dir);

- 'coverage' - for coverage scripts (It will nice if somebody also placed
here data from issue 564);

- 'japi' - for script to run 'japi'-tool.


Agreed on all three. Do we have a japi script?

geir





Seems, that directory 'tests' also should be created in this module to
place non-unit tests when we will have one.



thanks, Vladimir



-
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [classlib] [testing] Coverage (was Re: 37% of total test execution time is spent in a single test)

[Vladimir Ivanov]

While nobody objects :) the right place for coverage scripts is 'buildtest'
module.

Seems, that this module should be a little bit reorder: new top level
directories should be created:

- 'cc' - for cruise control script (and move current stuff to this dir);

- 'coverage' - for coverage scripts (It will nice if somebody also placed
here data from issue 564);

- 'japi' - for script to run 'japi'-tool.



Seems, that directory 'tests' also should be created in this module to
place non-unit tests when we will have one.



thanks, Vladimir

Re: [classlib] [testing] Coverage (was Re: 37% of total test execution time is spent in a single test)

[Vladimir Ivanov]

On 10/3/06, Mark Hindess <[EMAIL PROTECTED]> wrote:



Regarding the 'run japi' script what are you planning to do here?  The
IBM Build/test builds also run japi (on linux only since we get enough
information using one platform and linux is easier).  We might as well
share ant code.

Also note that to get anything like reasonable data you need to be
running the latest japi from CVS.



Please, share the code (as part of B&TI) :) It will be enough I think
thanks, Vladimir


Regards,

Mark.

>  Thanks, Vladimir
>
>
>
> On 10/2/06, Vladimir Ivanov <[EMAIL PROTECTED]> wrote:
> >
> >  The coverage information was updated on the wiki to current state
(issue
> > 564 also was updated):
> > http://wiki.apache.org/harmony/Coverage_information
> >
> >  thanks, Vladimir
> >
> >
> >
>
> --=_Part_60236_8031756.1159884501259--
>



-
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [classlib] [testing] Coverage (was Re: 37% of total test execution time is spent in a single test)

[Mark Hindess]

On 3 October 2006 at 21:08, "Vladimir Ivanov" <[EMAIL PROTECTED]> wrote:
> 
> I have one more question about coverage: should it be the part of the B&T
> infrastructure or integrated to the current classlib build system?
> 
> From my point of view it should be a part of B&TI while it is rarely used
> functionality and no needs to waste regular build by this data (it does not
> required to duplicate code while coverage depends on regular build and we
> should describe it in the readme.txt).
> 
> 
> 
> By the way, we (at least I :) ) going to have some different scripts in the
> B&I modules:
> 
>  - code coverage (issue 564);
> 
>  - cruise control (issue 995);
> 
>  - japi script (In progress);
> 
>  - script to simple download and run tests against HDK.
> 
> 
> 
> Seems, that it will OK to have some wrapper for these scripts and one set of
> properties.
> 
> Something like: 'ant cc' - to run cruise control, 'ant coverage' - to
> calculate coverage etc.
> 
> If no objections I will try to implement it after 'run japi' script.

Regarding the 'run japi' script what are you planning to do here?  The 
IBM Build/test builds also run japi (on linux only since we get enough
information using one platform and linux is easier).  We might as well
share ant code.

Also note that to get anything like reasonable data you need to be 
running the latest japi from CVS.

Regards,
 Mark.

>  Thanks, Vladimir
> 
> 
> 
> On 10/2/06, Vladimir Ivanov <[EMAIL PROTECTED]> wrote:
> >
> >  The coverage information was updated on the wiki to current state (issue
> > 564 also was updated):
> > http://wiki.apache.org/harmony/Coverage_information
> >
> >  thanks, Vladimir
> >
> >
> >
> 
> --=_Part_60236_8031756.1159884501259--
> 



-
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [classlib] [testing] Coverage (was Re: 37% of total test execution time is spent in a single test)

[Vladimir Ivanov]

I have one more question about coverage: should it be the part of the B&T
infrastructure or integrated to the current classlib build system?


From my point of view it should be a part of B&TI while it is rarely used

functionality and no needs to waste regular build by this data (it does not
required to duplicate code while coverage depends on regular build and we
should describe it in the readme.txt).



By the way, we (at least I :) ) going to have some different scripts in the
B&I modules:

- code coverage (issue 564);

- cruise control (issue 995);

- japi script (In progress);

- script to simple download and run tests against HDK.



Seems, that it will OK to have some wrapper for these scripts and one set of
properties.

Something like: 'ant cc' - to run cruise control, 'ant coverage' - to
calculate coverage etc.

If no objections I will try to implement it after 'run japi' script.



Thanks, Vladimir



On 10/2/06, Vladimir Ivanov <[EMAIL PROTECTED]> wrote:


 The coverage information was updated on the wiki to current state (issue
564 also was updated):
http://wiki.apache.org/harmony/Coverage_information

 thanks, Vladimir

Re: [classlib] [testing] Coverage (was Re: 37% of total test execution time is spent in a single test)

[Vladimir Ivanov]

The coverage information was updated on the wiki to current state (issue
564 also was updated):
http://wiki.apache.org/harmony/Coverage_information

thanks, Vladimir

Re: [classlib] [testing] Coverage (was Re: 37% of total test execution time is spent in a single test)

[Vladimir Ivanov]

The coverage information was updated on the wiki to current state.
thanks, Vladimir

RE: [classlib] [testing] Coverage (was Re: 37% of total test execution time is spent in a single test)

[Ivanov, Alexey A]

Vladimir,

I am working to minimize hang-up of swing tests.

Regards,
--
Alexey A. Ivanov
Intel Middleware Product Division


>-Original Message-
>From: Vladimir Ivanov [mailto:[EMAIL PROTECTED]
>Sent: Friday, August 18, 2006 4:28 PM
>To: harmony-dev@incubator.apache.org
>Subject: Re: [classlib] [testing] Coverage (was Re: 37% of total test
>execution time is spent in a single test)
>
>The coverage information was updated on the wiki. Also, coverage for
>accessibility, awt, instrument and sound modules was added. I have a
>problem
>to calculate coverage for swing module (test run hang up) so issue 564
will
>be updated later.
>
> thanks, Vladimir
>
>
>On 6/20/06, Paulex Yang <[EMAIL PROTECTED]> wrote:
>>
>> Vladimir Ivanov wrote:
>> > Classes from exclude list are now specified as green.
>> > I've update wiki
(http://wiki.apache.org/harmony/Coverage_information)
>> > and
>> > coverage pages.
>> >
>> Great, thank you, Vladimir!
>> > Thanks,
>> >  Vladimir
>> >
>> >
>> > On 6/16/06, Paulex Yang <[EMAIL PROTECTED]> wrote:
>> >>
>> >> Vladimir
>> >>
>> >> Vladimir Ivanov wrote:
>> >> >>
>> >> >> The current reports don't provide code source linking. Are you
>> >> going to
>> >>
>> >> >> add it?
>> >> >
>> >> >
>> >> > There were no information for 'security' and 'auth' modules,
but, I
>> >> have
>> >> > updated the pages and now there is source code linking for all
>> >> modules.
>> >> >
>> >> > One more issue to discuss: excluded classes present in the
coverage
>> >> table
>> >> > now with 0 coverage. May be it is more convenient do not have
these
>> >> > classes
>> >> > in coverage tables at all? In this case one won't wonder why the
>> class
>> >> > has 0
>> >> > coverage - go to exclude list to look at the class and decide
>whether
>> >> the
>> >> > class is really untested or just excluded from coverage,
instead,
>all
>> >> > really
>> >> > uncovered classes will be shown with 0 coverage, if a class is
>> >> missed in
>> >> > coverage table - it is in exclude list.
>> >> +1 for current "0 coverage" is not convenient. But if we can
remove
>> them
>> >> from the report, how about just mark them in another way? say,
mark
>the
>> >> excluded class with different background colors?
>> >>
>> >> At least people don't need to care about two documents for one
package.
>> >> > Thanks,
>> >> >   Vladimir
>> >> >
>> >> >
>> >> >
>> >> >> Now I have 2 questions/ issues to discuss:
>> >> >> > 1) preferable VM to calculate coverage (seems, the exclude
list
>> >> is a
>> >> >> > little
>> >> >> > bit different for j9 and drlvm)
>> >> >>
>> >> >>
>> >> >> If the only difference is the exclude list then I'd suggest
using
>VM
>> >> >> with
>> >> >> the shortest one. :-)
>> >> >>
>> >> >> 2) preferable sorting mode for results (by name, by blocks or
by
>> >> >> methods)
>> >> >>
>> >> >>
>> >> >> IMHO, sorting by name looks more natural.
>> >> >>
>> >> >> Thanks,
>> >> >> Stepan.
>> >> >>
>> >> >> Thanks,
>> >> >> > Vladimir
>> >> >> >
>> >> >> > 
>> >> >> >
>> >> >>
>> >> >>
>> >> >> --
>> >> >> Terms of use : http://incubator.apache.org/harmony/mailing.html
>> >> >> To unsubscribe, e-mail: harmony-dev-
>[EMAIL PROTECTED]
>> >> >> For additional commands, e-mail:
>> >> [EMAIL PROTECTED]
>> >> >>
>> >> >>
>> >> >
>> >>
>> >>
>> >> --
>> >> Paulex Yang
>> >> China Software Development Lab
>> >> IBM
>> >>
>> >>
>> >>
>> >>
-
>> >> Terms of use : http://incubator.apache.org/harmony/mailing.html
>> >> To unsubscribe, e-mail:
[EMAIL PROTECTED]
>> >> For additional commands, e-mail:
[EMAIL PROTECTED]
>> >>
>> >>
>> >
>>
>>
>> --
>> Paulex Yang
>> China Software Development Lab
>> IBM
>>
>>
>>
>> -
>> Terms of use : http://incubator.apache.org/harmony/mailing.html
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail:
[EMAIL PROTECTED]
>>
>>

-
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [classlib] [testing] Coverage (was Re: 37% of total test execution time is spent in a single test)

[Vladimir Ivanov]

Coverage for swing module was added.

thanks, Vladimir


On 8/18/06, Tim Ellison <[EMAIL PROTECTED]> wrote:


Thanks for updating the numbers Vladimir.  Overall I think they look
quite respectable.

There are a few places where it looks like we could use more test
coverage.  It's a great way to contribute to Harmony (he said, hinting
to the lurkers ).  Pick a favourite package, kick the wheels of
Harmony using JUnit tests -- then contribute them for the greater good.

Regards,
Tim

Vladimir Ivanov wrote:
> The coverage information was updated on the wiki. Also, coverage for
> accessibility, awt, instrument and sound modules was added. I have a
> problem
> to calculate coverage for swing module (test run hang up) so issue 564
will
> be updated later.
>
> thanks, Vladimir
>
>
> On 6/20/06, Paulex Yang < [EMAIL PROTECTED]> wrote:
>>
>> Vladimir Ivanov wrote:
>> > Classes from exclude list are now specified as green.
>> > I've update wiki (http://wiki.apache.org/harmony/Coverage_information
)
>> > and
>> > coverage pages.
>> >
>> Great, thank you, Vladimir!
>> > Thanks,
>> >  Vladimir
>> >
>> >
>> > On 6/16/06, Paulex Yang <[EMAIL PROTECTED]> wrote:
>> >>
>> >> Vladimir
>> >>
>> >> Vladimir Ivanov wrote:
>> >> >>
>> >> >> The current reports don't provide code source linking. Are you
>> >> going to
>> >>
>> >> >> add it?
>> >> >
>> >> >
>> >> > There were no information for 'security' and 'auth' modules, but,
I
>> >> have
>> >> > updated the pages and now there is source code linking for all
>> >> modules.
>> >> >
>> >> > One more issue to discuss: excluded classes present in the
coverage
>> >> table
>> >> > now with 0 coverage. May be it is more convenient do not have
these
>> >> > classes
>> >> > in coverage tables at all? In this case one won't wonder why the
>> class
>> >> > has 0
>> >> > coverage - go to exclude list to look at the class and decide
>> whether
>> >> the
>> >> > class is really untested or just excluded from coverage, instead,
>> all
>> >> > really
>> >> > uncovered classes will be shown with 0 coverage, if a class is
>> >> missed in
>> >> > coverage table – it is in exclude list.
>> >> +1 for current "0 coverage" is not convenient. But if we can remove
>> them
>> >> from the report, how about just mark them in another way? say, mark
>> the
>> >> excluded class with different background colors?
>> >>
>> >> At least people don't need to care about two documents for one
>> package.
>> >> > Thanks,
>> >> >   Vladimir
>> >> >
>> >> >
>> >> >
>> >> >> Now I have 2 questions/ issues to discuss:
>> >> >> > 1) preferable VM to calculate coverage (seems, the exclude list

>> >> is a
>> >> >> > little
>> >> >> > bit different for j9 and drlvm)
>> >> >>
>> >> >>
>> >> >> If the only difference is the exclude list then I'd suggest
>> using VM
>> >> >> with
>> >> >> the shortest one. :-)
>> >> >>
>> >> >> 2) preferable sorting mode for results (by name, by blocks or by
>> >> >> methods)
>> >> >>
>> >> >>
>> >> >> IMHO, sorting by name looks more natural.
>> >> >>
>> >> >> Thanks,
>> >> >> Stepan.
>> >> >>
>> >> >> Thanks,
>> >> >> > Vladimir
>> >> >> >
>> >> >> > 
>> >> >> >
>> >> >>
>> >> >>
>> >> >> --
>> >> >> Terms of use : http://incubator.apache.org/harmony/mailing.html
>> >> >> To unsubscribe, e-mail:
>> [EMAIL PROTECTED]
>> >> >> For additional commands, e-mail:
>> >> [EMAIL PROTECTED]
>> >> >>
>> >> >>
>> >> >
>> >>
>> >>
>> >> --
>> >> Paulex Yang
>> >> China Software Development Lab
>> >> IBM
>> >>
>> >>
>> >>
>> >>
-
>> >> Terms of use : http://incubator.apache.org/harmony/mailing.html
>> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> >> For additional commands, e-mail:
[EMAIL PROTECTED]
>> >>
>> >>
>> >
>>
>>
>> --
>> Paulex Yang
>> China Software Development Lab
>> IBM
>>
>>
>>
>> -
>> Terms of use : http://incubator.apache.org/harmony/mailing.html
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>

--

Tim Ellison ([EMAIL PROTECTED] )
IBM Java technology centre, UK.

-
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [classlib] [testing] Coverage (was Re: 37% of total test execution time is spent in a single test)

[Tim Ellison]

Thanks for updating the numbers Vladimir.  Overall I think they look
quite respectable.

There are a few places where it looks like we could use more test
coverage.  It's a great way to contribute to Harmony (he said, hinting
to the lurkers ).  Pick a favourite package, kick the wheels of
Harmony using JUnit tests -- then contribute them for the greater good.

Regards,
Tim

Vladimir Ivanov wrote:
> The coverage information was updated on the wiki. Also, coverage for
> accessibility, awt, instrument and sound modules was added. I have a
> problem
> to calculate coverage for swing module (test run hang up) so issue 564 will
> be updated later.
> 
> thanks, Vladimir
> 
> 
> On 6/20/06, Paulex Yang <[EMAIL PROTECTED]> wrote:
>>
>> Vladimir Ivanov wrote:
>> > Classes from exclude list are now specified as green.
>> > I've update wiki (http://wiki.apache.org/harmony/Coverage_information)
>> > and
>> > coverage pages.
>> >
>> Great, thank you, Vladimir!
>> > Thanks,
>> >  Vladimir
>> >
>> >
>> > On 6/16/06, Paulex Yang <[EMAIL PROTECTED]> wrote:
>> >>
>> >> Vladimir
>> >>
>> >> Vladimir Ivanov wrote:
>> >> >>
>> >> >> The current reports don't provide code source linking. Are you
>> >> going to
>> >>
>> >> >> add it?
>> >> >
>> >> >
>> >> > There were no information for 'security' and 'auth' modules, but, I
>> >> have
>> >> > updated the pages and now there is source code linking for all
>> >> modules.
>> >> >
>> >> > One more issue to discuss: excluded classes present in the coverage
>> >> table
>> >> > now with 0 coverage. May be it is more convenient do not have these
>> >> > classes
>> >> > in coverage tables at all? In this case one won't wonder why the
>> class
>> >> > has 0
>> >> > coverage - go to exclude list to look at the class and decide
>> whether
>> >> the
>> >> > class is really untested or just excluded from coverage, instead,
>> all
>> >> > really
>> >> > uncovered classes will be shown with 0 coverage, if a class is
>> >> missed in
>> >> > coverage table – it is in exclude list.
>> >> +1 for current "0 coverage" is not convenient. But if we can remove
>> them
>> >> from the report, how about just mark them in another way? say, mark
>> the
>> >> excluded class with different background colors?
>> >>
>> >> At least people don't need to care about two documents for one
>> package.
>> >> > Thanks,
>> >> >   Vladimir
>> >> >
>> >> >
>> >> >
>> >> >> Now I have 2 questions/ issues to discuss:
>> >> >> > 1) preferable VM to calculate coverage (seems, the exclude list
>> >> is a
>> >> >> > little
>> >> >> > bit different for j9 and drlvm)
>> >> >>
>> >> >>
>> >> >> If the only difference is the exclude list then I'd suggest
>> using VM
>> >> >> with
>> >> >> the shortest one. :-)
>> >> >>
>> >> >> 2) preferable sorting mode for results (by name, by blocks or by
>> >> >> methods)
>> >> >>
>> >> >>
>> >> >> IMHO, sorting by name looks more natural.
>> >> >>
>> >> >> Thanks,
>> >> >> Stepan.
>> >> >>
>> >> >> Thanks,
>> >> >> > Vladimir
>> >> >> >
>> >> >> > 
>> >> >> >
>> >> >>
>> >> >>
>> >> >> --
>> >> >> Terms of use : http://incubator.apache.org/harmony/mailing.html
>> >> >> To unsubscribe, e-mail:
>> [EMAIL PROTECTED]
>> >> >> For additional commands, e-mail:
>> >> [EMAIL PROTECTED]
>> >> >>
>> >> >>
>> >> >
>> >>
>> >>
>> >> --
>> >> Paulex Yang
>> >> China Software Development Lab
>> >> IBM
>> >>
>> >>
>> >>
>> >> -
>> >> Terms of use : http://incubator.apache.org/harmony/mailing.html
>> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> >> For additional commands, e-mail: [EMAIL PROTECTED]
>> >>
>> >>
>> >
>>
>>
>> -- 
>> Paulex Yang
>> China Software Development Lab
>> IBM
>>
>>
>>
>> -
>> Terms of use : http://incubator.apache.org/harmony/mailing.html
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
> 

-- 

Tim Ellison ([EMAIL PROTECTED])
IBM Java technology centre, UK.

-
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [classlib] [testing] Coverage (was Re: 37% of total test execution time is spent in a single test)

[Vladimir Ivanov]

The coverage information was updated on the wiki. Also, coverage for
accessibility, awt, instrument and sound modules was added. I have a problem
to calculate coverage for swing module (test run hang up) so issue 564 will
be updated later.

thanks, Vladimir


On 6/20/06, Paulex Yang <[EMAIL PROTECTED]> wrote:


Vladimir Ivanov wrote:
> Classes from exclude list are now specified as green.
> I've update wiki (http://wiki.apache.org/harmony/Coverage_information)
> and
> coverage pages.
>
Great, thank you, Vladimir!
> Thanks,
>  Vladimir
>
>
> On 6/16/06, Paulex Yang <[EMAIL PROTECTED]> wrote:
>>
>> Vladimir
>>
>> Vladimir Ivanov wrote:
>> >>
>> >> The current reports don't provide code source linking. Are you
>> going to
>>
>> >> add it?
>> >
>> >
>> > There were no information for 'security' and 'auth' modules, but, I
>> have
>> > updated the pages and now there is source code linking for all
>> modules.
>> >
>> > One more issue to discuss: excluded classes present in the coverage
>> table
>> > now with 0 coverage. May be it is more convenient do not have these
>> > classes
>> > in coverage tables at all? In this case one won't wonder why the
class
>> > has 0
>> > coverage - go to exclude list to look at the class and decide whether
>> the
>> > class is really untested or just excluded from coverage, instead, all
>> > really
>> > uncovered classes will be shown with 0 coverage, if a class is
>> missed in
>> > coverage table – it is in exclude list.
>> +1 for current "0 coverage" is not convenient. But if we can remove
them
>> from the report, how about just mark them in another way? say, mark the
>> excluded class with different background colors?
>>
>> At least people don't need to care about two documents for one package.
>> > Thanks,
>> >   Vladimir
>> >
>> >
>> >
>> >> Now I have 2 questions/ issues to discuss:
>> >> > 1) preferable VM to calculate coverage (seems, the exclude list
>> is a
>> >> > little
>> >> > bit different for j9 and drlvm)
>> >>
>> >>
>> >> If the only difference is the exclude list then I'd suggest using VM
>> >> with
>> >> the shortest one. :-)
>> >>
>> >> 2) preferable sorting mode for results (by name, by blocks or by
>> >> methods)
>> >>
>> >>
>> >> IMHO, sorting by name looks more natural.
>> >>
>> >> Thanks,
>> >> Stepan.
>> >>
>> >> Thanks,
>> >> > Vladimir
>> >> >
>> >> > 
>> >> >
>> >>
>> >>
>> >> --
>> >> Terms of use : http://incubator.apache.org/harmony/mailing.html
>> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> >> For additional commands, e-mail:
>> [EMAIL PROTECTED]
>> >>
>> >>
>> >
>>
>>
>> --
>> Paulex Yang
>> China Software Development Lab
>> IBM
>>
>>
>>
>> -
>> Terms of use : http://incubator.apache.org/harmony/mailing.html
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>


--
Paulex Yang
China Software Development Lab
IBM



-
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [classlib] [testing] Coverage (was Re: 37% of total test execution time is spent in a single test)

[Paulex Yang]

Vladimir Ivanov wrote:

Classes from exclude list are now specified as green.
I've update wiki (http://wiki.apache.org/harmony/Coverage_information) 
and

coverage pages.


Great, thank you, Vladimir!

Thanks,
 Vladimir


On 6/16/06, Paulex Yang <[EMAIL PROTECTED]> wrote:


Vladimir

Vladimir Ivanov wrote:
>>
>> The current reports don't provide code source linking. Are you 
going to


>> add it?
>
>
> There were no information for 'security' and 'auth' modules, but, I 
have
> updated the pages and now there is source code linking for all 
modules.

>
> One more issue to discuss: excluded classes present in the coverage
table
> now with 0 coverage. May be it is more convenient do not have these
> classes
> in coverage tables at all? In this case one won't wonder why the class
> has 0
> coverage - go to exclude list to look at the class and decide whether
the
> class is really untested or just excluded from coverage, instead, all
> really
> uncovered classes will be shown with 0 coverage, if a class is 
missed in

> coverage table – it is in exclude list.
+1 for current "0 coverage" is not convenient. But if we can remove them
from the report, how about just mark them in another way? say, mark the
excluded class with different background colors?

At least people don't need to care about two documents for one package.
> Thanks,
>   Vladimir
>
>
>
>> Now I have 2 questions/ issues to discuss:
>> > 1) preferable VM to calculate coverage (seems, the exclude list 
is a

>> > little
>> > bit different for j9 and drlvm)
>>
>>
>> If the only difference is the exclude list then I'd suggest using VM
>> with
>> the shortest one. :-)
>>
>> 2) preferable sorting mode for results (by name, by blocks or by
>> methods)
>>
>>
>> IMHO, sorting by name looks more natural.
>>
>> Thanks,
>> Stepan.
>>
>> Thanks,
>> > Vladimir
>> >
>> > 
>> >
>>
>>
>> --
>> Terms of use : http://incubator.apache.org/harmony/mailing.html
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: 
[EMAIL PROTECTED]

>>
>>
>


--
Paulex Yang
China Software Development Lab
IBM



-
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]







--
Paulex Yang
China Software Development Lab
IBM



-
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [classlib] [testing] Coverage (was Re: 37% of total test execution time is spent in a single test)

[Vladimir Ivanov]

Classes from exclude list are now specified as green.
I've update wiki (http://wiki.apache.org/harmony/Coverage_information) and
coverage pages.

Thanks,
 Vladimir


On 6/16/06, Paulex Yang <[EMAIL PROTECTED]> wrote:


Vladimir

Vladimir Ivanov wrote:
>>
>> The current reports don't provide code source linking. Are you going to

>> add it?
>
>
> There were no information for 'security' and 'auth' modules, but, I have
> updated the pages and now there is source code linking for all modules.
>
> One more issue to discuss: excluded classes present in the coverage
table
> now with 0 coverage. May be it is more convenient do not have these
> classes
> in coverage tables at all? In this case one won't wonder why the class
> has 0
> coverage - go to exclude list to look at the class and decide whether
the
> class is really untested or just excluded from coverage, instead, all
> really
> uncovered classes will be shown with 0 coverage, if a class is missed in
> coverage table – it is in exclude list.
+1 for current "0 coverage" is not convenient. But if we can remove them
from the report, how about just mark them in another way? say, mark the
excluded class with different background colors?

At least people don't need to care about two documents for one package.
> Thanks,
>   Vladimir
>
>
>
>> Now I have 2 questions/ issues to discuss:
>> > 1) preferable VM to calculate coverage (seems, the exclude list is a
>> > little
>> > bit different for j9 and drlvm)
>>
>>
>> If the only difference is the exclude list then I'd suggest using VM
>> with
>> the shortest one. :-)
>>
>> 2) preferable sorting mode for results (by name, by blocks or by
>> methods)
>>
>>
>> IMHO, sorting by name looks more natural.
>>
>> Thanks,
>> Stepan.
>>
>> Thanks,
>> > Vladimir
>> >
>> > 
>> >
>>
>>
>> --
>> Terms of use : http://incubator.apache.org/harmony/mailing.html
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>


--
Paulex Yang
China Software Development Lab
IBM



-
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [classlib] [testing] Coverage (was Re: 37% of total test execution time is spent in a single test)

[Paulex Yang]

Vladimir

Vladimir Ivanov wrote:


The current reports don't provide code source linking. Are you going to
add it?



There were no information for 'security' and 'auth' modules, but, I have
updated the pages and now there is source code linking for all modules.

One more issue to discuss: excluded classes present in the coverage table
now with 0 coverage. May be it is more convenient do not have these 
classes
in coverage tables at all? In this case one won't wonder why the class 
has 0

coverage - go to exclude list to look at the class and decide whether the
class is really untested or just excluded from coverage, instead, all 
really

uncovered classes will be shown with 0 coverage, if a class is missed in
coverage table – it is in exclude list.
+1 for current "0 coverage" is not convenient. But if we can remove them 
from the report, how about just mark them in another way? say, mark the 
excluded class with different background colors?


At least people don't need to care about two documents for one package.

Thanks,
  Vladimir




Now I have 2 questions/ issues to discuss:
> 1) preferable VM to calculate coverage (seems, the exclude list is a
> little
> bit different for j9 and drlvm)


If the only difference is the exclude list then I'd suggest using VM 
with

the shortest one. :-)

2) preferable sorting mode for results (by name, by blocks or by 
methods)



IMHO, sorting by name looks more natural.

Thanks,
Stepan.

Thanks,
> Vladimir
>
> 
>


--
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]







--
Paulex Yang
China Software Development Lab
IBM



-
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [classlib] [testing] Coverage (was Re: 37% of total test execution time is spent in a single test)

[Vladimir Ivanov]

The current reports don't provide code source linking. Are you going to
add it?



There were no information for 'security' and 'auth' modules, but, I have
updated the pages and now there is source code linking for all modules.

One more issue to discuss: excluded classes present in the coverage table
now with 0 coverage. May be it is more convenient do not have these classes
in coverage tables at all? In this case one won't wonder why the class has 0
coverage - go to exclude list to look at the class and decide whether the
class is really untested or just excluded from coverage, instead, all really
uncovered classes will be shown with 0 coverage, if a class is missed in
coverage table – it is in exclude list.
Thanks,
  Vladimir




Now I have 2 questions/ issues to discuss:
> 1) preferable VM to calculate coverage (seems, the exclude list is a
> little
> bit different for j9 and drlvm)


If the only difference is the exclude list then I'd suggest using VM with
the shortest one. :-)

2) preferable sorting mode for results (by name, by blocks or by methods)


IMHO, sorting by name looks more natural.

Thanks,
Stepan.

Thanks,
> Vladimir
>
> 
>


--
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [classlib] [testing] Coverage (was Re: 37% of total test execution time is spent in a single test)

[Stepan Mishura]

On 6/15/06, Vladimir Ivanov wrote:


I've update web (viv.byethost15.com) - published fresh coverage
information.
No awt package in the beans coverage table anymore.

Also I've update the jira-564 by extended script (that include security,
auth, crypto, lang and rmi packages).



Hi Vladimir,

The current reports don't provide code source linking. Are you going to add
it?

Now I have 2 questions/ issues to discuss:

1) preferable VM to calculate coverage (seems, the exclude list is a
little
bit different for j9 and drlvm)



If the only difference is the exclude list then I'd suggest using VM with
the shortest one. :-)

2) preferable sorting mode for results (by name, by blocks or by methods)


IMHO, sorting by name looks more natural.

Thanks,
Stepan.

Thanks,

Vladimir






--
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [classlib] [testing] Coverage (was Re: 37% of total test execution time is spent in a single test)

[Vladimir Ivanov]

I've update web (viv.byethost15.com) - published fresh coverage information.
No awt package in the beans coverage table anymore.

Also I've update the jira-564 by extended script (that include security,
auth, crypto, lang and rmi packages).

Now I have 2 questions/ issues to discuss:
1) preferable VM to calculate coverage (seems, the exclude list is a little
bit different for j9 and drlvm)
2) preferable sorting mode for results (by name, by blocks or by methods)

Thanks,
 Vladimir

On 6/14/06, Geir Magnusson Jr <[EMAIL PROTECTED]> wrote:




Mark Hindess wrote:
> On 14 June 2006 at 7:04, Geir Magnusson Jr < [EMAIL PROTECTED]> wrote:
>> yes.
>>
>> And/or add it to the upcoming donation of the [testing] infrastructure
>> to make it part of the CI runs.
>
> Are you talking about me?  It's just an ant file and a few script so I
> hope you aren't expecting too much.

A pearl starts with a spec of sand.

(And a perl starts with a #!, I suppose...)

geir

>
>> geir
>>
>> Nathan Beyer wrote:
>>> Is there any possibility of adding this to an Ant script that can
>>> optionally be run with the build scripts? I'd like to make this
>>> easier for everyone to run while developing.
>
> Nathan,
>
> I'm look at doing exactly this.
>
> Regards,
>  Mark.
>
>>> Has anyone tried any other coverage tools? Like TPTP for Eclipse,
Clover or
>>> Corbetura (sp)?
>>>
>>> -Nathan
>>>
 -Original Message-
 From: Vladimir Ivanov [mailto:[EMAIL PROTECTED]

 Latest Harmony API source coverage by Harmony API unit tests results
I
 stored at wiki page

 http://wiki.apache.org/harmony/Coverage_information



 I'm going to refresh it bi-weekly (seems, it is enough for coverage).



> I think we have got a agreement on the test naming convention[1],
but
> for sure, there have been many (legacy) test cases before this
> agreement, and I think the volunteer is highly welcome to provide
patch
> for them.
>
>
[1]http://incubator.apache.org/harmony/subcomponents/classlibrary/testing
 .html

 If nobody objects I'm going to look through the unit tests to correct
 package names according to the agreement (where needed).



  Thanks,

Vladimir



 On 6/8/06, Paulex Yang < [EMAIL PROTECTED] > wrote:
> Vladimir,
>
> Vladimir Ivanov wrote:
>> Thanks Paulex!
>>
>> I did the same, but could not send results due to spam filter J
>> Observations:
>>
>>   1. Coverage results look pretty much similar.
>>   2. Exclude list looks pretty much similar too, but, looks like it
>>   depends on the way of data collection (I didn't run ant task and
the
>> list is
>>   a little bit different).
> Great.
>> In any case, I think, when we run harmony on another VM exclude
list
> will
>> have to be updated.
>>
>>
>>
>> May be we can start publishing the coverage information on wiki
pages
> and
>> provide some updates time to time (I can do it)?
>>
> +1,  and of course, you can only if  no one in the mailing list
objects
> and you'll have my welcome, and I think it will be even greater if
these
> reports can be generated regularly like what JAPI is doing:)
>> One note:
>>
>> I noticed that different unit tests have very different package
names
>>
>> Now the directory with all built tests copied to one place looks
like:
> I think we have got a agreement on the test naming convention[1],
but
> for sure, there have been many (legacy) test cases before this
> agreement, and I think the volunteer is highly welcome to provide
patch
> for them.
>
>

[1]http://incubator.apache.org/harmony/subcomponents/classlibrary/testing.
 html
>>
>> C:\coverage\tests\test>ls
>>
>> GZIPOutClose2.txtapi   config javax
>> tests
>>
>> GZIPOutFinish.txt api.injected  dazzle org
 xml
>> GZIPOutWrite.txt binarygifprefs
>>
>> Inet6Address.golden.ser   bundles   impl
serialization
>>
>> JDK2-3gabba.zip  com   impl.injected   test.txt
>>
>>
>>
>> I think, it would be good if tests had unified package names.
>>
>> Why? - so far, just common sense, just to have an order in test
suite
>>
>> Organization (if consider all unit tests as solid test suite).
>>
>> Thanks,
>>  Vladimir
>>
>> For example, my exclude list for java.io is:
>> -java.io.BufferedInputStream ,
>> -java.io.BufferedOutputStream ,
>> -java.io.File ,
>> -java.io.FileChannelFactory,
>> -java.io.FileDescriptor,
>> -java.io.FileInputStream,
>> - java.io.FileOutputStream,
>> -java.io.FilterInputStream ,
>> -java.io.FilterOutputStream,
>> - java.io.InputStream,
>> -java.io.OutputStream ,
>> -java.io.ObjectStreamFie

Re: [classlib] [testing] Coverage (was Re: 37% of total test execution time is spent in a single test)

[Geir Magnusson Jr]

Mark Hindess wrote:
> On 14 June 2006 at 7:04, Geir Magnusson Jr <[EMAIL PROTECTED]> wrote:
>> yes.
>>
>> And/or add it to the upcoming donation of the [testing] infrastructure
>> to make it part of the CI runs.
> 
> Are you talking about me?  It's just an ant file and a few script so I
> hope you aren't expecting too much.

A pearl starts with a spec of sand.

(And a perl starts with a #!, I suppose...)

geir

> 
>> geir
>>
>> Nathan Beyer wrote:
>>> Is there any possibility of adding this to an Ant script that can
>>> optionally be run with the build scripts? I'd like to make this
>>> easier for everyone to run while developing.
> 
> Nathan,
> 
> I'm look at doing exactly this.
> 
> Regards,
>  Mark.
> 
>>> Has anyone tried any other coverage tools? Like TPTP for Eclipse, Clover or
>>> Corbetura (sp)?
>>>
>>> -Nathan
>>>
 -Original Message-
 From: Vladimir Ivanov [mailto:[EMAIL PROTECTED]

 Latest Harmony API source coverage by Harmony API unit tests results I
 stored at wiki page

 http://wiki.apache.org/harmony/Coverage_information



 I'm going to refresh it bi-weekly (seems, it is enough for coverage).



> I think we have got a agreement on the test naming convention[1], but
> for sure, there have been many (legacy) test cases before this
> agreement, and I think the volunteer is highly welcome to provide patch
> for them.
>
> [1]http://incubator.apache.org/harmony/subcomponents/classlibrary/testing
 .html

 If nobody objects I'm going to look through the unit tests to correct
 package names according to the agreement (where needed).



  Thanks,

Vladimir



 On 6/8/06, Paulex Yang <[EMAIL PROTECTED] > wrote:
> Vladimir,
>
> Vladimir Ivanov wrote:
>> Thanks Paulex!
>>
>> I did the same, but could not send results due to spam filter J
>> Observations:
>>
>>   1. Coverage results look pretty much similar.
>>   2. Exclude list looks pretty much similar too, but, looks like it
>>   depends on the way of data collection (I didn't run ant task and the
>> list is
>>   a little bit different).
> Great.
>> In any case, I think, when we run harmony on another VM exclude list
> will
>> have to be updated.
>>
>>
>>
>> May be we can start publishing the coverage information on wiki pages
> and
>> provide some updates time to time (I can do it)?
>>
> +1,  and of course, you can only if  no one in the mailing list objects
> and you'll have my welcome, and I think it will be even greater if these
> reports can be generated regularly like what JAPI is doing:)
>> One note:
>>
>> I noticed that different unit tests have very different package names
>>
>> Now the directory with all built tests copied to one place looks like:
> I think we have got a agreement on the test naming convention[1], but
> for sure, there have been many (legacy) test cases before this
> agreement, and I think the volunteer is highly welcome to provide patch
> for them.
>
>
 [1]http://incubator.apache.org/harmony/subcomponents/classlibrary/testing.
 html
>>
>> C:\coverage\tests\test>ls
>>
>> GZIPOutClose2.txtapi   config javax
>> tests
>>
>> GZIPOutFinish.txtapi.injected  dazzle org
 xml
>> GZIPOutWrite.txt binarygifprefs
>>
>> Inet6Address.golden.ser  bundles   impl   serialization
>>
>> JDK2-3gabba.zip  com   impl.injected   test.txt
>>
>>
>>
>> I think, it would be good if tests had unified package names.
>>
>> Why? - so far, just common sense, just to have an order in test suite
>>
>> Organization (if consider all unit tests as solid test suite).
>>
>> Thanks,
>>  Vladimir
>>
>> For example, my exclude list for java.io is:
>> -java.io.BufferedInputStream ,
>> -java.io.BufferedOutputStream,
>> -java.io.File ,
>> -java.io.FileChannelFactory,
>> -java.io.FileDescriptor,
>> -java.io.FileInputStream,
>> -java.io.FileOutputStream,
>> -java.io.FilterInputStream ,
>> -java.io.FilterOutputStream,
>> - java.io.InputStream,
>> -java.io.OutputStream,
>> -java.io.ObjectStreamField,
>> -java.io.PrintStream
>>
>>
>> On 6/6/06, Paulex Yang < [EMAIL PROTECTED] > wrote:
>>> I've attach the scripts and excluded class lists to JIRA,  please
 refer
>>> to https://issues.apache.org/jira/browse/HARMONY-564 .  Enjoy it:).
>>>
>>> Mark Hindess wrote:
 On 2 June 2006 at 10:37, Paulex Yang < [EMAIL PROTECTED]>
 wrote:
> Mark,
>
> I'm glad that there is someone else has interest on emma, I've
>>> tried it
> before. AFAIK, emma works by in

Re: [classlib] [testing] Coverage (was Re: 37% of total test execution time is spent in a single test)

[Mark Hindess]

On 14 June 2006 at 7:04, Geir Magnusson Jr <[EMAIL PROTECTED]> wrote:
>
> yes.
> 
> And/or add it to the upcoming donation of the [testing] infrastructure
> to make it part of the CI runs.

Are you talking about me?  It's just an ant file and a few script so I
hope you aren't expecting too much.

> geir
> 
> Nathan Beyer wrote:
> >
> > Is there any possibility of adding this to an Ant script that can
> > optionally be run with the build scripts? I'd like to make this
> > easier for everyone to run while developing.

Nathan,

I'm look at doing exactly this.

Regards,
 Mark.

> > Has anyone tried any other coverage tools? Like TPTP for Eclipse, Clover or
> > Corbetura (sp)?
> > 
> > -Nathan
> > 
> >> -Original Message-
> >> From: Vladimir Ivanov [mailto:[EMAIL PROTECTED]
> >>
> >> Latest Harmony API source coverage by Harmony API unit tests results I
> >> stored at wiki page
> >>
> >> http://wiki.apache.org/harmony/Coverage_information
> >>
> >>
> >>
> >> I'm going to refresh it bi-weekly (seems, it is enough for coverage).
> >>
> >>
> >>
> >>> I think we have got a agreement on the test naming convention[1], but
> >>> for sure, there have been many (legacy) test cases before this
> >>> agreement, and I think the volunteer is highly welcome to provide patch
> >>> for them.
> >>>
> >>> [1]http://incubator.apache.org/harmony/subcomponents/classlibrary/testing
> >> .html
> >>
> >> If nobody objects I'm going to look through the unit tests to correct
> >> package names according to the agreement (where needed).
> >>
> >>
> >>
> >>  Thanks,
> >>
> >>Vladimir
> >>
> >>
> >>
> >> On 6/8/06, Paulex Yang <[EMAIL PROTECTED] > wrote:
> >>> Vladimir,
> >>>
> >>> Vladimir Ivanov wrote:
>  Thanks Paulex!
> 
>  I did the same, but could not send results due to spam filter J
>  Observations:
> 
>    1. Coverage results look pretty much similar.
>    2. Exclude list looks pretty much similar too, but, looks like it
>    depends on the way of data collection (I didn't run ant task and the
>  list is
>    a little bit different).
> >>> Great.
>  In any case, I think, when we run harmony on another VM exclude list
> >>> will
>  have to be updated.
> 
> 
> 
>  May be we can start publishing the coverage information on wiki pages
> >>> and
>  provide some updates time to time (I can do it)?
> 
> >>> +1,  and of course, you can only if  no one in the mailing list objects
> >>> and you'll have my welcome, and I think it will be even greater if these
> >>> reports can be generated regularly like what JAPI is doing:)
> 
>  One note:
> 
>  I noticed that different unit tests have very different package names
> 
>  Now the directory with all built tests copied to one place looks like:
> >>> I think we have got a agreement on the test naming convention[1], but
> >>> for sure, there have been many (legacy) test cases before this
> >>> agreement, and I think the volunteer is highly welcome to provide patch
> >>> for them.
> >>>
> >>>
> >> [1]http://incubator.apache.org/harmony/subcomponents/classlibrary/testing.
> >> html
> 
> 
>  C:\coverage\tests\test>ls
> 
>  GZIPOutClose2.txtapi   config javax
>  tests
> 
>  GZIPOutFinish.txtapi.injected  dazzle org
> >> xml
>  GZIPOutWrite.txt binarygifprefs
> 
>  Inet6Address.golden.ser  bundles   impl   serialization
> 
>  JDK2-3gabba.zip  com   impl.injected   test.txt
> 
> 
> 
>  I think, it would be good if tests had unified package names.
> 
>  Why? - so far, just common sense, just to have an order in test suite
> 
>  Organization (if consider all unit tests as solid test suite).
> 
>  Thanks,
>   Vladimir
> 
>  For example, my exclude list for java.io is:
>  -java.io.BufferedInputStream ,
>  -java.io.BufferedOutputStream,
>  -java.io.File ,
>  -java.io.FileChannelFactory,
>  -java.io.FileDescriptor,
>  -java.io.FileInputStream,
>  -java.io.FileOutputStream,
>  -java.io.FilterInputStream ,
>  -java.io.FilterOutputStream,
>  - java.io.InputStream,
>  -java.io.OutputStream,
>  -java.io.ObjectStreamField,
>  -java.io.PrintStream
> 
> 
>  On 6/6/06, Paulex Yang < [EMAIL PROTECTED] > wrote:
> > I've attach the scripts and excluded class lists to JIRA,  please
> >> refer
> > to https://issues.apache.org/jira/browse/HARMONY-564 .  Enjoy it:).
> >
> > Mark Hindess wrote:
> >> On 2 June 2006 at 10:37, Paulex Yang < [EMAIL PROTECTED]>
> >> wrote:
> >>> Mark,
> >>>
> >>> I'm glad that there is someone else has interest on emma, I've
> > tried it
> >>> before. AFAIK, emma works by instrumentation, but sometimes for
> > classes
> >>> in bootclasspath, the instrumentation cannot work, there are

Re: [classlib] [testing] Coverage (was Re: 37% of total test execution time is spent in a single test)

[Geir Magnusson Jr]

yes.

And/or add it to the upcoming donation of the [testing] infrastructure
to make it part of the CI runs.

geir

Nathan Beyer wrote:
> Is there any possibility of adding this to an Ant script that can optionally
> be run with the build scripts? I'd like to make this easier for everyone to
> run while developing.
> 
> Has anyone tried any other coverage tools? Like TPTP for Eclipse, Clover or
> Corbetura (sp)?
> 
> -Nathan
> 
>> -Original Message-
>> From: Vladimir Ivanov [mailto:[EMAIL PROTECTED]
>>
>> Latest Harmony API source coverage by Harmony API unit tests results I
>> stored at wiki page
>>
>> http://wiki.apache.org/harmony/Coverage_information
>>
>>
>>
>> I'm going to refresh it bi-weekly (seems, it is enough for coverage).
>>
>>
>>
>>> I think we have got a agreement on the test naming convention[1], but
>>> for sure, there have been many (legacy) test cases before this
>>> agreement, and I think the volunteer is highly welcome to provide patch
>>> for them.
>>>
>>> [1]http://incubator.apache.org/harmony/subcomponents/classlibrary/testing
>> .html
>>
>> If nobody objects I'm going to look through the unit tests to correct
>> package names according to the agreement (where needed).
>>
>>
>>
>>  Thanks,
>>
>>Vladimir
>>
>>
>>
>> On 6/8/06, Paulex Yang <[EMAIL PROTECTED] > wrote:
>>> Vladimir,
>>>
>>> Vladimir Ivanov wrote:
 Thanks Paulex!

 I did the same, but could not send results due to spam filter J
 Observations:

   1. Coverage results look pretty much similar.
   2. Exclude list looks pretty much similar too, but, looks like it
   depends on the way of data collection (I didn't run ant task and the
 list is
   a little bit different).
>>> Great.
 In any case, I think, when we run harmony on another VM exclude list
>>> will
 have to be updated.



 May be we can start publishing the coverage information on wiki pages
>>> and
 provide some updates time to time (I can do it)?

>>> +1,  and of course, you can only if  no one in the mailing list objects
>>> and you'll have my welcome, and I think it will be even greater if these
>>> reports can be generated regularly like what JAPI is doing:)

 One note:

 I noticed that different unit tests have very different package names

 Now the directory with all built tests copied to one place looks like:
>>> I think we have got a agreement on the test naming convention[1], but
>>> for sure, there have been many (legacy) test cases before this
>>> agreement, and I think the volunteer is highly welcome to provide patch
>>> for them.
>>>
>>>
>> [1]http://incubator.apache.org/harmony/subcomponents/classlibrary/testing.
>> html


 C:\coverage\tests\test>ls

 GZIPOutClose2.txtapi   config javax
 tests

 GZIPOutFinish.txtapi.injected  dazzle org
>> xml
 GZIPOutWrite.txt binarygifprefs

 Inet6Address.golden.ser  bundles   impl   serialization

 JDK2-3gabba.zip  com   impl.injected   test.txt



 I think, it would be good if tests had unified package names.

 Why? - so far, just common sense, just to have an order in test suite

 Organization (if consider all unit tests as solid test suite).

 Thanks,
  Vladimir

 For example, my exclude list for java.io is:
 -java.io.BufferedInputStream ,
 -java.io.BufferedOutputStream,
 -java.io.File ,
 -java.io.FileChannelFactory,
 -java.io.FileDescriptor,
 -java.io.FileInputStream,
 -java.io.FileOutputStream,
 -java.io.FilterInputStream ,
 -java.io.FilterOutputStream,
 - java.io.InputStream,
 -java.io.OutputStream,
 -java.io.ObjectStreamField,
 -java.io.PrintStream


 On 6/6/06, Paulex Yang < [EMAIL PROTECTED] > wrote:
> I've attach the scripts and excluded class lists to JIRA,  please
>> refer
> to https://issues.apache.org/jira/browse/HARMONY-564 .  Enjoy it:).
>
> Mark Hindess wrote:
>> On 2 June 2006 at 10:37, Paulex Yang < [EMAIL PROTECTED]>
>> wrote:
>>> Mark,
>>>
>>> I'm glad that there is someone else has interest on emma, I've
> tried it
>>> before. AFAIK, emma works by instrumentation, but sometimes for
> classes
>>> in bootclasspath, the instrumentation cannot work, there are two
> cases:
>
>>> 1. Some instrumented classes cannot be loaded by VM.
>>> 2. Some classes cannot be instrumented
>>>
>>> I have tried to look more inside to find some way to work around
> but I
>>> haven't got enough time yet.
>>>
>>> Specifically for nio-channel module, I had a list for these two
>>> cases
> (I
>>> believe the data is a little outdated and should be reevaluated)
>>> case 1.
>>> BaseByteBuffer.class
>>> Buffer.class
>>> BufferFactory.class
>>> 

RE: [classlib] [testing] Coverage (was Re: 37% of total test execution time is spent in a single test)

[Nathan Beyer]

Is there any possibility of adding this to an Ant script that can optionally
be run with the build scripts? I'd like to make this easier for everyone to
run while developing.

Has anyone tried any other coverage tools? Like TPTP for Eclipse, Clover or
Corbetura (sp)?

-Nathan

> -Original Message-
> From: Vladimir Ivanov [mailto:[EMAIL PROTECTED]
> 
> Latest Harmony API source coverage by Harmony API unit tests results I
> stored at wiki page
> 
> http://wiki.apache.org/harmony/Coverage_information
> 
> 
> 
> I'm going to refresh it bi-weekly (seems, it is enough for coverage).
> 
> 
> 
> >I think we have got a agreement on the test naming convention[1], but
> >for sure, there have been many (legacy) test cases before this
> >agreement, and I think the volunteer is highly welcome to provide patch
> >for them.
> >
> >[1]http://incubator.apache.org/harmony/subcomponents/classlibrary/testing
> .html
> 
> >
> 
> If nobody objects I'm going to look through the unit tests to correct
> package names according to the agreement (where needed).
> 
> 
> 
>  Thanks,
> 
>Vladimir
> 
> 
> 
> On 6/8/06, Paulex Yang <[EMAIL PROTECTED] > wrote:
> >
> > Vladimir,
> >
> > Vladimir Ivanov wrote:
> > > Thanks Paulex!
> > >
> > > I did the same, but could not send results due to spam filter J
> > > Observations:
> > >
> > >   1. Coverage results look pretty much similar.
> > >   2. Exclude list looks pretty much similar too, but, looks like it
> > >   depends on the way of data collection (I didn't run ant task and the
> > > list is
> > >   a little bit different).
> > Great.
> > >
> > > In any case, I think, when we run harmony on another VM exclude list
> > will
> > > have to be updated.
> > >
> > >
> > >
> > > May be we can start publishing the coverage information on wiki pages
> > and
> > > provide some updates time to time (I can do it)?
> > >
> > +1,  and of course, you can only if  no one in the mailing list objects
> > and you'll have my welcome, and I think it will be even greater if these
> > reports can be generated regularly like what JAPI is doing:)
> > >
> > >
> > > One note:
> > >
> > > I noticed that different unit tests have very different package names
> > >
> > > Now the directory with all built tests copied to one place looks like:
> > I think we have got a agreement on the test naming convention[1], but
> > for sure, there have been many (legacy) test cases before this
> > agreement, and I think the volunteer is highly welcome to provide patch
> > for them.
> >
> >
> [1]http://incubator.apache.org/harmony/subcomponents/classlibrary/testing.
> html
> >
> > >
> > >
> > >
> > > C:\coverage\tests\test>ls
> > >
> > > GZIPOutClose2.txtapi   config javax
> > > tests
> > >
> > > GZIPOutFinish.txtapi.injected  dazzle org
> xml
> >
> > >
> > > GZIPOutWrite.txt binarygifprefs
> > >
> > > Inet6Address.golden.ser  bundles   impl   serialization
> > >
> > > JDK2-3gabba.zip  com   impl.injected   test.txt
> > >
> > >
> > >
> > > I think, it would be good if tests had unified package names.
> > >
> > > Why? - so far, just common sense, just to have an order in test suite
> > >
> > > Organization (if consider all unit tests as solid test suite).
> > >
> > > Thanks,
> > >  Vladimir
> > >
> > > For example, my exclude list for java.io is:
> > > -java.io.BufferedInputStream ,
> > > -java.io.BufferedOutputStream,
> > > -java.io.File ,
> > > -java.io.FileChannelFactory,
> > > -java.io.FileDescriptor,
> > > -java.io.FileInputStream,
> > > -java.io.FileOutputStream,
> > > -java.io.FilterInputStream ,
> > > -java.io.FilterOutputStream,
> > > - java.io.InputStream,
> > > -java.io.OutputStream,
> > > -java.io.ObjectStreamField,
> > > -java.io.PrintStream
> > >
> > >
> > > On 6/6/06, Paulex Yang < [EMAIL PROTECTED] > wrote:
> > >>
> > >> I've attach the scripts and excluded class lists to JIRA,  please
> refer
> > >> to https://issues.apache.org/jira/browse/HARMONY-564 .  Enjoy it:).
> > >>
> > >> Mark Hindess wrote:
> > >> > On 2 June 2006 at 10:37, Paulex Yang < [EMAIL PROTECTED]>
> wrote:
> > >> >
> > >> >> Mark,
> > >> >>
> > >> >> I'm glad that there is someone else has interest on emma, I've
> > >> tried it
> > >> >> before. AFAIK, emma works by instrumentation, but sometimes for
> > >> classes
> > >> >> in bootclasspath, the instrumentation cannot work, there are two
> > >> cases:
> > >>
> > >> >> 1. Some instrumented classes cannot be loaded by VM.
> > >> >> 2. Some classes cannot be instrumented
> > >> >>
> > >> >> I have tried to look more inside to find some way to work around
> > >> but I
> > >> >> haven't got enough time yet.
> > >> >>
> > >> >> Specifically for nio-channel module, I had a list for these two
> > cases
> > >> (I
> > >> >> believe the data is a little outdated and should be reevaluated)
> > >> >> case 1.
> > >> >> BaseByteBuffer.class
> > >> >> Buffer.class
> > >> >> BufferFactory.class
> > >> >> Byt

Re: [classlib] [testing] Coverage (was Re: 37% of total test execution time is spent in a single test)

[Mark Hindess]

On 13 June 2006 at 18:50, "Vladimir Ivanov" <[EMAIL PROTECTED]> wrote:
> 
> > > P.S. I think java.awt does not currently belong to beans module,
> > > though who knows what the future may bring us :)
> 
> In fact, coverage information is gathered for each jar, that, to
> some extend corresponds to modules content.  Some awt classes are in
> beans.jar, that is why they appeared in coverage statistics for beans
> module.

This is fixed in r413883.

-Mark.



-
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [classlib] [testing] Coverage (was Re: 37% of total test execution time is spent in a single test)

[Vladimir Ivanov]

I've update the web site by information about auth, crypto and rmi modules.
The exclude list also was added.
I'm not sure that all tests were run correctly so I'm going to verify test
runs.

Thanks,
 Vladimir


On 6/13/06, Vladimir Ivanov <[EMAIL PROTECTED]> wrote:


  > One more thing I've missed: what is the exclude list you've finally
ended with?
I'm going to publish it ASAP.

 > > P.S. I think java.awt does not currently belong to beans module,
> > though who knows what the future may bring us :)

In fact, coverage information is gathered for each jar, that, to some
extend corresponds to modules content.
Some awt classes are in beans.jar, that is why they appeared in coverage
statistics for beans module.

  Thanks,
  Vladimir

On 6/13/06, Mikhail Loenko <[EMAIL PROTECTED]> wrote:

> Cool! Sorry, I've missed it
>
> One more thing I've missed: what is the exclude list you've finally
> ended with?
>
> Thanks,
> Mikhail
>
> 2006/6/13, Vladimir Ivanov <[EMAIL PROTECTED]>:
> > The detailed info available at   http://viv.byethost15.com/ (this
> address
> > also pointed on wiki-page).
> > Do you need additional information ?
> >
> > Thanks,
> >  Vladimir
> >
> >
> > On 6/13/06, Mikhail Loenko < [EMAIL PROTECTED] > wrote:
> > >
> > > Great!
> > >
> > > Is it possible to see uncovered classes/methods/lines?
> > >
> > > Thanks,
> > > Mikhail
> > >
> > > P.S. I think java.awt does not currently belong to beans module,
> > > though who knows what the future may bring us :)
> > >
> > > 2006/6/13, Vladimir Ivanov < [EMAIL PROTECTED]>:
> > > > Latest Harmony API source coverage by Harmony API unit tests
> results I
> > > > stored at wiki page
> > > >
> > > > http://wiki.apache.org/harmony/Coverage_information
> > > >
> > > >
> > > >
> > > > I'm going to refresh it bi-weekly (seems, it is enough for
> coverage).
> > > >
> > > >
> > > >
> > > > >I think we have got a agreement on the test naming convention[1],
> but
> > > > >for sure, there have been many (legacy) test cases before this
> > > > >agreement, and I think the volunteer is highly welcome to provide
> patch
> > > > >for them.
> > > > >
> > > >
> > >
> 
>[1]http://incubator.apache.org/harmony/subcomponents/classlibrary/testing.html
> > > >
> > > > >
> > > >
> > > > If nobody objects I'm going to look through the unit tests to
> correct
> > > > package names according to the agreement (where needed).
> > > >
> > > >
> > > >
> > > >  Thanks,
> > > >
> > > >   Vladimir
> > > >
> > > >
> > > >
> > > > On 6/8/06, Paulex Yang < [EMAIL PROTECTED] > wrote:
> > > > >
> > > > > Vladimir,
> > > > >
> > > > > Vladimir Ivanov wrote:
> > > > > > Thanks Paulex!
> > > > > >
> > > > > > I did the same, but could not send results due to spam filter
> J
> > > > > > Observations:
> > > > > >
> > > > > >   1. Coverage results look pretty much similar.
> > > > > >   2. Exclude list looks pretty much similar too, but, looks
> like it
> > > > > >   depends on the way of data collection (I didn't run ant task
> and
> > > the
> > > > > > list is
> > > > > >   a little bit different).
> > > > > Great.
> > > > > >
> > > > > > In any case, I think, when we run harmony on another VM
> exclude list
> > > > > will
> > > > > > have to be updated.
> > > > > >
> > > > > >
> > > > > >
> > > > > > May be we can start publishing the coverage information on
> wiki
> > > pages
> > > > > and
> > > > > > provide some updates time to time (I can do it)?
> > > > > >
> > > > > +1,  and of course, you can only if  no one in the mailing list
> > > objects
> > > > > and you'll have my welcome, and I think it will be even greater
> if
> > > these
> > > > > reports can be generated regularly like what JAPI is doing:)
> > > > > >
> > > > > >
> > > > > > One note:
> > > > > >
> > > > > > I noticed that different unit tests have very different
> package
> > > names
> > > > > >
> > > > > > Now the directory with all built tests copied to one place
> looks
> > > like:
> > > > > I think we have got a agreement on the test naming
> convention[1], but
> > > > > for sure, there have been many (legacy) test cases before this
> > > > > agreement, and I think the volunteer is highly welcome to
> provide
> > > patch
> > > > > for them.
> > > > >
> > > > >
> > >
> [1]http://incubator.apache.org/harmony/subcomponents/classlibrary/testing.html
>
> > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > C:\coverage\tests\test>ls
> > > > > >
> > > > > > GZIPOutClose2.txtapi   config javax
> > > > > > tests
> > > > > >
> > > > > > GZIPOutFinish.txtapi.injected  dazzle
> > > orgxml
> > > > >
> > > > > >
> > > > > > GZIPOutWrite.txt binarygifprefs
> > > > > >
> > > > > > Inet6Address.golden.ser  bundles   impl
> serialization
> > > > > >
> > > > > > JDK2-3gabba.zip  com   impl.injected
> test.txt
> > > > > >
> > > > > >
> > > > > >
> > > > > > I think, it would be good if tests had unified package names.
> > > > > >
> > > > > > Why? – so 

Re: [classlib] [testing] Coverage (was Re: 37% of total test execution time is spent in a single test)

[Vladimir Ivanov]

One more thing I've missed: what is the exclude list you've finally ended

with?
I'm going to publish it ASAP.


> P.S. I think java.awt does not currently belong to beans module,
> though who knows what the future may bring us :)


In fact, coverage information is gathered for each jar, that, to some extend
corresponds to modules content.
Some awt classes are in beans.jar, that is why they appeared in coverage
statistics for beans module.

Thanks,
 Vladimir

On 6/13/06, Mikhail Loenko <[EMAIL PROTECTED]> wrote:


Cool! Sorry, I've missed it

One more thing I've missed: what is the exclude list you've finally ended
with?

Thanks,
Mikhail

2006/6/13, Vladimir Ivanov <[EMAIL PROTECTED]>:
> The detailed info available at  http://viv.byethost15.com/ (this address
> also pointed on wiki-page).
> Do you need additional information ?
>
> Thanks,
>  Vladimir
>
>
> On 6/13/06, Mikhail Loenko < [EMAIL PROTECTED]> wrote:
> >
> > Great!
> >
> > Is it possible to see uncovered classes/methods/lines?
> >
> > Thanks,
> > Mikhail
> >
> > P.S. I think java.awt does not currently belong to beans module,
> > though who knows what the future may bring us :)
> >
> > 2006/6/13, Vladimir Ivanov < [EMAIL PROTECTED]>:
> > > Latest Harmony API source coverage by Harmony API unit tests results
I
> > > stored at wiki page
> > >
> > > http://wiki.apache.org/harmony/Coverage_information
> > >
> > >
> > >
> > > I'm going to refresh it bi-weekly (seems, it is enough for
coverage).
> > >
> > >
> > >
> > > >I think we have got a agreement on the test naming convention[1],
but
> > > >for sure, there have been many (legacy) test cases before this
> > > >agreement, and I think the volunteer is highly welcome to provide
patch
> > > >for them.
> > > >
> > >
> >
>[1]http://incubator.apache.org/harmony/subcomponents/classlibrary/testing.html
> > >
> > > >
> > >
> > > If nobody objects I'm going to look through the unit tests to
correct
> > > package names according to the agreement (where needed).
> > >
> > >
> > >
> > >  Thanks,
> > >
> > >   Vladimir
> > >
> > >
> > >
> > > On 6/8/06, Paulex Yang <[EMAIL PROTECTED] > wrote:
> > > >
> > > > Vladimir,
> > > >
> > > > Vladimir Ivanov wrote:
> > > > > Thanks Paulex!
> > > > >
> > > > > I did the same, but could not send results due to spam filter J
> > > > > Observations:
> > > > >
> > > > >   1. Coverage results look pretty much similar.
> > > > >   2. Exclude list looks pretty much similar too, but, looks like
it
> > > > >   depends on the way of data collection (I didn't run ant task
and
> > the
> > > > > list is
> > > > >   a little bit different).
> > > > Great.
> > > > >
> > > > > In any case, I think, when we run harmony on another VM exclude
list
> > > > will
> > > > > have to be updated.
> > > > >
> > > > >
> > > > >
> > > > > May be we can start publishing the coverage information on wiki
> > pages
> > > > and
> > > > > provide some updates time to time (I can do it)?
> > > > >
> > > > +1,  and of course, you can only if  no one in the mailing list
> > objects
> > > > and you'll have my welcome, and I think it will be even greater if

> > these
> > > > reports can be generated regularly like what JAPI is doing:)
> > > > >
> > > > >
> > > > > One note:
> > > > >
> > > > > I noticed that different unit tests have very different package
> > names
> > > > >
> > > > > Now the directory with all built tests copied to one place looks

> > like:
> > > > I think we have got a agreement on the test naming convention[1],
but
> > > > for sure, there have been many (legacy) test cases before this
> > > > agreement, and I think the volunteer is highly welcome to provide
> > patch
> > > > for them.
> > > >
> > > >
> >
[1]http://incubator.apache.org/harmony/subcomponents/classlibrary/testing.html
> > > >
> > > > >
> > > > >
> > > > >
> > > > > C:\coverage\tests\test>ls
> > > > >
> > > > > GZIPOutClose2.txtapi   config javax
> > > > > tests
> > > > >
> > > > > GZIPOutFinish.txtapi.injected  dazzle
> > orgxml
> > > >
> > > > >
> > > > > GZIPOutWrite.txt binarygifprefs
> > > > >
> > > > > Inet6Address.golden.ser  bundles   impl
serialization
> > > > >
> > > > > JDK2-3gabba.zip  com   impl.injected   test.txt
> > > > >
> > > > >
> > > > >
> > > > > I think, it would be good if tests had unified package names.
> > > > >
> > > > > Why? – so far, just common sense, just to have an order in test
> > suite
> > > > >
> > > > > Organization (if consider all unit tests as solid test suite).
> > > > >
> > > > > Thanks,
> > > > >  Vladimir
> > > > >
> > > > > For example, my exclude list for java.io is:
> > > > > -java.io.BufferedInputStream ,
> > > > > -java.io.BufferedOutputStream,
> > > > > -java.io.File ,
> > > > > -java.io.FileChannelFactory ,
> > > > > -java.io.FileDescriptor,
> > > > > -java.io.FileInputStream,
> > > > > -java.io.FileOutputStream,
> > > > > -java.io.FilterInputStream ,
> > > > > -java.io.FilterOutputStr

Re: [classlib] [testing] Coverage (was Re: 37% of total test execution time is spent in a single test)

[Paulex Yang]

Vladimir Ivanov wrote:

Latest Harmony API source coverage by Harmony API unit tests results I
stored at wiki page

http://wiki.apache.org/harmony/Coverage_information

Cool! Thank you, Vladimir.

Would you please also add the excluded class list, so that we can 
differentiate them from the classes actually without unit tests?




I'm going to refresh it bi-weekly (seems, it is enough for coverage).




I think we have got a agreement on the test naming convention[1], but
for sure, there have been many (legacy) test cases before this
agreement, and I think the volunteer is highly welcome to provide patch
for them.

[1]http://incubator.apache.org/harmony/subcomponents/classlibrary/testing.html 







If nobody objects I'm going to look through the unit tests to correct
package names according to the agreement (where needed).



Thanks,

  Vladimir



On 6/8/06, Paulex Yang <[EMAIL PROTECTED] > wrote:


Vladimir,

Vladimir Ivanov wrote:
> Thanks Paulex!
>
> I did the same, but could not send results due to spam filter J
> Observations:
>
>   1. Coverage results look pretty much similar.
>   2. Exclude list looks pretty much similar too, but, looks like it
>   depends on the way of data collection (I didn't run ant task and the
> list is
>   a little bit different).
Great.
>
> In any case, I think, when we run harmony on another VM exclude list
will
> have to be updated.
>
>
>
> May be we can start publishing the coverage information on wiki pages
and
> provide some updates time to time (I can do it)?
>
+1,  and of course, you can only if  no one in the mailing list objects
and you'll have my welcome, and I think it will be even greater if these
reports can be generated regularly like what JAPI is doing:)
>
>
> One note:
>
> I noticed that different unit tests have very different package names
>
> Now the directory with all built tests copied to one place looks like:
I think we have got a agreement on the test naming convention[1], but
for sure, there have been many (legacy) test cases before this
agreement, and I think the volunteer is highly welcome to provide patch
for them.

[1]http://incubator.apache.org/harmony/subcomponents/classlibrary/testing.html 



>
>
>
> C:\coverage\tests\test>ls
>
> GZIPOutClose2.txtapi   config javax
> tests
>
> GZIPOutFinish.txtapi.injected  dazzle 
orgxml


>
> GZIPOutWrite.txt binarygifprefs
>
> Inet6Address.golden.ser  bundles   impl   serialization
>
> JDK2-3gabba.zip  com   impl.injected   test.txt
>
>
>
> I think, it would be good if tests had unified package names.
>
> Why? – so far, just common sense, just to have an order in test suite
>
> Organization (if consider all unit tests as solid test suite).
>
> Thanks,
>  Vladimir
>
> For example, my exclude list for java.io is:
> -java.io.BufferedInputStream ,
> -java.io.BufferedOutputStream,
> -java.io.File ,
> -java.io.FileChannelFactory,
> -java.io.FileDescriptor,
> -java.io.FileInputStream,
> -java.io.FileOutputStream,
> -java.io.FilterInputStream ,
> -java.io.FilterOutputStream,
> - java.io.InputStream,
> -java.io.OutputStream,
> -java.io.ObjectStreamField,
> -java.io.PrintStream
>
>
> On 6/6/06, Paulex Yang < [EMAIL PROTECTED] > wrote:
>>
>> I've attach the scripts and excluded class lists to JIRA,  please 
refer

>> to https://issues.apache.org/jira/browse/HARMONY-564 .  Enjoy it:).
>>
>> Mark Hindess wrote:
>> > On 2 June 2006 at 10:37, Paulex Yang < [EMAIL PROTECTED]> 
wrote:

>> >
>> >> Mark,
>> >>
>> >> I'm glad that there is someone else has interest on emma, I've
>> tried it
>> >> before. AFAIK, emma works by instrumentation, but sometimes for
>> classes
>> >> in bootclasspath, the instrumentation cannot work, there are two
>> cases:
>>
>> >> 1. Some instrumented classes cannot be loaded by VM.
>> >> 2. Some classes cannot be instrumented
>> >>
>> >> I have tried to look more inside to find some way to work around
>> but I
>> >> haven't got enough time yet.
>> >>
>> >> Specifically for nio-channel module, I had a list for these two
cases
>> (I
>> >> believe the data is a little outdated and should be reevaluated)
>> >> case 1.
>> >> BaseByteBuffer.class
>> >> Buffer.class
>> >> BufferFactory.class
>> >> ByteBuffer.class
>> >> CharArrayBuffer.class
>> >> CharBuffer.class
>> >> HeapByteBuffer.class
>> >> ReadWriteCharArrayBuffer.class
>> >> ReadWriteHeapByteBuffer.class
>> >> FileChannel.class
>> >> AbstractInterruptibleChannel.class
>> >> FileChannelImpl.class
>> >> WriteOnlyFileChannel.class
>> >> LockManager.class
>> >> LockManager$1.class
>> >> ReadOnlyFileChannel.class
>> >>
>> >> case 2:
>> >> ByteChannel.class
>> >> Channel.class
>> >> GatheringByteChannel.class
>> >> InterruptibleChannel.class
>> >> WritableByteChannel.class
>> >>
>> >> And I have got some ant script and more excluded list for emma, if
>> >> anyone has interests, I can upload it to JIRA.
>> >>
>> >
>> > Yes!
>> >
>> > -Mark.
>> 

Re: [classlib] [testing] Coverage (was Re: 37% of total test execution time is spent in a single test)

[Mikhail Loenko]

Cool! Sorry, I've missed it

One more thing I've missed: what is the exclude list you've finally ended with?

Thanks,
Mikhail

2006/6/13, Vladimir Ivanov <[EMAIL PROTECTED]>:

The detailed info available at  http://viv.byethost15.com/ (this address
also pointed on wiki-page).
Do you need additional information ?

Thanks,
 Vladimir


On 6/13/06, Mikhail Loenko <[EMAIL PROTECTED]> wrote:
>
> Great!
>
> Is it possible to see uncovered classes/methods/lines?
>
> Thanks,
> Mikhail
>
> P.S. I think java.awt does not currently belong to beans module,
> though who knows what the future may bring us :)
>
> 2006/6/13, Vladimir Ivanov <[EMAIL PROTECTED]>:
> > Latest Harmony API source coverage by Harmony API unit tests results I
> > stored at wiki page
> >
> > http://wiki.apache.org/harmony/Coverage_information
> >
> >
> >
> > I'm going to refresh it bi-weekly (seems, it is enough for coverage).
> >
> >
> >
> > >I think we have got a agreement on the test naming convention[1], but
> > >for sure, there have been many (legacy) test cases before this
> > >agreement, and I think the volunteer is highly welcome to provide patch
> > >for them.
> > >
> >
> 
>[1]http://incubator.apache.org/harmony/subcomponents/classlibrary/testing.html
> >
> > >
> >
> > If nobody objects I'm going to look through the unit tests to correct
> > package names according to the agreement (where needed).
> >
> >
> >
> >  Thanks,
> >
> >   Vladimir
> >
> >
> >
> > On 6/8/06, Paulex Yang <[EMAIL PROTECTED] > wrote:
> > >
> > > Vladimir,
> > >
> > > Vladimir Ivanov wrote:
> > > > Thanks Paulex!
> > > >
> > > > I did the same, but could not send results due to spam filter J
> > > > Observations:
> > > >
> > > >   1. Coverage results look pretty much similar.
> > > >   2. Exclude list looks pretty much similar too, but, looks like it
> > > >   depends on the way of data collection (I didn't run ant task and
> the
> > > > list is
> > > >   a little bit different).
> > > Great.
> > > >
> > > > In any case, I think, when we run harmony on another VM exclude list
> > > will
> > > > have to be updated.
> > > >
> > > >
> > > >
> > > > May be we can start publishing the coverage information on wiki
> pages
> > > and
> > > > provide some updates time to time (I can do it)?
> > > >
> > > +1,  and of course, you can only if  no one in the mailing list
> objects
> > > and you'll have my welcome, and I think it will be even greater if
> these
> > > reports can be generated regularly like what JAPI is doing:)
> > > >
> > > >
> > > > One note:
> > > >
> > > > I noticed that different unit tests have very different package
> names
> > > >
> > > > Now the directory with all built tests copied to one place looks
> like:
> > > I think we have got a agreement on the test naming convention[1], but
> > > for sure, there have been many (legacy) test cases before this
> > > agreement, and I think the volunteer is highly welcome to provide
> patch
> > > for them.
> > >
> > >
> [1]http://incubator.apache.org/harmony/subcomponents/classlibrary/testing.html
> > >
> > > >
> > > >
> > > >
> > > > C:\coverage\tests\test>ls
> > > >
> > > > GZIPOutClose2.txtapi   config javax
> > > > tests
> > > >
> > > > GZIPOutFinish.txtapi.injected  dazzle
> orgxml
> > >
> > > >
> > > > GZIPOutWrite.txt binarygifprefs
> > > >
> > > > Inet6Address.golden.ser  bundles   impl   serialization
> > > >
> > > > JDK2-3gabba.zip  com   impl.injected   test.txt
> > > >
> > > >
> > > >
> > > > I think, it would be good if tests had unified package names.
> > > >
> > > > Why? – so far, just common sense, just to have an order in test
> suite
> > > >
> > > > Organization (if consider all unit tests as solid test suite).
> > > >
> > > > Thanks,
> > > >  Vladimir
> > > >
> > > > For example, my exclude list for java.io is:
> > > > -java.io.BufferedInputStream ,
> > > > -java.io.BufferedOutputStream,
> > > > -java.io.File ,
> > > > -java.io.FileChannelFactory,
> > > > -java.io.FileDescriptor,
> > > > -java.io.FileInputStream,
> > > > -java.io.FileOutputStream,
> > > > -java.io.FilterInputStream ,
> > > > -java.io.FilterOutputStream,
> > > > - java.io.InputStream,
> > > > -java.io.OutputStream,
> > > > -java.io.ObjectStreamField,
> > > > -java.io.PrintStream
> > > >
> > > >
> > > > On 6/6/06, Paulex Yang < [EMAIL PROTECTED] > wrote:
> > > >>
> > > >> I've attach the scripts and excluded class lists to JIRA,  please
> refer
> > > >> to https://issues.apache.org/jira/browse/HARMONY-564 .  Enjoy it:).
> > > >>
> > > >> Mark Hindess wrote:
> > > >> > On 2 June 2006 at 10:37, Paulex Yang < [EMAIL PROTECTED]>
> wrote:
> > > >> >
> > > >> >> Mark,
> > > >> >>
> > > >> >> I'm glad that there is someone else has interest on emma, I've
> > > >> tried it
> > > >> >> before. AFAIK, emma works by instrumentation, but sometimes for
> > > >> classes
> > > >> >> in bootclasspath, the instrumentation cannot work, there are two
> >

Re: [classlib] [testing] Coverage (was Re: 37% of total test execution time is spent in a single test)

[Vladimir Ivanov]

The detailed info available at  http://viv.byethost15.com/ (this address
also pointed on wiki-page).
Do you need additional information ?

Thanks,
 Vladimir


On 6/13/06, Mikhail Loenko <[EMAIL PROTECTED]> wrote:


Great!

Is it possible to see uncovered classes/methods/lines?

Thanks,
Mikhail

P.S. I think java.awt does not currently belong to beans module,
though who knows what the future may bring us :)

2006/6/13, Vladimir Ivanov <[EMAIL PROTECTED]>:
> Latest Harmony API source coverage by Harmony API unit tests results I
> stored at wiki page
>
> http://wiki.apache.org/harmony/Coverage_information
>
>
>
> I'm going to refresh it bi-weekly (seems, it is enough for coverage).
>
>
>
> >I think we have got a agreement on the test naming convention[1], but
> >for sure, there have been many (legacy) test cases before this
> >agreement, and I think the volunteer is highly welcome to provide patch
> >for them.
> >
>
>[1]http://incubator.apache.org/harmony/subcomponents/classlibrary/testing.html
>
> >
>
> If nobody objects I'm going to look through the unit tests to correct
> package names according to the agreement (where needed).
>
>
>
>  Thanks,
>
>   Vladimir
>
>
>
> On 6/8/06, Paulex Yang <[EMAIL PROTECTED] > wrote:
> >
> > Vladimir,
> >
> > Vladimir Ivanov wrote:
> > > Thanks Paulex!
> > >
> > > I did the same, but could not send results due to spam filter J
> > > Observations:
> > >
> > >   1. Coverage results look pretty much similar.
> > >   2. Exclude list looks pretty much similar too, but, looks like it
> > >   depends on the way of data collection (I didn't run ant task and
the
> > > list is
> > >   a little bit different).
> > Great.
> > >
> > > In any case, I think, when we run harmony on another VM exclude list
> > will
> > > have to be updated.
> > >
> > >
> > >
> > > May be we can start publishing the coverage information on wiki
pages
> > and
> > > provide some updates time to time (I can do it)?
> > >
> > +1,  and of course, you can only if  no one in the mailing list
objects
> > and you'll have my welcome, and I think it will be even greater if
these
> > reports can be generated regularly like what JAPI is doing:)
> > >
> > >
> > > One note:
> > >
> > > I noticed that different unit tests have very different package
names
> > >
> > > Now the directory with all built tests copied to one place looks
like:
> > I think we have got a agreement on the test naming convention[1], but
> > for sure, there have been many (legacy) test cases before this
> > agreement, and I think the volunteer is highly welcome to provide
patch
> > for them.
> >
> >
[1]http://incubator.apache.org/harmony/subcomponents/classlibrary/testing.html
> >
> > >
> > >
> > >
> > > C:\coverage\tests\test>ls
> > >
> > > GZIPOutClose2.txtapi   config javax
> > > tests
> > >
> > > GZIPOutFinish.txtapi.injected  dazzle
orgxml
> >
> > >
> > > GZIPOutWrite.txt binarygifprefs
> > >
> > > Inet6Address.golden.ser  bundles   impl   serialization
> > >
> > > JDK2-3gabba.zip  com   impl.injected   test.txt
> > >
> > >
> > >
> > > I think, it would be good if tests had unified package names.
> > >
> > > Why? – so far, just common sense, just to have an order in test
suite
> > >
> > > Organization (if consider all unit tests as solid test suite).
> > >
> > > Thanks,
> > >  Vladimir
> > >
> > > For example, my exclude list for java.io is:
> > > -java.io.BufferedInputStream ,
> > > -java.io.BufferedOutputStream,
> > > -java.io.File ,
> > > -java.io.FileChannelFactory,
> > > -java.io.FileDescriptor,
> > > -java.io.FileInputStream,
> > > -java.io.FileOutputStream,
> > > -java.io.FilterInputStream ,
> > > -java.io.FilterOutputStream,
> > > - java.io.InputStream,
> > > -java.io.OutputStream,
> > > -java.io.ObjectStreamField,
> > > -java.io.PrintStream
> > >
> > >
> > > On 6/6/06, Paulex Yang < [EMAIL PROTECTED] > wrote:
> > >>
> > >> I've attach the scripts and excluded class lists to JIRA,  please
refer
> > >> to https://issues.apache.org/jira/browse/HARMONY-564 .  Enjoy it:).
> > >>
> > >> Mark Hindess wrote:
> > >> > On 2 June 2006 at 10:37, Paulex Yang < [EMAIL PROTECTED]>
wrote:
> > >> >
> > >> >> Mark,
> > >> >>
> > >> >> I'm glad that there is someone else has interest on emma, I've
> > >> tried it
> > >> >> before. AFAIK, emma works by instrumentation, but sometimes for
> > >> classes
> > >> >> in bootclasspath, the instrumentation cannot work, there are two
> > >> cases:
> > >>
> > >> >> 1. Some instrumented classes cannot be loaded by VM.
> > >> >> 2. Some classes cannot be instrumented
> > >> >>
> > >> >> I have tried to look more inside to find some way to work around
> > >> but I
> > >> >> haven't got enough time yet.
> > >> >>
> > >> >> Specifically for nio-channel module, I had a list for these two
> > cases
> > >> (I
> > >> >> believe the data is a little outdated and should be reevaluated)
> > >> >> case 1.
> > >> >> BaseByteBuffer.

Re: [classlib] [testing] Coverage (was Re: 37% of total test execution time is spent in a single test)

[Tim Ellison]

Mikhail Loenko wrote:
> Great!

Yep, that's great.

> Is it possible to see uncovered classes/methods/lines?

There is a link at the top of the wiki page to show details.

> Thanks,
> Mikhail
> 
> P.S. I think java.awt does not currently belong to beans module,
> though who knows what the future may bring us :)

That's not funny ;-)

Regards,
Tim

-- 

Tim Ellison ([EMAIL PROTECTED])
IBM Java technology centre, UK.

-
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [classlib] [testing] Coverage (was Re: 37% of total test execution time is spent in a single test)

[Mikhail Loenko]

Great!

Is it possible to see uncovered classes/methods/lines?

Thanks,
Mikhail

P.S. I think java.awt does not currently belong to beans module,
though who knows what the future may bring us :)

2006/6/13, Vladimir Ivanov <[EMAIL PROTECTED]>:

Latest Harmony API source coverage by Harmony API unit tests results I
stored at wiki page

http://wiki.apache.org/harmony/Coverage_information



I'm going to refresh it bi-weekly (seems, it is enough for coverage).



>I think we have got a agreement on the test naming convention[1], but
>for sure, there have been many (legacy) test cases before this
>agreement, and I think the volunteer is highly welcome to provide patch
>for them.
>
>[1]http://incubator.apache.org/harmony/subcomponents/classlibrary/testing.html

>

If nobody objects I'm going to look through the unit tests to correct
package names according to the agreement (where needed).



 Thanks,

  Vladimir



On 6/8/06, Paulex Yang <[EMAIL PROTECTED] > wrote:
>
> Vladimir,
>
> Vladimir Ivanov wrote:
> > Thanks Paulex!
> >
> > I did the same, but could not send results due to spam filter J
> > Observations:
> >
> >   1. Coverage results look pretty much similar.
> >   2. Exclude list looks pretty much similar too, but, looks like it
> >   depends on the way of data collection (I didn't run ant task and the
> > list is
> >   a little bit different).
> Great.
> >
> > In any case, I think, when we run harmony on another VM exclude list
> will
> > have to be updated.
> >
> >
> >
> > May be we can start publishing the coverage information on wiki pages
> and
> > provide some updates time to time (I can do it)?
> >
> +1,  and of course, you can only if  no one in the mailing list objects
> and you'll have my welcome, and I think it will be even greater if these
> reports can be generated regularly like what JAPI is doing:)
> >
> >
> > One note:
> >
> > I noticed that different unit tests have very different package names
> >
> > Now the directory with all built tests copied to one place looks like:
> I think we have got a agreement on the test naming convention[1], but
> for sure, there have been many (legacy) test cases before this
> agreement, and I think the volunteer is highly welcome to provide patch
> for them.
>
> [1]http://incubator.apache.org/harmony/subcomponents/classlibrary/testing.html
>
> >
> >
> >
> > C:\coverage\tests\test>ls
> >
> > GZIPOutClose2.txtapi   config javax
> > tests
> >
> > GZIPOutFinish.txtapi.injected  dazzle orgxml
>
> >
> > GZIPOutWrite.txt binarygifprefs
> >
> > Inet6Address.golden.ser  bundles   impl   serialization
> >
> > JDK2-3gabba.zip  com   impl.injected   test.txt
> >
> >
> >
> > I think, it would be good if tests had unified package names.
> >
> > Why? – so far, just common sense, just to have an order in test suite
> >
> > Organization (if consider all unit tests as solid test suite).
> >
> > Thanks,
> >  Vladimir
> >
> > For example, my exclude list for java.io is:
> > -java.io.BufferedInputStream ,
> > -java.io.BufferedOutputStream,
> > -java.io.File ,
> > -java.io.FileChannelFactory,
> > -java.io.FileDescriptor,
> > -java.io.FileInputStream,
> > -java.io.FileOutputStream,
> > -java.io.FilterInputStream ,
> > -java.io.FilterOutputStream,
> > - java.io.InputStream,
> > -java.io.OutputStream,
> > -java.io.ObjectStreamField,
> > -java.io.PrintStream
> >
> >
> > On 6/6/06, Paulex Yang < [EMAIL PROTECTED] > wrote:
> >>
> >> I've attach the scripts and excluded class lists to JIRA,  please refer
> >> to https://issues.apache.org/jira/browse/HARMONY-564 .  Enjoy it:).
> >>
> >> Mark Hindess wrote:
> >> > On 2 June 2006 at 10:37, Paulex Yang < [EMAIL PROTECTED]> wrote:
> >> >
> >> >> Mark,
> >> >>
> >> >> I'm glad that there is someone else has interest on emma, I've
> >> tried it
> >> >> before. AFAIK, emma works by instrumentation, but sometimes for
> >> classes
> >> >> in bootclasspath, the instrumentation cannot work, there are two
> >> cases:
> >>
> >> >> 1. Some instrumented classes cannot be loaded by VM.
> >> >> 2. Some classes cannot be instrumented
> >> >>
> >> >> I have tried to look more inside to find some way to work around
> >> but I
> >> >> haven't got enough time yet.
> >> >>
> >> >> Specifically for nio-channel module, I had a list for these two
> cases
> >> (I
> >> >> believe the data is a little outdated and should be reevaluated)
> >> >> case 1.
> >> >> BaseByteBuffer.class
> >> >> Buffer.class
> >> >> BufferFactory.class
> >> >> ByteBuffer.class
> >> >> CharArrayBuffer.class
> >> >> CharBuffer.class
> >> >> HeapByteBuffer.class
> >> >> ReadWriteCharArrayBuffer.class
> >> >> ReadWriteHeapByteBuffer.class
> >> >> FileChannel.class
> >> >> AbstractInterruptibleChannel.class
> >> >> FileChannelImpl.class
> >> >> WriteOnlyFileChannel.class
> >> >> LockManager.class
> >> >> LockManager$1.class
> >> >> ReadOnlyFileChannel.class
> >> >>
> >> >> case 2:
>

Re: [classlib] [testing] Coverage (was Re: 37% of total test execution time is spent in a single test)

[Vladimir Ivanov]

Latest Harmony API source coverage by Harmony API unit tests results I
stored at wiki page

http://wiki.apache.org/harmony/Coverage_information



I'm going to refresh it bi-weekly (seems, it is enough for coverage).




I think we have got a agreement on the test naming convention[1], but
for sure, there have been many (legacy) test cases before this
agreement, and I think the volunteer is highly welcome to provide patch
for them.

[1]http://incubator.apache.org/harmony/subcomponents/classlibrary/testing.html






If nobody objects I'm going to look through the unit tests to correct
package names according to the agreement (where needed).



Thanks,

  Vladimir



On 6/8/06, Paulex Yang <[EMAIL PROTECTED] > wrote:


Vladimir,

Vladimir Ivanov wrote:
> Thanks Paulex!
>
> I did the same, but could not send results due to spam filter J
> Observations:
>
>   1. Coverage results look pretty much similar.
>   2. Exclude list looks pretty much similar too, but, looks like it
>   depends on the way of data collection (I didn't run ant task and the
> list is
>   a little bit different).
Great.
>
> In any case, I think, when we run harmony on another VM exclude list
will
> have to be updated.
>
>
>
> May be we can start publishing the coverage information on wiki pages
and
> provide some updates time to time (I can do it)?
>
+1,  and of course, you can only if  no one in the mailing list objects
and you'll have my welcome, and I think it will be even greater if these
reports can be generated regularly like what JAPI is doing:)
>
>
> One note:
>
> I noticed that different unit tests have very different package names
>
> Now the directory with all built tests copied to one place looks like:
I think we have got a agreement on the test naming convention[1], but
for sure, there have been many (legacy) test cases before this
agreement, and I think the volunteer is highly welcome to provide patch
for them.

[1]http://incubator.apache.org/harmony/subcomponents/classlibrary/testing.html

>
>
>
> C:\coverage\tests\test>ls
>
> GZIPOutClose2.txtapi   config javax
> tests
>
> GZIPOutFinish.txtapi.injected  dazzle orgxml

>
> GZIPOutWrite.txt binarygifprefs
>
> Inet6Address.golden.ser  bundles   impl   serialization
>
> JDK2-3gabba.zip  com   impl.injected   test.txt
>
>
>
> I think, it would be good if tests had unified package names.
>
> Why? – so far, just common sense, just to have an order in test suite
>
> Organization (if consider all unit tests as solid test suite).
>
> Thanks,
>  Vladimir
>
> For example, my exclude list for java.io is:
> -java.io.BufferedInputStream ,
> -java.io.BufferedOutputStream,
> -java.io.File ,
> -java.io.FileChannelFactory,
> -java.io.FileDescriptor,
> -java.io.FileInputStream,
> -java.io.FileOutputStream,
> -java.io.FilterInputStream ,
> -java.io.FilterOutputStream,
> - java.io.InputStream,
> -java.io.OutputStream,
> -java.io.ObjectStreamField,
> -java.io.PrintStream
>
>
> On 6/6/06, Paulex Yang < [EMAIL PROTECTED] > wrote:
>>
>> I've attach the scripts and excluded class lists to JIRA,  please refer
>> to https://issues.apache.org/jira/browse/HARMONY-564 .  Enjoy it:).
>>
>> Mark Hindess wrote:
>> > On 2 June 2006 at 10:37, Paulex Yang < [EMAIL PROTECTED]> wrote:
>> >
>> >> Mark,
>> >>
>> >> I'm glad that there is someone else has interest on emma, I've
>> tried it
>> >> before. AFAIK, emma works by instrumentation, but sometimes for
>> classes
>> >> in bootclasspath, the instrumentation cannot work, there are two
>> cases:
>>
>> >> 1. Some instrumented classes cannot be loaded by VM.
>> >> 2. Some classes cannot be instrumented
>> >>
>> >> I have tried to look more inside to find some way to work around
>> but I
>> >> haven't got enough time yet.
>> >>
>> >> Specifically for nio-channel module, I had a list for these two
cases
>> (I
>> >> believe the data is a little outdated and should be reevaluated)
>> >> case 1.
>> >> BaseByteBuffer.class
>> >> Buffer.class
>> >> BufferFactory.class
>> >> ByteBuffer.class
>> >> CharArrayBuffer.class
>> >> CharBuffer.class
>> >> HeapByteBuffer.class
>> >> ReadWriteCharArrayBuffer.class
>> >> ReadWriteHeapByteBuffer.class
>> >> FileChannel.class
>> >> AbstractInterruptibleChannel.class
>> >> FileChannelImpl.class
>> >> WriteOnlyFileChannel.class
>> >> LockManager.class
>> >> LockManager$1.class
>> >> ReadOnlyFileChannel.class
>> >>
>> >> case 2:
>> >> ByteChannel.class
>> >> Channel.class
>> >> GatheringByteChannel.class
>> >> InterruptibleChannel.class
>> >> WritableByteChannel.class
>> >>
>> >> And I have got some ant script and more excluded list for emma, if
>> >> anyone has interests, I can upload it to JIRA.
>> >>
>> >
>> > Yes!
>> >
>> > -Mark.
>> >
>> >
>> >> Mark Hindess wrote:
>> >>
>> >>> Anyone tried using emma (emma.sf.net) to look at test coverage
>> for our
>> >>> tests?  That might help ensure we don't trim them down too much?
>> >>

Re: [classlib] [testing] Coverage (was Re: 37% of total test execution time is spent in a single test)

[Paulex Yang]

Mikhail Loenko wrote:

2006/6/8, Paulex Yang <[EMAIL PROTECTED]>:

Vladimir,

Vladimir Ivanov wrote:
> Thanks Paulex!
>
> I did the same, but could not send results due to spam filter J
> Observations:
>
>   1. Coverage results look pretty much similar.
>   2. Exclude list looks pretty much similar too, but, looks like it
>   depends on the way of data collection (I didn't run ant task and the
> list is
>   a little bit different).
Great.
>
> In any case, I think, when we run harmony on another VM exclude 
list will

> have to be updated.
>
>
>
> May be we can start publishing the coverage information on wiki 
pages and

> provide some updates time to time (I can do it)?
>
+1,  and of course, you can only if  no one in the mailing list objects
and you'll have my welcome, and I think it will be even greater if these
reports can be generated regularly like what JAPI is doing:)


Does it make sense to create corresponding build target?

Sure, I think so.


Thanks,
Mikhail


>
>
> One note:
>
> I noticed that different unit tests have very different package names
>
> Now the directory with all built tests copied to one place looks like:
I think we have got a agreement on the test naming convention[1], but
for sure, there have been many (legacy) test cases before this
agreement, and I think the volunteer is highly welcome to provide patch
for them.

[1]http://incubator.apache.org/harmony/subcomponents/classlibrary/testing.html 


>
>
>
> C:\coverage\tests\test>ls
>
> GZIPOutClose2.txtapi   config javax
> tests
>
> GZIPOutFinish.txtapi.injected  dazzle 
orgxml

>
> GZIPOutWrite.txt binarygifprefs
>
> Inet6Address.golden.ser  bundles   impl   serialization
>
> JDK2-3gabba.zip  com   impl.injected  test.txt
>
>
>
> I think, it would be good if tests had unified package names.
>
> Why? – so far, just common sense, just to have an order in test suite
>
> Organization (if consider all unit tests as solid test suite).
>
> Thanks,
>  Vladimir
>
> For example, my exclude list for java.io is:
> -java.io.BufferedInputStream,
> -java.io.BufferedOutputStream,
> -java.io.File,
> -java.io.FileChannelFactory,
> -java.io.FileDescriptor,
> -java.io.FileInputStream,
> -java.io.FileOutputStream,
> -java.io.FilterInputStream ,
> -java.io.FilterOutputStream,
> -java.io.InputStream,
> -java.io.OutputStream,
> -java.io.ObjectStreamField,
> -java.io.PrintStream
>
>
> On 6/6/06, Paulex Yang <[EMAIL PROTECTED]> wrote:
>>
>> I've attach the scripts and excluded class lists to JIRA,  please 
refer

>> to https://issues.apache.org/jira/browse/HARMONY-564.  Enjoy it:).
>>
>> Mark Hindess wrote:
>> > On 2 June 2006 at 10:37, Paulex Yang <[EMAIL PROTECTED]> wrote:
>> >
>> >> Mark,
>> >>
>> >> I'm glad that there is someone else has interest on emma, I've
>> tried it
>> >> before. AFAIK, emma works by instrumentation, but sometimes for
>> classes
>> >> in bootclasspath, the instrumentation cannot work, there are two
>> cases:
>>
>> >> 1. Some instrumented classes cannot be loaded by VM.
>> >> 2. Some classes cannot be instrumented
>> >>
>> >> I have tried to look more inside to find some way to work around
>> but I
>> >> haven't got enough time yet.
>> >>
>> >> Specifically for nio-channel module, I had a list for these two 
cases

>> (I
>> >> believe the data is a little outdated and should be reevaluated)
>> >> case 1.
>> >> BaseByteBuffer.class
>> >> Buffer.class
>> >> BufferFactory.class
>> >> ByteBuffer.class
>> >> CharArrayBuffer.class
>> >> CharBuffer.class
>> >> HeapByteBuffer.class
>> >> ReadWriteCharArrayBuffer.class
>> >> ReadWriteHeapByteBuffer.class
>> >> FileChannel.class
>> >> AbstractInterruptibleChannel.class
>> >> FileChannelImpl.class
>> >> WriteOnlyFileChannel.class
>> >> LockManager.class
>> >> LockManager$1.class
>> >> ReadOnlyFileChannel.class
>> >>
>> >> case 2:
>> >> ByteChannel.class
>> >> Channel.class
>> >> GatheringByteChannel.class
>> >> InterruptibleChannel.class
>> >> WritableByteChannel.class
>> >>
>> >> And I have got some ant script and more excluded list for emma, if
>> >> anyone has interests, I can upload it to JIRA.
>> >>
>> >
>> > Yes!
>> >
>> > -Mark.
>> >
>> >
>> >> Mark Hindess wrote:
>> >>
>> >>> Anyone tried using emma (emma.sf.net) to look at test coverage
>> for our
>> >>> tests?  That might help ensure we don't trim them down too much?
>> >>>
>> >>> I suspect we will soon reach a point where there are 
significantly

>> fewer
>> >>> obvious opportunities for small contributions - e.g.
>> 1.5generification,
>> >>> etc from looking at JAPI reports.  Having test coverage reports
>> might
>> >>> help by highlighting areas for improvement.
>> >>>
>> >>> I had a quick try with:
>> >>>
>> >>>   ant -f make/build.xml
>> >>>   ant -f modules/nio/make/build.xml test
>> >>>   java -cp emma.jar emma instr -m overwrite -cp
>> deploy/jdk/jre/lib/boot/nio
>> >>>
>> >> .jar
>> >>
>> >>> and then:
>> >>>
>>

Re: [classlib] [testing] Coverage (was Re: 37% of total test execution time is spent in a single test)

[Mikhail Loenko]

2006/6/8, Paulex Yang <[EMAIL PROTECTED]>:

Vladimir,

Vladimir Ivanov wrote:
> Thanks Paulex!
>
> I did the same, but could not send results due to spam filter J
> Observations:
>
>   1. Coverage results look pretty much similar.
>   2. Exclude list looks pretty much similar too, but, looks like it
>   depends on the way of data collection (I didn't run ant task and the
> list is
>   a little bit different).
Great.
>
> In any case, I think, when we run harmony on another VM exclude list will
> have to be updated.
>
>
>
> May be we can start publishing the coverage information on wiki pages and
> provide some updates time to time (I can do it)?
>
+1,  and of course, you can only if  no one in the mailing list objects
and you'll have my welcome, and I think it will be even greater if these
reports can be generated regularly like what JAPI is doing:)


Does it make sense to create corresponding build target?

Thanks,
Mikhail


>
>
> One note:
>
> I noticed that different unit tests have very different package names
>
> Now the directory with all built tests copied to one place looks like:
I think we have got a agreement on the test naming convention[1], but
for sure, there have been many (legacy) test cases before this
agreement, and I think the volunteer is highly welcome to provide patch
for them.

[1]http://incubator.apache.org/harmony/subcomponents/classlibrary/testing.html
>
>
>
> C:\coverage\tests\test>ls
>
> GZIPOutClose2.txtapi   config javax
> tests
>
> GZIPOutFinish.txtapi.injected  dazzle orgxml
>
> GZIPOutWrite.txt binarygifprefs
>
> Inet6Address.golden.ser  bundles   impl   serialization
>
> JDK2-3gabba.zip  com   impl.injected  test.txt
>
>
>
> I think, it would be good if tests had unified package names.
>
> Why? – so far, just common sense, just to have an order in test suite
>
> Organization (if consider all unit tests as solid test suite).
>
> Thanks,
>  Vladimir
>
> For example, my exclude list for java.io is:
> -java.io.BufferedInputStream,
> -java.io.BufferedOutputStream,
> -java.io.File,
> -java.io.FileChannelFactory,
> -java.io.FileDescriptor,
> -java.io.FileInputStream,
> -java.io.FileOutputStream,
> -java.io.FilterInputStream ,
> -java.io.FilterOutputStream,
> -java.io.InputStream,
> -java.io.OutputStream,
> -java.io.ObjectStreamField,
> -java.io.PrintStream
>
>
> On 6/6/06, Paulex Yang <[EMAIL PROTECTED]> wrote:
>>
>> I've attach the scripts and excluded class lists to JIRA,  please refer
>> to https://issues.apache.org/jira/browse/HARMONY-564.  Enjoy it:).
>>
>> Mark Hindess wrote:
>> > On 2 June 2006 at 10:37, Paulex Yang <[EMAIL PROTECTED]> wrote:
>> >
>> >> Mark,
>> >>
>> >> I'm glad that there is someone else has interest on emma, I've
>> tried it
>> >> before. AFAIK, emma works by instrumentation, but sometimes for
>> classes
>> >> in bootclasspath, the instrumentation cannot work, there are two
>> cases:
>>
>> >> 1. Some instrumented classes cannot be loaded by VM.
>> >> 2. Some classes cannot be instrumented
>> >>
>> >> I have tried to look more inside to find some way to work around
>> but I
>> >> haven't got enough time yet.
>> >>
>> >> Specifically for nio-channel module, I had a list for these two cases
>> (I
>> >> believe the data is a little outdated and should be reevaluated)
>> >> case 1.
>> >> BaseByteBuffer.class
>> >> Buffer.class
>> >> BufferFactory.class
>> >> ByteBuffer.class
>> >> CharArrayBuffer.class
>> >> CharBuffer.class
>> >> HeapByteBuffer.class
>> >> ReadWriteCharArrayBuffer.class
>> >> ReadWriteHeapByteBuffer.class
>> >> FileChannel.class
>> >> AbstractInterruptibleChannel.class
>> >> FileChannelImpl.class
>> >> WriteOnlyFileChannel.class
>> >> LockManager.class
>> >> LockManager$1.class
>> >> ReadOnlyFileChannel.class
>> >>
>> >> case 2:
>> >> ByteChannel.class
>> >> Channel.class
>> >> GatheringByteChannel.class
>> >> InterruptibleChannel.class
>> >> WritableByteChannel.class
>> >>
>> >> And I have got some ant script and more excluded list for emma, if
>> >> anyone has interests, I can upload it to JIRA.
>> >>
>> >
>> > Yes!
>> >
>> > -Mark.
>> >
>> >
>> >> Mark Hindess wrote:
>> >>
>> >>> Anyone tried using emma (emma.sf.net) to look at test coverage
>> for our
>> >>> tests?  That might help ensure we don't trim them down too much?
>> >>>
>> >>> I suspect we will soon reach a point where there are significantly
>> fewer
>> >>> obvious opportunities for small contributions - e.g.
>> 1.5generification,
>> >>> etc from looking at JAPI reports.  Having test coverage reports
>> might
>> >>> help by highlighting areas for improvement.
>> >>>
>> >>> I had a quick try with:
>> >>>
>> >>>   ant -f make/build.xml
>> >>>   ant -f modules/nio/make/build.xml test
>> >>>   java -cp emma.jar emma instr -m overwrite -cp
>> deploy/jdk/jre/lib/boot/nio
>> >>>
>> >> .jar
>> >>
>> >>> and then:
>> >>>
>> >>>   java -Xbootclasspath/p: emma.jar \
>> >>>-c

Re: [classlib] [testing] Coverage (was Re: 37% of total test execution time is spent in a single test)

[Paulex Yang]

Vladimir,

Vladimir Ivanov wrote:

Thanks Paulex!

I did the same, but could not send results due to spam filter J
Observations:

  1. Coverage results look pretty much similar.
  2. Exclude list looks pretty much similar too, but, looks like it
  depends on the way of data collection (I didn't run ant task and the 
list is

  a little bit different).

Great.


In any case, I think, when we run harmony on another VM exclude list will
have to be updated.



May be we can start publishing the coverage information on wiki pages and
provide some updates time to time (I can do it)?

+1,  and of course, you can only if  no one in the mailing list objects 
and you'll have my welcome, and I think it will be even greater if these 
reports can be generated regularly like what JAPI is doing:)



One note:

I noticed that different unit tests have very different package names

Now the directory with all built tests copied to one place looks like:
I think we have got a agreement on the test naming convention[1], but 
for sure, there have been many (legacy) test cases before this 
agreement, and I think the volunteer is highly welcome to provide patch 
for them.


[1]http://incubator.apache.org/harmony/subcomponents/classlibrary/testing.html




C:\coverage\tests\test>ls

GZIPOutClose2.txtapi   config javax  
tests


GZIPOutFinish.txtapi.injected  dazzle orgxml

GZIPOutWrite.txt binarygifprefs

Inet6Address.golden.ser  bundles   impl   serialization

JDK2-3gabba.zip  com   impl.injected  test.txt



I think, it would be good if tests had unified package names.

Why? – so far, just common sense, just to have an order in test suite

Organization (if consider all unit tests as solid test suite).

Thanks,
 Vladimir

For example, my exclude list for java.io is:
-java.io.BufferedInputStream,
-java.io.BufferedOutputStream,
-java.io.File,
-java.io.FileChannelFactory,
-java.io.FileDescriptor,
-java.io.FileInputStream,
-java.io.FileOutputStream,
-java.io.FilterInputStream ,
-java.io.FilterOutputStream,
-java.io.InputStream,
-java.io.OutputStream,
-java.io.ObjectStreamField,
-java.io.PrintStream


On 6/6/06, Paulex Yang <[EMAIL PROTECTED]> wrote:


I've attach the scripts and excluded class lists to JIRA,  please refer
to https://issues.apache.org/jira/browse/HARMONY-564.  Enjoy it:).

Mark Hindess wrote:
> On 2 June 2006 at 10:37, Paulex Yang <[EMAIL PROTECTED]> wrote:
>
>> Mark,
>>
>> I'm glad that there is someone else has interest on emma, I've 
tried it
>> before. AFAIK, emma works by instrumentation, but sometimes for 
classes
>> in bootclasspath, the instrumentation cannot work, there are two 
cases:


>> 1. Some instrumented classes cannot be loaded by VM.
>> 2. Some classes cannot be instrumented
>>
>> I have tried to look more inside to find some way to work around 
but I

>> haven't got enough time yet.
>>
>> Specifically for nio-channel module, I had a list for these two cases
(I
>> believe the data is a little outdated and should be reevaluated)
>> case 1.
>> BaseByteBuffer.class
>> Buffer.class
>> BufferFactory.class
>> ByteBuffer.class
>> CharArrayBuffer.class
>> CharBuffer.class
>> HeapByteBuffer.class
>> ReadWriteCharArrayBuffer.class
>> ReadWriteHeapByteBuffer.class
>> FileChannel.class
>> AbstractInterruptibleChannel.class
>> FileChannelImpl.class
>> WriteOnlyFileChannel.class
>> LockManager.class
>> LockManager$1.class
>> ReadOnlyFileChannel.class
>>
>> case 2:
>> ByteChannel.class
>> Channel.class
>> GatheringByteChannel.class
>> InterruptibleChannel.class
>> WritableByteChannel.class
>>
>> And I have got some ant script and more excluded list for emma, if
>> anyone has interests, I can upload it to JIRA.
>>
>
> Yes!
>
> -Mark.
>
>
>> Mark Hindess wrote:
>>
>>> Anyone tried using emma (emma.sf.net) to look at test coverage 
for our

>>> tests?  That might help ensure we don't trim them down too much?
>>>
>>> I suspect we will soon reach a point where there are significantly
fewer
>>> obvious opportunities for small contributions - e.g. 
1.5generification,
>>> etc from looking at JAPI reports.  Having test coverage reports 
might

>>> help by highlighting areas for improvement.
>>>
>>> I had a quick try with:
>>>
>>>   ant -f make/build.xml
>>>   ant -f modules/nio/make/build.xml test
>>>   java -cp emma.jar emma instr -m overwrite -cp
deploy/jdk/jre/lib/boot/nio
>>>
>> .jar
>>
>>> and then:
>>>
>>>   java -Xbootclasspath/p: emma.jar \
>>>-cp build/tests:modules/nio/bin/test:junit.jar:. \
>>>junit.textui.TestRunner \
>>>org.apache.harmony.tests.java.nio.channels.SocketChannelTest
>>>
>>> (Running all the tests is a little tricky because test depends on
build,
>>> which depends on clean which wipes out the instr'd jar. ;-( )
>>>
>>> Sadly it dies horribly with the stack trace below.  I'll take 
another

>>> look when I have a little more time, but I thought I'd mention it i

Re: [classlib] [testing] Coverage (was Re: 37% of total test execution time is spent in a single test)

[Vladimir Ivanov]

Thanks Paulex!

I did the same, but could not send results due to spam filter J
Observations:

  1. Coverage results look pretty much similar.
  2. Exclude list looks pretty much similar too, but, looks like it
  depends on the way of data collection (I didn't run ant task and the list is
  a little bit different).

In any case, I think, when we run harmony on another VM exclude list will
have to be updated.



May be we can start publishing the coverage information on wiki pages and
provide some updates time to time (I can do it)?



One note:

I noticed that different unit tests have very different package names

Now the directory with all built tests copied to one place looks like:



C:\coverage\tests\test>ls

GZIPOutClose2.txtapi   config javax  tests

GZIPOutFinish.txtapi.injected  dazzle orgxml

GZIPOutWrite.txt binarygifprefs

Inet6Address.golden.ser  bundles   impl   serialization

JDK2-3gabba.zip  com   impl.injected  test.txt



I think, it would be good if tests had unified package names.

Why? – so far, just common sense, just to have an order in test suite

Organization (if consider all unit tests as solid test suite).

Thanks,
 Vladimir

For example, my exclude list for java.io is:
-java.io.BufferedInputStream,
-java.io.BufferedOutputStream,
-java.io.File,
-java.io.FileChannelFactory,
-java.io.FileDescriptor,
-java.io.FileInputStream,
-java.io.FileOutputStream,
-java.io.FilterInputStream ,
-java.io.FilterOutputStream,
-java.io.InputStream,
-java.io.OutputStream,
-java.io.ObjectStreamField,
-java.io.PrintStream


On 6/6/06, Paulex Yang <[EMAIL PROTECTED]> wrote:


I've attach the scripts and excluded class lists to JIRA,  please refer
to https://issues.apache.org/jira/browse/HARMONY-564.  Enjoy it:).

Mark Hindess wrote:
> On 2 June 2006 at 10:37, Paulex Yang <[EMAIL PROTECTED]> wrote:
>
>> Mark,
>>
>> I'm glad that there is someone else has interest on emma, I've tried it
>> before. AFAIK, emma works by instrumentation, but sometimes for classes
>> in bootclasspath, the instrumentation cannot work, there are two cases:

>> 1. Some instrumented classes cannot be loaded by VM.
>> 2. Some classes cannot be instrumented
>>
>> I have tried to look more inside to find some way to work around but I
>> haven't got enough time yet.
>>
>> Specifically for nio-channel module, I had a list for these two cases
(I
>> believe the data is a little outdated and should be reevaluated)
>> case 1.
>> BaseByteBuffer.class
>> Buffer.class
>> BufferFactory.class
>> ByteBuffer.class
>> CharArrayBuffer.class
>> CharBuffer.class
>> HeapByteBuffer.class
>> ReadWriteCharArrayBuffer.class
>> ReadWriteHeapByteBuffer.class
>> FileChannel.class
>> AbstractInterruptibleChannel.class
>> FileChannelImpl.class
>> WriteOnlyFileChannel.class
>> LockManager.class
>> LockManager$1.class
>> ReadOnlyFileChannel.class
>>
>> case 2:
>> ByteChannel.class
>> Channel.class
>> GatheringByteChannel.class
>> InterruptibleChannel.class
>> WritableByteChannel.class
>>
>> And I have got some ant script and more excluded list for emma, if
>> anyone has interests, I can upload it to JIRA.
>>
>
> Yes!
>
> -Mark.
>
>
>> Mark Hindess wrote:
>>
>>> Anyone tried using emma (emma.sf.net) to look at test coverage for our
>>> tests?  That might help ensure we don't trim them down too much?
>>>
>>> I suspect we will soon reach a point where there are significantly
fewer
>>> obvious opportunities for small contributions - e.g. 1.5generification,
>>> etc from looking at JAPI reports.  Having test coverage reports might
>>> help by highlighting areas for improvement.
>>>
>>> I had a quick try with:
>>>
>>>   ant -f make/build.xml
>>>   ant -f modules/nio/make/build.xml test
>>>   java -cp emma.jar emma instr -m overwrite -cp
deploy/jdk/jre/lib/boot/nio
>>>
>> .jar
>>
>>> and then:
>>>
>>>   java -Xbootclasspath/p: emma.jar \
>>>-cp build/tests:modules/nio/bin/test:junit.jar:. \
>>>junit.textui.TestRunner \
>>>org.apache.harmony.tests.java.nio.channels.SocketChannelTest
>>>
>>> (Running all the tests is a little tricky because test depends on
build,
>>> which depends on clean which wipes out the instr'd jar. ;-( )
>>>
>>> Sadly it dies horribly with the stack trace below.  I'll take another
>>> look when I have a little more time, but I thought I'd mention it in
>>> case anyone else had any thoughts on the subject.
>>>
>>> Regards,
>>>
>>> Mark.
>>>
>>> Exception in thread "main" java/lang/ExceptionInInitializerError
>>> at java/lang/J9VMInternals.initialize (J9VMInternals.java:203)
>>> at java/nio/Buffer.$VRi ( Buffer.java:4294967295)
>>> at java/nio/Buffer. (Buffer.java:4294967295)
>>> at java/lang/J9VMInternals.initializeImpl (Native Method)
>>> at java/lang/J9VMInternals.initialize ( J9VMInternals.java
:185)
>>> at java/lang/J9VMInternals.initialize (J9VMInternals.java

Re: [classlib] [testing] Coverage (was Re: 37% of total test execution time is spent in a single test)

[Paulex Yang]

I've attach the scripts and excluded class lists to JIRA,  please refer 
to https://issues.apache.org/jira/browse/HARMONY-564.  Enjoy it:).


Mark Hindess wrote:

On 2 June 2006 at 10:37, Paulex Yang <[EMAIL PROTECTED]> wrote:
  

Mark,

I'm glad that there is someone else has interest on emma, I've tried it 
before. AFAIK, emma works by instrumentation, but sometimes for classes 
in bootclasspath, the instrumentation cannot work, there are two cases:

1. Some instrumented classes cannot be loaded by VM.
2. Some classes cannot be instrumented

I have tried to look more inside to find some way to work around but I 
haven't got enough time yet.


Specifically for nio-channel module, I had a list for these two cases (I 
believe the data is a little outdated and should be reevaluated)

case 1.
BaseByteBuffer.class
Buffer.class
BufferFactory.class
ByteBuffer.class
CharArrayBuffer.class
CharBuffer.class
HeapByteBuffer.class
ReadWriteCharArrayBuffer.class
ReadWriteHeapByteBuffer.class
FileChannel.class
AbstractInterruptibleChannel.class
FileChannelImpl.class
WriteOnlyFileChannel.class
LockManager.class
LockManager$1.class
ReadOnlyFileChannel.class

case 2:
ByteChannel.class
Channel.class
GatheringByteChannel.class
InterruptibleChannel.class
WritableByteChannel.class

And I have got some ant script and more excluded list for emma, if 
anyone has interests, I can upload it to JIRA.



Yes!

-Mark.

  

Mark Hindess wrote:


Anyone tried using emma (emma.sf.net) to look at test coverage for our
tests?  That might help ensure we don't trim them down too much?

I suspect we will soon reach a point where there are significantly fewer
obvious opportunities for small contributions - e.g. 1.5 generification,
etc from looking at JAPI reports.  Having test coverage reports might
help by highlighting areas for improvement.

I had a quick try with:

  ant -f make/build.xml
  ant -f modules/nio/make/build.xml test
  java -cp emma.jar emma instr -m overwrite -cp deploy/jdk/jre/lib/boot/nio
  

.jar


and then:

  java -Xbootclasspath/p:emma.jar \
   -cp build/tests:modules/nio/bin/test:junit.jar:. \
   junit.textui.TestRunner \
   org.apache.harmony.tests.java.nio.channels.SocketChannelTest

(Running all the tests is a little tricky because test depends on build, 
which depends on clean which wipes out the instr'd jar. ;-( )


Sadly it dies horribly with the stack trace below.  I'll take another
look when I have a little more time, but I thought I'd mention it in
case anyone else had any thoughts on the subject.

Regards,
 
Mark.


Exception in thread "main" java/lang/ExceptionInInitializerError
at java/lang/J9VMInternals.initialize (J9VMInternals.java:203)
at java/nio/Buffer.$VRi (Buffer.java:4294967295)
at java/nio/Buffer. (Buffer.java:4294967295)
at java/lang/J9VMInternals.initializeImpl (Native Method)
at java/lang/J9VMInternals.initialize (J9VMInternals.java:185)
at java/lang/J9VMInternals.initialize (J9VMInternals.java:154)
at java/lang/String.getBytes (String.java:783)
at org/apache/harmony/luni/util/Util.getBytes (Util.java:54)
at java/lang/ClassLoader.loadLibraryWithPath (ClassLoader.java:998)
at java/lang/ClassLoader.loadLibraryWithClassLoader (ClassLoader.ja
  

va:970)


at java/lang/System.loadLibrary (System.java:706)
at com/ibm/icu4jni/common/ICU4JNILoader.loadLibrary (Unknown Source
  

)


at com/ibm/icu4jni/converters/NativeConverter. (Unknown Sou
  

rce)


at java/lang/J9VMInternals.initializeImpl (Native Method)
at java/lang/J9VMInternals.initialize (J9VMInternals.java:185)
at com/ibm/icu4jni/charset/CharsetProviderICU.charsetForName (Unkno
  

wn Source)


at java/nio/charset/Charset.forNameInternal (Charset.java:450)
at java/nio/charset/Charset.forName (Charset.java:513)
at java/lang/String.defaultCharset (String.java:688)
at java/lang/String. (String.java:252)
at org/apache/harmony/luni/util/Util.toString (Util.java:74)
at java/lang/System.getPropertyList (Native Method)
at java/lang/System.ensureProperties (System.java:496)
at java/lang/System. (System.java:55)
at java/lang/J9VMInternals.initializeImpl (Native Method)
at java/lang/J9VMInternals.initialize (J9VMInternals.java:185)
at java/lang/ClassLoader.initializeClassLoaders (ClassLoader.java:6
  

5)


at java/lang/Thread.initialize (Thread.java:301)
at java/lang/Thread. (Thread.java:120)
java/lang/NullPointerException
at java/lang/Throwable.printStackTrace (Throwable.java:231)
at com/vladium/emma/rt/RTExitHook.createClassLoaderClosure (RTExitH
  

ook.java:63)


at com/vladium/emma/rt/RT.reset (RT.java:92)
at com/vladium/emma/rt/RT. (RT.java:238)
at java/lang/J9VMInternals.initializeImpl (Native Method)

Re: [classlib] [testing] Coverage (was Re: 37% of total test execution time is spent in a single test)

[Vladimir Ivanov]

Paulex,




And I have got some ant script and more excluded list for emma, if
anyone has interests, I can upload it to JIRA.


Yes please, upload the list into JIRA. I'm going to experiment with the list
and source coverage of HY API too.



When I tried to experiment with HY API by unit tests code coverage
measurement via Emma I saw such errors.

The reason why runtime dies is that Emma instruments core classes and
inserts calls to its classes, which, in their turn, depend on the being
initialized core classes (for example, initialization of java.lang.Object is
working, it calls instrumented code, i.e. Emma class to store profiling
information, but the class in its turn depends on Object).

Thanks,
 Vladimir


On 6/2/06, Mark Hindess <[EMAIL PROTECTED] > wrote:



On 2 June 2006 at 10:37, Paulex Yang < [EMAIL PROTECTED] > wrote:
>
> Mark,
>
> I'm glad that there is someone else has interest on emma, I've tried it
> before. AFAIK, emma works by instrumentation, but sometimes for classes
> in bootclasspath, the instrumentation cannot work, there are two cases:
> 1. Some instrumented classes cannot be loaded by VM.
> 2. Some classes cannot be instrumented
>
> I have tried to look more inside to find some way to work around but I
> haven't got enough time yet.
>
> Specifically for nio-channel module, I had a list for these two cases (I
> believe the data is a little outdated and should be reevaluated)
> case 1.
> BaseByteBuffer.class
> Buffer.class
> BufferFactory.class
> ByteBuffer.class
> CharArrayBuffer.class
> CharBuffer.class
> HeapByteBuffer.class
> ReadWriteCharArrayBuffer.class
> ReadWriteHeapByteBuffer.class
> FileChannel.class
> AbstractInterruptibleChannel.class
> FileChannelImpl.class
> WriteOnlyFileChannel.class
> LockManager.class
> LockManager$1.class
> ReadOnlyFileChannel.class
>
> case 2:
> ByteChannel.class
> Channel.class
> GatheringByteChannel.class
> InterruptibleChannel.class
> WritableByteChannel.class
>
> And I have got some ant script and more excluded list for emma, if
> anyone has interests, I can upload it to JIRA.

Yes!

-Mark.

> Mark Hindess wrote:
> > Anyone tried using emma ( emma.sf.net) to look at test coverage for
our
> > tests?  That might help ensure we don't trim them down too much?
> >
> > I suspect we will soon reach a point where there are significantly
fewer
> > obvious opportunities for small contributions - e.g. 1.5generification,
> > etc from looking at JAPI reports.  Having test coverage reports might
> > help by highlighting areas for improvement.
> >
> > I had a quick try with:
> >
> >   ant -f make/build.xml
> >   ant -f modules/nio/make/build.xml test
> >   java -cp emma.jar emma instr -m overwrite -cp
deploy/jdk/jre/lib/boot/nio
> .jar
> >
> > and then:
> >
> >   java -Xbootclasspath/p:emma.jar \
> >-cp build/tests:modules/nio/bin/test: junit.jar:. \
> >junit.textui.TestRunner \
> >org.apache.harmony.tests.java.nio.channels.SocketChannelTest
> >
> > (Running all the tests is a little tricky because test depends on
build,
> > which depends on clean which wipes out the instr'd jar. ;-( )
> >
> > Sadly it dies horribly with the stack trace below.  I'll take another
> > look when I have a little more time, but I thought I'd mention it in
> > case anyone else had any thoughts on the subject.
> >
> > Regards,
> >
> > Mark.
> >
> > Exception in thread "main" java/lang/ExceptionInInitializerError
> > at java/lang/J9VMInternals.initialize (J9VMInternals.java:203)
> > at java/nio/Buffer.$VRi (Buffer.java :4294967295)
> > at java/nio/Buffer. (Buffer.java :4294967295)
> > at java/lang/J9VMInternals.initializeImpl (Native Method)
> > at java/lang/J9VMInternals.initialize ( J9VMInternals.java
:185)
> > at java/lang/J9VMInternals.initialize ( J9VMInternals.java
:154)
> > at java/lang/String.getBytes (String.java:783)
> > at org/apache/harmony/luni/util/Util.getBytes ( Util.java:54)
> > at java/lang/ClassLoader.loadLibraryWithPath (
ClassLoader.java:998)
> > at java/lang/ClassLoader.loadLibraryWithClassLoader (
ClassLoader.ja
> va:970)
> > at java/lang/System.loadLibrary ( System.java:706)
> > at com/ibm/icu4jni/common/ICU4JNILoader.loadLibrary (Unknown
Source
> )
> > at com/ibm/icu4jni/converters/NativeConverter.
(Unknown Sou
> rce)
> > at java/lang/J9VMInternals.initializeImpl (Native Method)
> > at java/lang/J9VMInternals.initialize ( J9VMInternals.java
:185)
> > at com/ibm/icu4jni/charset/CharsetProviderICU.charsetForName
(Unkno
> wn Source)
> > at java/nio/charset/Charset.forNameInternal (Charset.java:450)
> > at java/nio/charset/Charset.forName ( Charset.java:513)
> > at java/lang/String.defaultCharset ( String.java:688)
> > at java/lang/String. (String.java:252)
> > at org/apache/harmony/luni/util/Util.toString ( Util.java:74)
> > at java/lang/System.getPropertyList (N

Re: [classlib] [testing] Coverage (was Re: 37% of total test execution time is spent in a single test)

[Mark Hindess]

On 2 June 2006 at 10:37, Paulex Yang <[EMAIL PROTECTED]> wrote:
>
> Mark,
> 
> I'm glad that there is someone else has interest on emma, I've tried it 
> before. AFAIK, emma works by instrumentation, but sometimes for classes 
> in bootclasspath, the instrumentation cannot work, there are two cases:
> 1. Some instrumented classes cannot be loaded by VM.
> 2. Some classes cannot be instrumented
> 
> I have tried to look more inside to find some way to work around but I 
> haven't got enough time yet.
> 
> Specifically for nio-channel module, I had a list for these two cases (I 
> believe the data is a little outdated and should be reevaluated)
> case 1.
> BaseByteBuffer.class
> Buffer.class
> BufferFactory.class
> ByteBuffer.class
> CharArrayBuffer.class
> CharBuffer.class
> HeapByteBuffer.class
> ReadWriteCharArrayBuffer.class
> ReadWriteHeapByteBuffer.class
> FileChannel.class
> AbstractInterruptibleChannel.class
> FileChannelImpl.class
> WriteOnlyFileChannel.class
> LockManager.class
> LockManager$1.class
> ReadOnlyFileChannel.class
> 
> case 2:
> ByteChannel.class
> Channel.class
> GatheringByteChannel.class
> InterruptibleChannel.class
> WritableByteChannel.class
> 
> And I have got some ant script and more excluded list for emma, if 
> anyone has interests, I can upload it to JIRA.

Yes!

-Mark.

> Mark Hindess wrote:
> > Anyone tried using emma (emma.sf.net) to look at test coverage for our
> > tests?  That might help ensure we don't trim them down too much?
> >
> > I suspect we will soon reach a point where there are significantly fewer
> > obvious opportunities for small contributions - e.g. 1.5 generification,
> > etc from looking at JAPI reports.  Having test coverage reports might
> > help by highlighting areas for improvement.
> >
> > I had a quick try with:
> >
> >   ant -f make/build.xml
> >   ant -f modules/nio/make/build.xml test
> >   java -cp emma.jar emma instr -m overwrite -cp deploy/jdk/jre/lib/boot/nio
> .jar
> >
> > and then:
> >
> >   java -Xbootclasspath/p:emma.jar \
> >-cp build/tests:modules/nio/bin/test:junit.jar:. \
> >junit.textui.TestRunner \
> >org.apache.harmony.tests.java.nio.channels.SocketChannelTest
> >
> > (Running all the tests is a little tricky because test depends on build, 
> > which depends on clean which wipes out the instr'd jar. ;-( )
> >
> > Sadly it dies horribly with the stack trace below.  I'll take another
> > look when I have a little more time, but I thought I'd mention it in
> > case anyone else had any thoughts on the subject.
> >
> > Regards,
> >  
> > Mark.
> >
> > Exception in thread "main" java/lang/ExceptionInInitializerError
> > at java/lang/J9VMInternals.initialize (J9VMInternals.java:203)
> > at java/nio/Buffer.$VRi (Buffer.java:4294967295)
> > at java/nio/Buffer. (Buffer.java:4294967295)
> > at java/lang/J9VMInternals.initializeImpl (Native Method)
> > at java/lang/J9VMInternals.initialize (J9VMInternals.java:185)
> > at java/lang/J9VMInternals.initialize (J9VMInternals.java:154)
> > at java/lang/String.getBytes (String.java:783)
> > at org/apache/harmony/luni/util/Util.getBytes (Util.java:54)
> > at java/lang/ClassLoader.loadLibraryWithPath (ClassLoader.java:998)
> > at java/lang/ClassLoader.loadLibraryWithClassLoader (ClassLoader.ja
> va:970)
> > at java/lang/System.loadLibrary (System.java:706)
> > at com/ibm/icu4jni/common/ICU4JNILoader.loadLibrary (Unknown Source
> )
> > at com/ibm/icu4jni/converters/NativeConverter. (Unknown Sou
> rce)
> > at java/lang/J9VMInternals.initializeImpl (Native Method)
> > at java/lang/J9VMInternals.initialize (J9VMInternals.java:185)
> > at com/ibm/icu4jni/charset/CharsetProviderICU.charsetForName (Unkno
> wn Source)
> > at java/nio/charset/Charset.forNameInternal (Charset.java:450)
> > at java/nio/charset/Charset.forName (Charset.java:513)
> > at java/lang/String.defaultCharset (String.java:688)
> > at java/lang/String. (String.java:252)
> > at org/apache/harmony/luni/util/Util.toString (Util.java:74)
> > at java/lang/System.getPropertyList (Native Method)
> > at java/lang/System.ensureProperties (System.java:496)
> > at java/lang/System. (System.java:55)
> > at java/lang/J9VMInternals.initializeImpl (Native Method)
> > at java/lang/J9VMInternals.initialize (J9VMInternals.java:185)
> > at java/lang/ClassLoader.initializeClassLoaders (ClassLoader.java:6
> 5)
> > at java/lang/Thread.initialize (Thread.java:301)
> > at java/lang/Thread. (Thread.java:120)
> > java/lang/NullPointerException
> > at java/lang/Throwable.printStackTrace (Throwable.java:231)
> > at com/vladium/emma/rt/RTExitHook.createClassLoaderClosure (RTExitH
> ook.java:63)
> > at com/vladium/emma/rt/RT.reset (RT.java:92)
> > at com/vladium/emma/rt/RT. (RT.java:23

Re: [classlib] [testing] Coverage (was Re: 37% of total test execution time is spent in a single test)

[Paulex Yang]

Mark,

I'm glad that there is someone else has interest on emma, I've tried it 
before. AFAIK, emma works by instrumentation, but sometimes for classes 
in bootclasspath, the instrumentation cannot work, there are two cases:

1. Some instrumented classes cannot be loaded by VM.
2. Some classes cannot be instrumented

I have tried to look more inside to find some way to work around but I 
haven't got enough time yet.


Specifically for nio-channel module, I had a list for these two cases (I 
believe the data is a little outdated and should be reevaluated)

case 1.
BaseByteBuffer.class
Buffer.class
BufferFactory.class
ByteBuffer.class
CharArrayBuffer.class
CharBuffer.class
HeapByteBuffer.class
ReadWriteCharArrayBuffer.class
ReadWriteHeapByteBuffer.class
FileChannel.class
AbstractInterruptibleChannel.class
FileChannelImpl.class
WriteOnlyFileChannel.class
LockManager.class
LockManager$1.class
ReadOnlyFileChannel.class

case 2:
ByteChannel.class
Channel.class
GatheringByteChannel.class
InterruptibleChannel.class
WritableByteChannel.class

And I have got some ant script and more excluded list for emma, if 
anyone has interests, I can upload it to JIRA.


Mark Hindess wrote:

Anyone tried using emma (emma.sf.net) to look at test coverage for our
tests?  That might help ensure we don't trim them down too much?

I suspect we will soon reach a point where there are significantly fewer
obvious opportunities for small contributions - e.g. 1.5 generification,
etc from looking at JAPI reports.  Having test coverage reports might
help by highlighting areas for improvement.

I had a quick try with:

  ant -f make/build.xml
  ant -f modules/nio/make/build.xml test
  java -cp emma.jar emma instr -m overwrite -cp deploy/jdk/jre/lib/boot/nio.jar

and then:

  java -Xbootclasspath/p:emma.jar \
   -cp build/tests:modules/nio/bin/test:junit.jar:. \
   junit.textui.TestRunner \
   org.apache.harmony.tests.java.nio.channels.SocketChannelTest

(Running all the tests is a little tricky because test depends on build, 
which depends on clean which wipes out the instr'd jar. ;-( )


Sadly it dies horribly with the stack trace below.  I'll take another
look when I have a little more time, but I thought I'd mention it in
case anyone else had any thoughts on the subject.

Regards,
 
Mark.


Exception in thread "main" java/lang/ExceptionInInitializerError
at java/lang/J9VMInternals.initialize (J9VMInternals.java:203)
at java/nio/Buffer.$VRi (Buffer.java:4294967295)
at java/nio/Buffer. (Buffer.java:4294967295)
at java/lang/J9VMInternals.initializeImpl (Native Method)
at java/lang/J9VMInternals.initialize (J9VMInternals.java:185)
at java/lang/J9VMInternals.initialize (J9VMInternals.java:154)
at java/lang/String.getBytes (String.java:783)
at org/apache/harmony/luni/util/Util.getBytes (Util.java:54)
at java/lang/ClassLoader.loadLibraryWithPath (ClassLoader.java:998)
at java/lang/ClassLoader.loadLibraryWithClassLoader 
(ClassLoader.java:970)
at java/lang/System.loadLibrary (System.java:706)
at com/ibm/icu4jni/common/ICU4JNILoader.loadLibrary (Unknown Source)
at com/ibm/icu4jni/converters/NativeConverter. (Unknown Source)
at java/lang/J9VMInternals.initializeImpl (Native Method)
at java/lang/J9VMInternals.initialize (J9VMInternals.java:185)
at com/ibm/icu4jni/charset/CharsetProviderICU.charsetForName (Unknown 
Source)
at java/nio/charset/Charset.forNameInternal (Charset.java:450)
at java/nio/charset/Charset.forName (Charset.java:513)
at java/lang/String.defaultCharset (String.java:688)
at java/lang/String. (String.java:252)
at org/apache/harmony/luni/util/Util.toString (Util.java:74)
at java/lang/System.getPropertyList (Native Method)
at java/lang/System.ensureProperties (System.java:496)
at java/lang/System. (System.java:55)
at java/lang/J9VMInternals.initializeImpl (Native Method)
at java/lang/J9VMInternals.initialize (J9VMInternals.java:185)
at java/lang/ClassLoader.initializeClassLoaders (ClassLoader.java:65)
at java/lang/Thread.initialize (Thread.java:301)
at java/lang/Thread. (Thread.java:120)
java/lang/NullPointerException
at java/lang/Throwable.printStackTrace (Throwable.java:231)
at com/vladium/emma/rt/RTExitHook.createClassLoaderClosure 
(RTExitHook.java:63)
at com/vladium/emma/rt/RT.reset (RT.java:92)
at com/vladium/emma/rt/RT. (RT.java:238)
at java/lang/J9VMInternals.initializeImpl (Native Method)
at java/lang/J9VMInternals.initialize (J9VMInternals.java:185)
at java/nio/Buffer.$VRi (Buffer.java:4294967295)
at java/nio/Buffer. (Buffer.java:4294967295)
at java/lang/J9VMInternals.initializeImpl (Native Method)
at java/lang/J9VMInternals.initialize (J9VMInternals.java:185)
at java/lang/J9VMInternals.initialize