Another call for more automated tests (was: Linotype broken)

[Bertrand Delacretaz <bd...@apache.org>]

Le Vendredi, 13 fév 2004, à 16:52 Europe/Zurich, Christopher Oliver a 
écrit :

> I noticed the Petstore and Linotype samples were both broken _after_ 
> the release. I'm not sure what caused this but it'd probably be a good 
> idea to test all the samples before releasing next time....

I think we all agree that testing is a good idea, but only a few of us 
did report on tests and problems during the last code freeze.

Technically, the solution is obvious: more automated tests will make it 
possible to ship known good releases, instead of just hoping for the 
best as we have to do now.

Unless people dedicate more energy to writing tests, however, I'm 
afraid we are bound to have more buggy releases.

A new test a day keeps the bugs away :-)

-Bertrand,
who'd like everyone here to write at least one anteater test to find 
out how easy it is 
(http://wiki.cocoondev.org/Wiki.jsp?page=TestingFramework)

Re: Another call for more automated tests (was: Linotype broken)

[Bertrand Delacretaz <bd...@apache.org>]

Le Lundi, 16 fév 2004, à 11:09 Europe/Zurich, Carsten Ziegeler a écrit :
> ...It might have been discussed before, but I still have this thought 
> anyway:
> Isn't it possible to use our nice crawling feature of Cocoon to check
> each link? So, basically we could start Cocoon as a servlet, start the
> crawler and the crawler reports every link (URI) that doesn't produce
> a valid response (throws an exception). I'm not sure, but that should
> only be a bunch of lines and would imho help a little bit.
> WDYT?

I was thinking about a similar thing which would list all test links 
and allow us to make a list of what's been tested or not  before a 
release.

But you're right, just checking that no links return an error page 
would be an improvement already.

Note that some samples (in "system pages" IIRC) do return exceptions by 
design, you might need to be able to define these special cases.

-Bertrand

RE: Another call for more automated tests (was: Linotype broken)

[Carsten Ziegeler <cz...@s-und-n.de>]

Bertrand Delacretaz wrote:
> 
> > I noticed the Petstore and Linotype samples were both 
> broken _after_ 
> > the release. I'm not sure what caused this but it'd 
> probably be a good 
> > idea to test all the samples before releasing next time....
> 
> I think we all agree that testing is a good idea, but only a 
> few of us did report on tests and problems during the last 
> code freeze.
> 
> Technically, the solution is obvious: more automated tests 
> will make it possible to ship known good releases, instead of 
> just hoping for the best as we have to do now.
> 
> Unless people dedicate more energy to writing tests, however, 
> I'm afraid we are bound to have more buggy releases.
> 
Unfortunately absolutely true.

> A new test a day keeps the bugs away :-)
> 
:)

It might have been discussed before, but I still have this thought anyway:
Isn't it possible to use our nice crawling feature of Cocoon to check
each link? So, basically we could start Cocoon as a servlet, start the
crawler and the crawler reports every link (URI) that doesn't produce
a valid response (throws an exception). I'm not sure, but that should
only be a bunch of lines and would imho help a little bit.
WDYT?

Carsten