summaryrefslogtreecommitdiff
path: root/modules/simpletest
Commit message (Collapse)AuthorAge
* - Patch #252365 by boombatower: clean up the temporary directory that gets ↵Dries Buytaert2008-04-30
| | | | creating during the test runs.
* - Patch #251550 by ksenzee: simpletest requires curl so make sure to add a ↵Dries Buytaert2008-04-28
| | | | requirements check.
* - Patch #251631 by chx: fixed behavior of the Drupal web test case with ↵Dries Buytaert2008-04-28
| | | | regard to POST and GET operations.
* - Patch #249546 by pwolanin: rip menu access inheritance -- was already ↵Dries Buytaert2008-04-23
| | | | committed to D6.
* - Patch #250056 by dmitrig01: if all the checkboxes in a checkbox group are ↵Dries Buytaert2008-04-23
| | | | checked on page load, the check all box isn't checked, which is should be (because all sub-boxes are checked).
* - Patch #249629 by chx, flobruit: made drupal_test_case() reusable and ↵Dries Buytaert2008-04-23
| | | | improve the SimpleTest documentation.
* - Added a test framework to Drupal along with a first batch of tests forDries Buytaert2008-04-20
| | | | | | | | | | | | | | | | | | | | | | | | | | Drupal core! This is an important milestone for the project so enable the module and check it out ... :) Thanks to Rok Žlender, Károly Négyesi, Jimmy Berry, Kevin Bridges, Charlie Gordon, Douglas Hubler, Miglius Alaburda, Andy Kirkham, Dimitri13, Kieran Lal, Moshe Weitzman, and the many other people that helped with testing over the past years and that drove this home. It all works but it is still rough around the edges (i.e. documentation is still being written, the coding style is not 100% yet, a number of tests still fail) but we spent the entire weekend working on it in Paris and made a ton of progress. The best way to help and to get up to speed, is to start writing and contributing some tests ... as well as fixing some of the failures. For those willing to help with improving the test framework, here are some next steps and issues to resolve: - How to best approach unit tests and mock functions? - How to test drupal_mail() and drupal_http_request()? - How to improve the admin UI so we have a nice progress bar? - How best to do code coverage? - See http://g.d.o/node/10099 for more ...
* - Added a test framework to Drupal along with a first batch of tests forDries Buytaert2008-04-20
Drupal core! This is an important milestone for the project so enable the module and check it out ... :) Thanks to Rok Žlender, Károly Négyesi, Jimmy Berry, Kevin Bridges, Charlie Gordon, Douglas Hubler, Miglius Alaburda, Andy Kirkham, Dimitri13, Kieran Lal, Moshe Weitzman, and the many other people that helped with testing over the past years and that drove this home. It all works but it is still rough around the edges (i.e. documentation is still being written, the coding style is not 100% yet, a number of tests still fail) but we spent the entire weekend working on it in Paris and made a ton of progress. The best way to help and to get up to speed, is to start writing and contributing some tests ... as well as fixing some of the failures. For those willing to help with improving the test framework, here are some next steps and issues to resolve: - How to best approach unit tests and mock functions? - How to test drupal_mail() and drupal_http_request()? - How to improve the admin UI so we have a nice progress bar? - How best to do code coverage? - See http://g.d.o/node/10099 for more ...