Commit message (Collapse) | Author | Age | |
---|---|---|---|
* | - Patch #352872 by Damien Tournoud: clean-up xmlrpc() wrapper. | Dries Buytaert | 2009-05-04 |
| | |||
* | #376129 by boombatower, Damien Tournoud, and chx: Change getInfo() to a ↵ | Angie Byron | 2009-03-31 |
| | | | | static method to reduce memory footprint of SimpleTest. | ||
* | - Patch #380064 by c960657: make file_scan_directory() use save property ↵ | Dries Buytaert | 2009-02-22 |
| | | | | names as file_load(). | ||
* | - Patch #352470 by scor: fixed typos and grammar in comments. | Dries Buytaert | 2008-12-30 |
| | |||
* | - Patch #338403 by drewish: code comments clean-up. | Dries Buytaert | 2008-11-25 |
| | |||
* | - Patch #296442 by Damien Tournoud: made upload and blog API tests pass ↵ | Dries Buytaert | 2008-10-13 |
| | | | | without clean URLs enabled. | ||
* | - Patch #305740 by catch, Benjamin Melançon: added an edit tab to taxonomy ↵ | Dries Buytaert | 2008-09-19 |
| | | | | term pages. | ||
* | - Patch #247423 by boombatower: code style fixes for the tests. | Dries Buytaert | 2008-05-30 |
| | |||
* | - Patch #257713 by Senpai: code cleanup. | Dries Buytaert | 2008-05-13 |
| | |||
* | - Patch #251263 by catch: fixing up many code style issues in the tests. | Dries Buytaert | 2008-04-25 |
| | |||
* | - Added a test framework to Drupal along with a first batch of tests for | Dries Buytaert | 2008-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 ... |