1. 03 Aug, 2016 1 commit
  2. 27 Jul, 2016 1 commit
  3. 08 Apr, 2016 1 commit
  4. 03 Feb, 2016 1 commit
  5. 10 Nov, 2015 1 commit
  6. 21 Oct, 2015 1 commit
  7. 21 Aug, 2015 1 commit
  8. 27 Apr, 2015 1 commit
  9. 17 Mar, 2015 1 commit
  10. 14 Mar, 2015 1 commit
  11. 27 Feb, 2015 1 commit
  12. 20 Feb, 2015 1 commit
  13. 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
  14. 01 Dec, 2014 2 commits
  15. 30 Oct, 2014 1 commit