Yes, bravo!
As said Christian, using Apache tools seems the way
I have no preferences (and no knowledge BTW), looks like some investigation is
needed...
Thanks
Jacques
From: "Hans Bakker" <[email protected]>
Scott...great job! and a good step to better quality, Thanks!
On Thu, 2009-11-19 at 22:44 +1300, Scott Gray wrote:
It took a while but all our JUnit tests now pass, next I'd like to get
a continuous integration server set up. Can anybody recommend some
tools that they've had good experiences with? I'm trying out Apache
Continuum at the moment (eat our own dog food) but I'd love to hear
from anyone who has actual experience with an open source CI tool (I
do not).
Once that is done I'd like to have it run the tests after every commit
and report any failures to the dev list. It would then be the
offending committer's responsibility (well primarily at least) to fix
the problem as soon as possible, much like a build failure. If we
can't get everyone to agree to take on that responsibility then I
might as well stop now because I'll be damned if I'm going to spend
any more time fixing tests that I didn't break :-)
Any thoughts?
After that I'll starting looking at what can be done to improve the
test tools and make tests easier to write, start looking at selenium
and start writing tests for open bug reports to be committed with the
fix so that they never occur again.
All of this should help us increase the stability of the trunk and our
confidence when taking a checkout that we won't half to spend our
development time fixing things that used to work. It'll hopefully
also encourage the community to contribute more tests with the
knowledge that doing so will increase the stability of the
functionality they depend on. Fix a bug and you're good for a day,
write a test and you're good a lifetime :-)
Regards
Scott
--
Antwebsystems.com: Quality OFBiz services for competitive rates
