From karoly@negyesi.net Thu Apr 24 06:05:14 2008
From: Karoly Negyesi <karoly@negyesi.net>
To: development@drupal.org
Subject: [development] Very important testing update
Date: Thu, 24 Apr 2008 08:05:10 +0200
Message-ID: <7e270cea0804232305v50dad74cm3d2b2e0623f912c5@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============8098515406995945168=="

--===============8098515406995945168==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit

Hi,

Yesterday we had quite a discussion on IRC which is summed up
http://groups.drupal.org/node/10957 . Basically, mock functions were
voted down as tests based on them takes too much developer resources
to write and maintain. Instead, we are writing functional testing on
an API level as described on http://drupal.org/node/30008 , for
example:

$this->assertEqual(l('Some page', 'node/34', array('class' =>
'foobar')), '<a href="/node/34" class="foobar">some page</a>');

This test presumes and verifies somewhat that every function l calls
is working correctly. Whether this still can be called unit testing or
not is a pointless academic debate :)

I expect that a number of tasks will be placed in the Drupal issue
queue telling the community which tests are to be written. When this
happens, I guess another email will land here and also I guess at
various other places... I also plan to hold a 'testing hour' every
single day starting probably next week.

Stay tuned!

Karoly Negyesi

--===============8098515406995945168==--