Commit message (Collapse) | Author | Age | |
---|---|---|---|
* | - Patch #440920 by brianV: whitespace and coding style clean-up. | Dries Buytaert | 2009-04-22 |
| | |||
* | - Patch #308296 by Dave Reid, Damien Tournoud: clean-up of drupalCreateNode(). | Dries Buytaert | 2009-04-22 |
| | |||
* | #368064 by catch: Provide a top-level 'International' menu item for ↵ | Angie Byron | 2009-03-31 |
| | | | | localization and translation-related items. | ||
* | #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 #348742 by catch: path tests should use drupalCreateNode() instead ↵ | Dries Buytaert | 2009-01-09 |
| | | | | of own createNode(). Code clean-up. | ||
* | - Patch #324313 by catch et al: load multiple nodes and terms at once. | Dries Buytaert | 2008-12-05 |
| | |||
* | - Patch #204106 by catch, Damien Tournoud: added test for translation of ↵ | Dries Buytaert | 2008-10-13 |
| | | | | path aliases. | ||
* | - Patch #225450 by Crell, chx, bjaspan, catch, swentel, recidive et al: next ↵ | Dries Buytaert | 2008-08-21 |
| | | | | generation database layer for Drupal 7. | ||
* | - 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 ... |