1. 01 Mar, 2017 2 commits
  2. 24 Feb, 2017 1 commit
  3. 23 Feb, 2017 1 commit
    • Test Speedup: Isolate Modulestore Signals · 2051c909
      There are a number of Django Signals that are on the modulestore's
      SignalHandler class, such as SignalHandler.course_published. These
      signals can trigger very expensive processes to occur, such as course
      overview or block structures generation. Most of the time, the test
      author doesn't care about these side-effects.
      
      This commit does a few things:
      
      * Converts the signals on SignalHandler to be instances of a new
        SwitchedSignal class, that allows signal sending to be disabled.
      
      * Creates a SignalIsolationMixin helper similar in spirit to the
        CacheIsolationMixin, and adds it to the ModuleStoreIsolationMixin
        (and thus to ModuleStoreTestCase and SharedModuleStoreTestCase).
      
      * Converts our various tests to use this new mechanism. In some cases,
        this means adjusting query counts downwards because they no longer
        have to account for publishing listener actions.
      
      Modulestore generated signals are now muted by default during test runs.
      Calls to send() them will result in no-ops. You can choose to enable
      specific signals for a given subclass of ModuleStoreTestCase or
      SharedModuleStoreTestCase by specifying an ENABLED_SIGNALS class
      attribute, like the following example:
      
          from xmodule.modulestore.tests.django_utils import ModuleStoreTestCase
      
          class MyPublishTestCase(ModuleStoreTestCase):
              ENABLED_SIGNALS = ['course_published', 'pre_publish']
      
      You should take great care when disabling signals outside of a
      ModuleStoreTestCase or SharedModuleStoreTestCase, since they can leak
      out into other tests. Be sure to always clean up, and never disable
      signals outside of testing. Because signals are essentially process
      globals, it can have a lot of unpleasant side-effects if we start
      mucking around with them during live requests.
      
      Overall, this change has cut the total test execution time for
      edx-platform by a bit over a third, though we still spend a lot in
      pre-test setup during our test builds.
      
      [PERF-413]
      David Ormsbee committed
  4. 22 Feb, 2017 2 commits
  5. 21 Feb, 2017 1 commit
  6. 18 Feb, 2017 1 commit
  7. 08 Feb, 2017 1 commit
  8. 02 Feb, 2017 1 commit
  9. 01 Feb, 2017 1 commit
  10. 31 Jan, 2017 2 commits
  11. 25 Jan, 2017 1 commit
  12. 23 Jan, 2017 1 commit
  13. 18 Jan, 2017 2 commits
  14. 14 Jan, 2017 1 commit
    • [courseware] generate sequence-specific titles server-side (AC-695) · 54a48a32
      [courseware] generate sequence-specific titles server-side (AC-695)
      
      [courseware] generate sequence-specific titles server-side (AC-695)
      
      case for empty subsections [AC-695]
      
      move title logic into courseware context method [AC-695]
      
      pep8
      
      coffeescript -> js
      
      js mistake
      
      jslint
      
      refactor sequence title generation slightly
      
      missed a line
      
      line too long
      
      python is not javascript
      
      ugh js
      
      ugh js part 2
      Ari Rizzitano committed
  15. 13 Jan, 2017 1 commit
  16. 12 Jan, 2017 3 commits
  17. 10 Jan, 2017 2 commits
  18. 07 Jan, 2017 1 commit
  19. 06 Jan, 2017 1 commit
  20. 05 Jan, 2017 7 commits
  21. 04 Jan, 2017 4 commits
  22. 03 Jan, 2017 1 commit
  23. 29 Dec, 2016 1 commit
  24. 22 Dec, 2016 1 commit