|
[feature] Regression/Unit/System Test Hook: msg#00964php.drupal.devel
Project: Drupal Version: cvs Component: base system Category: feature requests Priority: normal Assigned to: Anonymous Reported by: javanaut Updated by: javanaut Status: active A hook would be defined by each module/theme to execute a suite of tests on itself. These tests could all be invoked on an administration page. Inter-module dependencies could be tested, new modifications could be tested...generally, anything that a module developer wants to test could be included. This would, IMO, make the community development process flow better as each developer could make sure his/her code doesn't break others' or in the presence of others'. It would allow you to instantly know when you have broken some major functionality of a given set of modules (or somebody else has broken yours). I'm not interested in engaging in the battle over extreme programming or anything like that, just a means of testing module/theme functionality without having to click all over the place to do it. I would be content with the hook merely returning success or failure, but a testing framework may be useful for more detailed testing. More information about test-driven development can be found at phpPatterns [1] or at junit.org [2]. [1] http://www.phppatterns.com/index.php/article/articleview/33/1/2/ [2] http://junit.org/index.htm javanaut -- View: http://drupal.org/node/view/6055 Edit: http://drupal.org/project/comments/add/6055 |
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | [feature] polls: separating poll-title and actual question: 00964, Steven |
|---|---|
| Next by Date: | [bug] Bad poll url from oldstyle pages: 00964, Steven |
| Previous by Thread: | [feature] polls: separating poll-title and actual questioni: 00964, Steven |
| Next by Thread: | [feature] Regression/Unit/System Test Hook: 00964, weitzman |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |