I agree. Without going overboard, it'd be great to set some specific milestones regarding the
quality of the code and documentation that need to be met for 3.0 final release (i.e. has to
pass the test suite with no errors, all public methods have to be documented with Javadoc,
etc.)
Automated tests on multiple platforms will go a long way towards achieving this goal.
A couple days ago, I put together a simple Java program that locates and eliminates dead
import lines from the tree [patch #475080]. I'd be happy to help create other similar source
code tests and integrate that into the test suite if there is some interest.
Comments? Ideas for new source code or documentation tests?
-- Guillaume
FROM: marc fleury
DATE: 10/30/2001 06:28:08
SUBJECT: RE: [JBoss-dev] Fwd: ests on different OS'es
Sounds great actually, having the automated tests is an important thing for
the next fase of dev. In fact even just the compile farm with Linux but
triggered when there are tag updates would be an important thing for us not
to miss obvious problems in the tests.
marcf
|-----Original Message-----
|From: <EMAIL: PROTECTED> </contact.php3?[EMAIL PROTECTED]>
|[mailto:<EMAIL: PROTECTED> </contact.php3?[EMAIL PROTECTED]>]On Behalf Of Chris
|Kimpton
|Sent: Tuesday, October 30, 2001 5:01 AM
|To: <EMAIL: PROTECTED> </contact.php3?[EMAIL PROTECTED]>
|Subject: [JBoss-dev] Fwd: ests on different OS'es
|
|
|Hi Peter
|
|[I sent this to the list - hope you don't mind - just to mix in any
|other ideas]
|
|There was some talk about the compile farm a few months back... and I
|tihnk it could be a way to go... We'd just need to see if we can
|automate all the work - eg cronjobs/at-jobs to automate and getting
|the stuff off the box, scp all the way to a public server.
|
|Although the biggest problem I see is that they have no Windoze
|servers - which I think is where we need regular testing.
|
|I think the tinderbox ( <http://mozilla.org/projects/tinderbox/> ) (or
|similar) route seems the way to go - that is, a central server for
|results and then various servers for generating/submitting results.
|It provides lots of info on when builds break and can highlight the
|code that causes the break - from what I've read.... ;-)
|
|This should allow practically anyone to use their dev pc as a test
|machine - after you run the tests, you can submit the results to the
|central server (although I maybe asking too much from tinderbox
|here...)
|
|This is what I want to look at next.
|
|Chris
|
|--- Peter Fagerlund <<EMAIL: PROTECTED> </contact.php3?[EMAIL PROTECTED]>> wrote:
|> Date: Mon, 29 Oct 2001 18:37:01 +0100
|> Subject: ests on different OS'es
|> From: Peter Fagerlund <<EMAIL: PROTECTED> </contact.php3?[EMAIL PROTECTED]>>
|> To: Chris Kimpton <<EMAIL: PROTECTED> </contact.php3?[EMAIL PROTECTED]>>
|>
|> Chris,
|>
|> have You seen "Guide to the SourceForge.net Compile Farm"
|> <http://sourceforge.net/docman/display_doc.php?docid=762&group_id=1>
|>
|> Could We use that ? ... to also test on other plattforms and have
|> an ant
|> task auto uppload the results for presentation ??? ...
|>
|> What do u think ? ...
|>
|> /peter_f
|>
|
