1. 30 May, 2017 1 commit
  2. 25 May, 2017 1 commit
  3. 17 May, 2017 1 commit
  4. 09 May, 2017 1 commit
  5. 05 May, 2017 2 commits
  6. 04 May, 2017 2 commits
  7. 28 Apr, 2017 2 commits
  8. 14 Apr, 2017 1 commit
  9. 31 Mar, 2017 1 commit
  10. 06 Mar, 2017 1 commit
  11. 23 Feb, 2017 2 commits
    • Student Dashboard CourseOverviews with one query. · 8423ecb1
      Pre-load the course overviews attached to CourseEnrollments on the
      Student Dashboard, if possible. This will only grab the CourseOverviews
      that already exist, and will not generate new ones. Any missing
      CourseOverviews fall back to the lazily-created one-at-a-time behavior
      they've always had. That's mostly because I wanted to optimize for the
      common case in the least invasive way possible, and I don't want to get
      caught up in locking issues.
      David Ormsbee committed
    • 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
  12. 14 Feb, 2017 1 commit
  13. 03 Feb, 2017 1 commit
  14. 01 Feb, 2017 1 commit
  15. 03 Jan, 2017 1 commit
  16. 22 Dec, 2016 1 commit
  17. 20 Dec, 2016 1 commit
  18. 07 Nov, 2016 1 commit
  19. 04 Nov, 2016 1 commit
  20. 03 Nov, 2016 1 commit
  21. 06 Oct, 2016 1 commit
  22. 03 Aug, 2016 1 commit
  23. 05 Jul, 2016 1 commit
  24. 24 Jun, 2016 1 commit
  25. 02 May, 2016 1 commit
  26. 28 Apr, 2016 1 commit
  27. 08 Apr, 2016 1 commit
  28. 30 Mar, 2016 1 commit
  29. 22 Mar, 2016 1 commit
  30. 17 Mar, 2016 1 commit
  31. 04 Mar, 2016 1 commit
    • Migrate correctly from scratch also · 631bfc08
      Unfortunately, instrospection.get_table_description runs
      select * from course_overview_courseoverview, which of course
      does not exist while django is calculating initial migrations, causing
      this to fail.  Additionally, sqlite does not support information_schema,
      but does not do a select * from the table.
      
      Lift the main part of mysql's get_table_description up to the migration itself
      and just inspect it directly.  Continue to call the API for sqlite.
      Kevin Falcone committed
  32. 26 Feb, 2016 2 commits
  33. 18 Feb, 2016 1 commit
  34. 11 Feb, 2016 1 commit
  35. 09 Feb, 2016 1 commit