1. 08 Apr, 2015 1 commit
  2. 06 Apr, 2015 1 commit
  3. 03 Apr, 2015 1 commit
  4. 23 Mar, 2015 1 commit
  5. 19 Mar, 2015 1 commit
  6. 17 Mar, 2015 2 commits
  7. 14 Mar, 2015 1 commit
  8. 04 Mar, 2015 1 commit
    • backend changes based on feedback · e21ff203
      Conflicts:
      	lms/djangoapps/courseware/courses.py
      	lms/djangoapps/instructor_task/api.py
      
      refined entrance exam student attempts reset
      
      Quality improvements 1/16
      
      added rescore, delete state and task history functionality
      
      added unit tests for entrance exam reset attempts
      
      added unit tests for re scoring of entrance exam and task history
      
      improved test coverage
      
      Got rid of pep violation
      
      feedback changes and added jasmine test
      
      added more jasmine tests for Javascript changes
      
      added bok-choy tests for UI changes
      
      replaced input containing <p> tags with <label>
      
      Removed ee element assertions to avoid js error
      
      Added call to super.setUp()
      
      changes based on feedback on 2/18
      
      Writing tests in JS instead of coffee script
      
      commit related to skip entrance exam 2/13
      
      fixed bad-continuation quality error
      
      fixed broken bok-choy test
      
      changes based on feedback on 2/18
      
      added js tests and removed coffee script tests
      
      fixed broken bok-choy and unit tests
      
      changes left while rebasing
      
      rephrase test titles
      
      do not need these libs
      
      changes based on feedback on 2/24
      
      changes text which was left
      
      Changes based on feedback on 3/3
      Zia Fazal committed
  9. 24 Feb, 2015 1 commit
  10. 23 Feb, 2015 3 commits
  11. 20 Feb, 2015 1 commit
  12. 18 Feb, 2015 1 commit
  13. 10 Feb, 2015 1 commit
  14. 06 Feb, 2015 1 commit
  15. 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
  16. 15 Jan, 2015 2 commits
  17. 08 Jan, 2015 1 commit
  18. 05 Jan, 2015 1 commit
  19. 13 Dec, 2014 1 commit
  20. 10 Dec, 2014 1 commit
  21. 05 Dec, 2014 1 commit
  22. 02 Dec, 2014 1 commit
  23. 01 Dec, 2014 3 commits
  24. 25 Nov, 2014 1 commit
  25. 10 Nov, 2014 1 commit
  26. 31 Oct, 2014 1 commit
  27. 30 Oct, 2014 1 commit
  28. 15 Oct, 2014 1 commit
  29. 14 Oct, 2014 1 commit
  30. 09 Oct, 2014 1 commit
  31. 08 Oct, 2014 1 commit
  32. 02 Oct, 2014 1 commit
  33. 15 Sep, 2014 1 commit