Skip to content
  1. Dec 18, 2010
  2. Oct 22, 2010
  3. Oct 15, 2010
  4. Oct 05, 2010
  5. Oct 03, 2010
  6. Sep 13, 2010
  7. Sep 11, 2010
  8. Sep 05, 2010
  9. Jul 30, 2010
  10. Jun 28, 2010
  11. Jun 14, 2010
  12. Feb 03, 2010
  13. Nov 17, 2009
  14. Nov 07, 2009
  15. Oct 18, 2009
  16. Sep 21, 2009
  17. Sep 11, 2009
  18. Aug 31, 2009
  19. Aug 17, 2009
  20. Jul 01, 2009
  21. Jun 08, 2009
  22. May 01, 2009
  23. Oct 11, 2008
  24. Oct 09, 2008
  25. May 06, 2008
    • Dries Buytaert's avatar
      - Patch #221964 by chx, dopry, webernet, moshe, webchick, justinrandall, flobruit · 2e18cb89
      Dries Buytaert authored
        et al.  Can you say 'registry'?  Drupal now maintains an internal registry of
        all functions or classes in the system, allowing it to lazy-load code files as
        needed (reducing the amount of code that must be parsed on each request). The
        list of included files is cached per menu callback for subsequent loading by
        the menu router. This way, a given page request will have all the code it needs
        but little else, minimizing time spent parsing unneeded code.
      2e18cb89
  26. Apr 20, 2008
    • Dries Buytaert's avatar
      - Added a test framework to Drupal along with a first batch of tests for · af474609
      Dries Buytaert authored
        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 ...
      af474609