It sounds like a good idea on the surface. Combining all the
testsuites into one, at the very least, is a worthy goal, since we're all
testing the same thing.
But as you say, *nobody* likes to write tests. Pushing them off into
their own project seems like a convenient way to forget about them. At
least as it stands now the authors have more reason to grudgingly accept
responsibility for it. We could fall into what my work likes to call "unit
testing." What this means, I have learned, is "I ran it and it didn't crash
the system, so it's ready for production."
Dunno, seems worth a try at least; the combination of existing
testsuites is a worthy goal. Go for it.
--John Keiser
- Project Mauve: A Free Java Regression Test and Compatibili... Aaron M. Renn
- Re: Project Mauve: A Free Java Regression Test and Co... Chris Toshok
- Re: Project Mauve: A Free Java Regression Test and Co... John Keiser
- Re: Project Mauve: A Free Java Regression Test and Co... Godmar Back
- Re: Project Mauve: A Free Java Regression Test an... Tom Tromey
- Re: Project Mauve: A Free Java Regression Tes... Godmar Back
- RE: Project Mauve: A Free Java Regression... John Keiser
- Re: Project Mauve: A Free Java Regression... Tom Tromey
- Re: Project Mauve: A Free Java Regression Tes... Bernd Kreimeier
- Re: Project Mauve: A Free Java Regression... Brian Jones
- Re: Project Mauve: A Free Java Regre... Stuart Ballard
- Re: Project Mauve: A Free Java Regression Test and Co... Aaron M. Renn
