1. 02 May, 2016 1 commit
  2. 28 Apr, 2016 1 commit
  3. 30 Mar, 2016 1 commit
  4. 25 Mar, 2016 1 commit
  5. 14 Mar, 2016 1 commit
  6. 08 Mar, 2016 1 commit
  7. 24 Feb, 2016 7 commits
  8. 22 Dec, 2015 1 commit
  9. 09 Dec, 2015 1 commit
  10. 29 Oct, 2015 1 commit
  11. 17 Jun, 2015 1 commit
  12. 03 Jun, 2015 1 commit
  13. 02 Jun, 2015 2 commits
  14. 19 May, 2015 1 commit
  15. 17 Mar, 2015 1 commit
  16. 13 Mar, 2015 1 commit
    • Added commerce/purchase endpoint · eaa7a220
      This new endpoint is intended to replace enrollment API call used on the login+registration page. Instead of directly enrolling students, the view will contact the external e-commerce API (Oscar) to create a new order. Oscar will be responsible for completing the order and enrolling the student.
      
      This behavior will only apply to course modes with associated SKUs. All other course mode enrollments will be processed directly by LMS.
      Clinton Blackburn committed
  17. 09 Feb, 2015 1 commit
  18. 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
  19. 19 Jan, 2015 1 commit
  20. 14 Jan, 2015 1 commit