1. 07 Aug, 2017 1 commit
  2. 25 Jul, 2017 1 commit
  3. 30 May, 2017 2 commits
  4. 25 May, 2017 2 commits
  5. 19 Apr, 2017 1 commit
  6. 13 Apr, 2017 1 commit
  7. 05 Apr, 2017 1 commit
  8. 30 Mar, 2017 1 commit
  9. 08 Mar, 2017 1 commit
  10. 01 Mar, 2017 1 commit
  11. 10 Nov, 2016 1 commit
  12. 29 Jul, 2016 1 commit
  13. 08 Apr, 2016 1 commit
  14. 23 Mar, 2016 1 commit
  15. 16 Feb, 2016 1 commit
  16. 04 Dec, 2015 1 commit
  17. 20 Aug, 2015 1 commit
    • In-course reverification access control · ec28a75f
      * Automatically create user partitions on course publish for each ICRV checkpoint.
      * Disable partitions for ICRV checkpoints that have been deleted.
      * Skip partitions that have been disabled when checking access.
      * Add verification access control UI to visibility settings.
      * Add verification access control UI to sequential and vertical settings.
      * Add partition scheme for verification partition groups.
      * Cache information used by verification partition scheme and invalidate the cache on update.
      * Add location parameter to UserPartition so the partition scheme can find the associated checkpoint.
      * Refactor GroupConfiguration to allow multiple user partitions.
      * Add special messaging to ICRV for students in the honor track.
      
      Authors: Zubair Arbi, Awais Qureshi, Aamir Khan, Will Daly
      zubair-arbi committed
  18. 06 Jul, 2015 1 commit
  19. 29 Jun, 2015 1 commit
  20. 02 Jun, 2015 1 commit
  21. 17 Mar, 2015 1 commit
  22. 09 Feb, 2015 3 commits
  23. 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
  24. 15 Jan, 2015 1 commit
  25. 10 Nov, 2014 1 commit
  26. 29 Sep, 2014 1 commit
  27. 16 Aug, 2014 1 commit
  28. 08 Aug, 2014 2 commits
  29. 07 Aug, 2014 2 commits
  30. 14 Jul, 2014 1 commit
  31. 10 Jul, 2014 1 commit
  32. 27 Jun, 2014 1 commit
  33. 29 May, 2014 1 commit