1. 03 Aug, 2016 1 commit
  2. 02 May, 2016 3 commits
  3. 28 Apr, 2016 1 commit
  4. 12 Apr, 2016 2 commits
  5. 23 Nov, 2015 1 commit
  6. 30 Oct, 2015 1 commit
  7. 03 Aug, 2015 1 commit
  8. 13 Jul, 2015 1 commit
  9. 30 Apr, 2015 1 commit
  10. 17 Mar, 2015 1 commit
  11. 09 Feb, 2015 1 commit
  12. 04 Feb, 2015 1 commit
    • 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
  13. 15 Jan, 2015 4 commits
  14. 17 Dec, 2014 1 commit
  15. 13 Dec, 2014 1 commit
  16. 05 Dec, 2014 2 commits
  17. 04 Nov, 2014 1 commit
  18. 29 Oct, 2014 1 commit
  19. 21 Oct, 2014 1 commit
  20. 14 Oct, 2014 1 commit
  21. 25 Aug, 2014 1 commit
  22. 19 Aug, 2014 1 commit
  23. 19 Jul, 2014 1 commit
  24. 14 Jul, 2014 1 commit
  25. 26 Jun, 2014 1 commit
  26. 20 Jun, 2014 2 commits
    • Review from Cale · afe22ca4
      Piotr Mitros committed
    • XBlocks can disable navigation chrome. · 4f303a62
      There is an option to:
      * Enable/disable accordion navigation
      * Enable/disable/repoint tab navigation
      
      This allows for full-screen XBlocks (e.g. a code IDE, or large video
      player). It is also the first pass at allowing top-level XBlocks. It's
      also now possible to make a chromeless XBlock, point a tab to it, and
      make it point back to that tab.
      
      Next steps down that path would be:
      * Fix up how tabs are handled. The current version is a hack.
      * Create appropriate XBlocks for courseware, tabbed navigation,
        etc. to reach feature parity
      * Invert/rejigger the XML format.
      Piotr Mitros committed
  27. 29 May, 2014 1 commit
  28. 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
  29. 29 Apr, 2014 1 commit
  30. 05 Mar, 2014 2 commits
    • Add tests and clean up A/B testing · bce7d9e4
      Also fixes STUD-1351
      Diana Huang committed
    • split testing support in the LMS. · 281ad63d
      Adds a split_test_module XModule, that can choose one of its children
      to display, based on a get_condition_for_user API added to the runtime.
      
      To test, add something like this to an xml course, or make equivalent
       tweaks in mongo.
      
       <vertical url_name="split_test_vert">
          <split_test url_name="split1" experiment_id="0" condition_id_to_child='{"0": "i4x://MITx/6.00x/html/split_test_cond0", "1": "i4x://MITx/6.00x/html/split_test_cond1"}'>
             <html url_name="split_test_cond0">condition 0</html>
             <html url_name="split_test_cond1">condition 1</html>
          </split_test>
        </vertical>
      
      Also needs an experiment configured in the course policy json: e.g.
      
              "user_partitions": [{"id": 0,
                                            "name": "Experiment 0",
                                            "description": "Unicorns?",
                                            "version": 1,
                                            "groups": [{"id": 0,
                                                              "name": "group 0",
                                                              "version": 1},
                                                              {"id": 1,
                                                              "name": "group 1",
                                                              "version": 1}]}]
      
      (This particular snippet will work inside a course with org MITx
       and course name 6.00x)
      
      Co-Author: Sarina Canelake <sarina@edx.org>
      Co-Author: Julia Hansbrough <julia@edx.org>
      Co-Author: Diana Huang <diana@edx.org>
      Co-Author: Calen Pennington <cale@edx.org>
      
      [LMS-2095]
      Victor Shnayder committed
  31. 25 Feb, 2014 1 commit