[lang][codec] Test Matrix [WAS:Sanity checking a client project b uild]

[Gary Gregory <gg...@seagullsw.com>]

How about something like:

Example: 
http://cvs.apache.org/~ggregory/test-platforms/docs/test-platforms.example.x
ml

XML Schema: 
http://cvs.apache.org/~ggregory/test-platforms/test-platforms.xsd

XML Schema docs: 
http://cvs.apache.org/~ggregory/test-platforms/docs/test-platforms.html

The XML could in turn be turned in HTML by a Maven doo-dad.
?

Gary

> -----Original Message-----
> From: Phil Steitz [mailto:phil@steitz.com]
> Sent: Friday, November 21, 2003 20:34
> To: Jakarta Commons Developers List
> Subject: Re: [lang][codec] Sanity checking a client project build
> 
> John Keyes wrote:
> >
> > On 21 Nov 2003, at 18:49, __matthewHawthorne wrote:
> >
> >> I agree with the idea about testing all Java versions.  Testing all
> >> platforms is important too.  In theory, it seems like we need some
> >> type of text matrix, in which we identify all platforms and JREs that
> >> the software has been tested on.
> >>
> >> Something like:
> >>
> >>      1.2    1.3    1.4
> >> Solaris   x
> >> Linux     x      x       x
> >> Windows          x
> >> BSD       x      x
> >> Mac OSX          x       x
> >>
> >> Even if we are not able to access every version on every platform, it
> >> would be nice to see this information.  Users who have access to an
> >> untested platform could volunteer to run the tests and submit the
> >> results.
> >>
> >> Is this overkill?
> >
> >
> > Well I think we should document what we've tested it on.  As Jakarta
> > is geared towards server side software this is a great idea.
> 
> I agree. We actually went through some of this fun in the run up to lang
> 2.0.  I tested using Sun's Linux JDKs 1.2, 1.3 and 1.4 and IIRC, Stephen
>   or Henri ran tests on Windoz.  I can't remember exactly which versions
> and what we had to do to get some of the tests to run under the pre-1.4
> JDKs.  We probably should document this and include a statement in the
> release notes.
> 
> The same comments hold true for performance tests.  I have been planning
> for some time to set up some performance tests for lang, similar to what
> Craig did for BeanUtils. Any volunteers to help with this?  We could
> gather and publish the test results, along with the platform
> compatablity tests on the lang web site.  I will eventually get to this,
> but I am a bit time constrained at the moment.
> 
> Phil
> >
> > -John K
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: commons-dev-help@jakarta.apache.org
> >
> 
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org

Re: [lang][codec] Test Matrix [WAS:Sanity checking a client project build]

[Phil Steitz <ph...@steitz.com>]

Gary Gregory wrote:
> How about something like:
> 
> Example: 
> http://cvs.apache.org/~ggregory/test-platforms/docs/test-platforms.example.x
> ml
> 
> XML Schema: 
> http://cvs.apache.org/~ggregory/test-platforms/test-platforms.xsd
> 
> XML Schema docs: 
> http://cvs.apache.org/~ggregory/test-platforms/docs/test-platforms.html
> 
> The XML could in turn be turned in HTML by a Maven doo-dad.
> ?
> 
> Gary
> 

Cool!  Might want to add a placeholder for more OS info than just OS 
name and version (build number, patch level, service pack, etc.) and, if 
we use the same schema for performance tests, machine characteristics.

What would really nice would be some way to gather at least the basic 
info and generate the xml as part of the test process, so folks could 
post xml test reports and we could merge them into the site docs 
somehow. I guess step 0 is to get the schema defined for the test reports.

What are you using to generate this stuff?

Phil



---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org