On May 21, 2005, at 4:05 AM, Adrian Rossouw wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I know there has been some discussion regarding this in the past, but I was wondering what it would actually
take to get Drupal into a state where we take advantage of unit testing.

As I have stated before, the most of my time spent maintaining the postgres port is spent testing every little thing
in the system, and anything to automate that would help me, and by extension Drupal, immensely.

Any thoughts ?

The main resource for finding OSS testing tools is: http://opensourcetesting.com

Here are link checkers: http://www.opensourcetesting.org/link_checkers.php
http://linkchecker.sourceforge.net/
http://j-spider.sourceforge.net/
http://htcheck.sourceforge.net/

Functional testing:
jWebUnit http://jwebunit.sourceforge.net/
WebInject http://www.webinject.org/

You should know I am currently running a testing program for the contribution modules we add to CivicSpace.  My testing plan is here: http://civicspacelabs.org/home/node/12441.  I'd be happy to extend this testing phase to Drupal core if I could get some help managing it.

Cheers,
Kieran

- --
Adrian Rossouw
Drupal developer and Bryght Guy
http://drupal.org | http://bryght.com


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)

iD8DBQFCjxYCgegMqdGlkasRAtLLAJ4wy1XmaTGSLIx/82a7A5yB1s77gACfWGn/
WnsHfDt10emthkkRviRcy/o=
=BwUV
-----END PGP SIGNATURE-----