summaryrefslogtreecommitdiff
path: root/modules/system/system.test
Commit message (Collapse)AuthorAge
...
* - Patch #471070 by stella: millions of code style fixes.Dries Buytaert2009-05-24
|
* - Patch #394572 by Berdir: converted system module to the new database ↵Dries Buytaert2009-05-16
| | | | abstraction layer.
* - Patch #210876 by deekayen: log enabling and disabling of modules, and ↵Dries Buytaert2009-05-12
| | | | wrote a handy assertLogMessage() function to assert watchdog messages.
* - Patch #391340 by chx, dww, neclimdul, Crell, alex_b, et al: job queue API.Dries Buytaert2009-05-06
| | | | | | | | | | | | | | | | The queue system allows placing items in a queue and processing them later. The system tries to ensure that only one consumer can process an item. Before a queue can be used it needs to be created by DrupalQueueInterface::createQueue(). Items can be added to the queue by passing an arbitrary data object to DrupalQueueInterface::createItem(). To process an item, call DrupalQueueInterface::claimItem() and specify how long you want to have a lease for working on that item. When finished processing, the item needs to be deleted by calling DrupalQueueInterface::deleteItem(). If the consumer dies, the item will be made available again by the DrapalQueueInterface implementation once the lease expires. Another consumer will then be able to receive it when calling DrupalQueueInterface::claimItem(). The $item object used by the DrupalQueueInterface can contain arbitrary metadata depending on the implementation. Systems using the interface should only rely on the data property which will contain the information passed to DrupalQueueInterface::createItem(). The full queue item returned by DrupalQueueInterface::createItem() needs to be passed to DrupalQueueInterface::deleteItem() once processing is completed. While the queue system makes a best effort to preserve order in messages, due to the pluggable nature of the queue, there is no guarantee that items will be delivered on claim in the order they were sent. For example, some implementations like beanstalkd or others with distributed back-ends like Amazon SQS will be managing jobs for a large set of producers and consumers where a strict FIFO ordering will likely not be preserved. The system also makes no guarantees about a task only being executed once: callers that have non-idempotent tasks either need to live with the possiblity of the task being invoked multiple times in cases where a claim lease expires, or need to implement their own transactions to make their tasks idempotent.
* #376129 by boombatower, Damien Tournoud, and chx: Change getInfo() to a ↵Angie Byron2009-03-31
| | | | static method to reduce memory footprint of SimpleTest.
* #135976 by Dave Reid: Move Administration Theme setting to the themes page ↵Angie Byron2009-02-11
| | | | where it is findable (with tests).
* #363687 by chx: Simplify DBTNG codeflow.Angie Byron2009-01-25
|
* - Patch #291026 by Dave Reid et al: further (usability) improvements to the ↵Dries Buytaert2009-01-21
| | | | E_NOTICE handling.
* - Patch #320451 by chx, Damien Tournoud: improved Drupal's module dependency ↵Dries Buytaert2009-01-14
| | | | system. This helps with fields in core. Comes with tests\!
* - Patch #266246 by David Strauss: added smart defaults for ↵Dries Buytaert2009-01-11
| | | | system_settings_form().
* - Patch #353207 by CitizenKane and drewish: cleaned up the ↵Dries Buytaert2009-01-02
| | | | FILE_STATUS_TEMPORARY field.
* - Patch #352470 by scor: fixed typos and grammar in comments.Dries Buytaert2008-12-30
|
* - Patch #330633 by drewish: temporary file clean-up _and_ unit tests. Oh yeah.Dries Buytaert2008-12-28
|
* - Patch #345866 by alexanderpas, justinrandell, Dave Reid: remove from ↵Dries Buytaert2008-12-16
| | | | hook_block().
* - Patch #340557 by Dave Reid: use static caching in drupal_is_front_page().Dries Buytaert2008-12-09
|
* - Patch #318016 by Dave Reid: step one to standardizing type-hinting.Dries Buytaert2008-12-08
|
* - Patch #324313 by catch et al: load multiple nodes and terms at once.Dries Buytaert2008-12-05
|
* - Patch #314870 by drewish: removed some code that accidentically got ↵Dries Buytaert2008-11-26
| | | | committed with api.php and that broke the tests.
* #314870 by Rob Loach, drewish, catch, and sun: Add hook API documentation to ↵Angie Byron2008-11-25
| | | | Drupal core.
* - Patch #333143 by justinrandell: cleaning up the Drupal bootstrap code, ↵Dries Buytaert2008-11-24
| | | | removing bootstrap flag in system table.
* #11077 by mfb, KarenS, macgirvin, and jjkd: Can you say Daylight Savings ↵Angie Byron2008-11-20
| | | | Time? I bet you didn't think Drupal ever would! :)
* - Patch #328719 by c960657: make the module list tests succeed again.Dries Buytaert2008-11-01
|
* - Patch #327480 by chx: remove DB specific code from simpletest.Dries Buytaert2008-10-31
|
* - Patch #296321 by pwolanin, swentel: link to cron.php broken when clean ↵Dries Buytaert2008-10-13
| | | | URLs are disabled.
* Re-commit of #242873 by pwolanin and bjaspan: Make drupal_set_title() ↵Angie Byron2008-10-13
| | | | check_plain() by default.
* Roll-back of #242873: This caused horrendous problems with SimpleTest on ↵Angie Byron2008-10-12
| | | | some configurations.
* #253569 by aaron, agentrickard, and Dave Reid: Add hook_modules_X to allow ↵Angie Byron2008-10-11
| | | | modules to react when other modules are enabled, disabled, installed, or uninstalled.
* #242873 by pwolanin and bjaspan: Make drupal_set_title() do check_plain() by ↵Angie Byron2008-10-11
| | | | default.
* #296306 by swentel: Test for custom 403 page.Angie Byron2008-10-11
|
* #319699 follow-up by Dave Reid: Simplify required module hiding in ↵Angie Byron2008-10-11
| | | | admin/build/modules.
* #319699 by Dave Reid: Simplify logic for hiding required modules.Angie Byron2008-10-11
|
* #318984 by Xano and Dave Reid: Change 'Core - optional' to 'Core' in modules UI.Angie Byron2008-10-11
|
* #308534 by Dave Reid: Remove stray whitespace core-wide.Angie Byron2008-09-15
|
* - Patch #296305 by Damien Tournoud, recidive, cwgordon7, chx: 404 page needs ↵Dries Buytaert2008-08-28
| | | | a test -- testing party
* - Patch #297869 by boombatower: add xpath method to simpletest and refactor ↵Dries Buytaert2008-08-22
| | | | existing tests.
* - Patch #229129 by dmitrig01: clean up system modules page.Dries Buytaert2008-07-23
|
* - Patch #256886 by catch et al: comment out a test that fails due to a bug ↵Dries Buytaert2008-06-29
| | | | in cURL.
* - Patch #275092 by kbahey: added test for meta-tag generator patch.Dries Buytaert2008-06-28
|
* - Patch #268449 by catch: fixed some tests that failed due to invalid ↵Dries Buytaert2008-06-09
| | | | permissions.
* - Patch #250918 by boombatower: cleaned up some tests and added some tests ↵Dries Buytaert2008-06-02
| | | | for the administration panels.
* - Patch #261836 by dropcube: tests for cron.Dries Buytaert2008-05-30
|
* - Patch #259871 by pwolanin: clean up system.test.Dries Buytaert2008-05-19
|
* - Patch #256152 by catch: added additional tests for the IP address blocking ↵Dries Buytaert2008-05-10
| | | | and added a small usability improvement.
* - 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 ...