Skip to content
  1. Oct 04, 2010
  2. Oct 01, 2010
  3. Sep 24, 2010
  4. Jan 12, 2010
  5. Jan 09, 2010
  6. Jan 04, 2010
  7. Dec 04, 2009
  8. Nov 29, 2009
  9. Sep 10, 2009
  10. Aug 24, 2009
  11. Aug 12, 2009
  12. Jul 31, 2009
  13. Jul 20, 2009
  14. Jun 04, 2009
  15. Jun 02, 2009
  16. May 27, 2009
  17. 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
  18. 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
  19. Apr 14, 2008
  20. Dec 14, 2007
  21. Dec 13, 2007
  22. Aug 19, 2007
  23. Jul 02, 2007
  24. Jun 30, 2007
  25. Apr 30, 2007
  26. Apr 18, 2007
  27. Apr 13, 2007
  28. Jan 24, 2007
  29. Dec 23, 2006
  30. Dec 18, 2006
  31. Dec 10, 2006
  32. Dec 01, 2006
  33. Nov 27, 2006
  34. Nov 24, 2006
  35. Nov 21, 2006
  36. Oct 22, 2006
  37. Oct 14, 2006