Skip to content

E
edx-platform
Switch branch/tag
  1. 22 Nov, 2017 1 commit
  3. 14 Nov, 2017 1 commit
  5. 08 Nov, 2017 1 commit
  7. 05 Oct, 2017 1 commit
  9. 19 Jul, 2017 1 commit
  11. 12 Jun, 2017 1 commit
  13. 03 Aug, 2016 1 commit
  15. 02 May, 2016 1 commit
  17. 28 Apr, 2016 1 commit
  19. 30 Mar, 2016 1 commit
  21. 25 Mar, 2016 1 commit
  23. 14 Mar, 2016 1 commit
  25. 08 Mar, 2016 1 commit
  27. 24 Feb, 2016 7 commits
  29. 22 Dec, 2015 1 commit
  31. 09 Dec, 2015 1 commit
  33. 29 Oct, 2015 1 commit
  35. 17 Jun, 2015 1 commit
  37. 03 Jun, 2015 1 commit
  39. 02 Jun, 2015 2 commits
  41. 19 May, 2015 1 commit
  43. 17 Mar, 2015 1 commit
  45. 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
  47. 09 Feb, 2015 1 commit
  49. 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
    • Always call super(..).setUp() from setUp · 03a05fd9
      Calen Pennington committed
  51. 19 Jan, 2015 1 commit
  53. 14 Jan, 2015 1 commit