1. 02 Jul, 2015 3 commits
  2. 19 Jun, 2015 1 commit
  3. 17 Jun, 2015 1 commit
  4. 16 Jun, 2015 1 commit
  5. 04 Jun, 2015 1 commit
  6. 02 Jun, 2015 1 commit
  7. 28 May, 2015 1 commit
  8. 22 May, 2015 1 commit
    • SOL-794 Detailed Enrollment Report · b555c869
      - added the abstract and concrete layers of enrollment report provider
      - created a celery task.
      -added the button in the e-commerce reports section
      
      added the enrollment data backend
      
      added the payment data and start writing the test cases.
      
      updated the code with the feedback suggestions and wrote some test cases.
      - all the downloadable reports are now visible in the ecommerce download section.
      Pending instructor tasks is also visible in the ecommerce section
      
      added the fields in the user profile information
      changed the report store configuration key
      added the new http endpoint for financial reports to add more permissions for finance_admin to access.
      
      fix quality issues
      
      added test cases to check csv content data
      
      rebased with master and resolved conflicts
      
      changed the log messages
      
      added the changes as per code clintonb suggestions during code review
      
      updated the test cases for the finance_admin decorator
      
      changes suggested by clinton.
      
      Created and moved Table level filters to the Custom Manager for the CourseEnrollment model.
      
      ecommerce.js file was loaded twice in the instructor_dashboard.js fixed the issues
      
      added the registration code column in the csv
      
      added the full gender in the csv file
      
      Update data sources and add display name translations for the report columns
      
      fix meta name
      
      Make sure the reports section does not appear on non whitelabel courses
      
      pylint fixes
      
      expand out enumerated values
      Muhammad Shoaib committed
  9. 13 May, 2015 1 commit
  10. 12 May, 2015 4 commits
  11. 11 May, 2015 1 commit
  12. 05 May, 2015 1 commit
  13. 15 Apr, 2015 1 commit
  14. 08 Apr, 2015 1 commit
  15. 06 Apr, 2015 1 commit
  16. 03 Apr, 2015 1 commit
  17. 23 Mar, 2015 1 commit
  18. 19 Mar, 2015 1 commit
  19. 17 Mar, 2015 2 commits
  20. 14 Mar, 2015 1 commit
  21. 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
  22. 24 Feb, 2015 1 commit
  23. 23 Feb, 2015 3 commits
  24. 20 Feb, 2015 1 commit
  25. 18 Feb, 2015 1 commit
  26. 10 Feb, 2015 1 commit
  27. 06 Feb, 2015 1 commit
  28. 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
  29. 15 Jan, 2015 2 commits
  30. 08 Jan, 2015 1 commit