1. 02 Jul, 2015 1 commit
  2. 23 Jun, 2015 1 commit
  3. 19 Jun, 2015 1 commit
  4. 08 Jun, 2015 1 commit
  5. 02 Jun, 2015 1 commit
  6. 07 May, 2015 1 commit
  7. 17 Mar, 2015 1 commit
  8. 14 Mar, 2015 3 commits
  9. 06 Mar, 2015 1 commit
  10. 04 Feb, 2015 2 commits
    • Better support specifying of modulestore configuration in test cases · b353ed2e
      The existing pattern of using `override_settings(MODULESTORE=...)` prevented
      us from having more than one layer of subclassing in modulestore tests.
      
      In a structure like:
      
          @override_settings(MODULESTORE=store_a)
          class BaseTestCase(ModuleStoreTestCase):
              def setUp(self):
                  # use store
      
          @override_settings(MODULESTORE=store_b)
          class ChildTestCase(BaseTestCase):
              def setUp(self):
                  # use store
      
      In this case, the store actions performed in `BaseTestCase` on behalf of
      `ChildTestCase` would still use `store_a`, even though the `ChildTestCase`
      had specified to use `store_b`. This is because the `override_settings`
      decorator would be the innermost wrapper around the `BaseTestCase.setUp` method,
      no matter what `ChildTestCase` does.
      
      To remedy this, we move the call to `override_settings` into the
      `ModuleStoreTestCase.setUp` method, and use a cleanup to remove the override.
      Subclasses can just defined the `MODULESTORE` class attribute to specify which
      modulestore to use _for the entire `setUp` chain_.
      
      [PLAT-419]
      Calen Pennington committed
  11. 02 Dec, 2014 1 commit
  12. 01 Dec, 2014 4 commits
  13. 31 Oct, 2014 1 commit
  14. 21 Jul, 2014 1 commit
  15. 29 May, 2014 1 commit
  16. 24 May, 2014 2 commits
  17. 08 May, 2014 1 commit
    • Make course ids and usage ids opaque to LMS and Studio [partial commit] · cd746bf8
      This commit adds the non-courseware lms/djangoapps and lms/lib.
      
      These keys are now objects with a limited interface, and the particular
      internal representation is managed by the data storage layer (the
      modulestore).
      
      For the LMS, there should be no outward-facing changes to the system.
      The keys are, for now, a change to internal representation only. For
      Studio, the new serialized form of the keys is used in urls, to allow
      for further migration in the future.
      
      Co-Author: Andy Armstrong <andya@edx.org>
      Co-Author: Christina Roberts <christina@edx.org>
      Co-Author: David Baumgold <db@edx.org>
      Co-Author: Diana Huang <dkh@edx.org>
      Co-Author: Don Mitchell <dmitchell@edx.org>
      Co-Author: Julia Hansbrough <julia@edx.org>
      Co-Author: Nimisha Asthagiri <nasthagiri@edx.org>
      Co-Author: Sarina Canelake <sarina@edx.org>
      
      [LMS-2370]
      Calen Pennington committed
  18. 28 Apr, 2014 1 commit
  19. 08 Apr, 2014 1 commit
  20. 26 Mar, 2014 1 commit
  21. 11 Mar, 2014 1 commit
  22. 10 Mar, 2014 2 commits
  23. 07 Mar, 2014 1 commit
  24. 28 Feb, 2014 1 commit
  25. 10 Feb, 2014 2 commits
  26. 24 Jan, 2014 1 commit
  27. 14 Jan, 2014 1 commit
  28. 10 Dec, 2013 1 commit
  29. 04 Dec, 2013 1 commit
  30. 25 Nov, 2013 1 commit
    • Make remaining dialogs in wiki accessible. · cccd61eb
      All the dialogs in the wiki are now accessible to screen readers.
      
      Also, the "Switch to selected version" button did the odd thing of
      reloading the page with the new version selected, but inside a dialog.
      That is now fixed.
      
      The merge dialog has a warning that looks kind of funky still, but you
      can read it, unlike the previous code.
      
      LMS-1337
      Ned Batchelder committed
  31. 13 Nov, 2013 1 commit