- 12 Jun, 2017 1 commit
-
-
Andy Armstrong committed
-
- 13 Apr, 2017 1 commit
-
-
Diana Huang committed
-
- 30 Mar, 2017 1 commit
-
-
TNL-6674
cahrens committed
-
- 28 Mar, 2017 1 commit
-
-
Nimisha Asthagiri committed
-
- 20 Mar, 2017 1 commit
-
-
TNL-6645
Nimisha Asthagiri committed
-
- 02 Mar, 2017 1 commit
-
-
TNL-6518
Nimisha Asthagiri committed
-
- 01 Mar, 2017 1 commit
-
-
Nimisha Asthagiri committed
-
- 23 Feb, 2017 1 commit
-
-
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
-
- 03 Jan, 2017 1 commit
-
-
christopher lee committed
-
- 29 Dec, 2016 1 commit
-
-
Nimisha Asthagiri committed
-
- 04 Aug, 2016 1 commit
-
-
Sanford Student committed
-
- 27 Jul, 2016 1 commit
-
-
Nimisha Asthagiri committed
-
- 25 Jul, 2016 1 commit
-
-
wajeeha-khalid committed
-
- 24 Jun, 2016 2 commits
-
-
Nimisha Asthagiri committed
-
Nimisha Asthagiri committed
-
- 16 Jun, 2016 1 commit
-
-
This commit "undoes"a previous hotfix, and allows a cms course_publish signal to trigger a block_structure update_course_in_cache task, which is run on an lms worker queue. Changes: -exposes ALTERNATE_QUEUE_ENVS -adds routing layer in celery.py -moves prior dev_with_worker settings file to devstack_with_worker -moves course_block api functionality into openedx/core/djangoapps/content/block_structure
Eric Fischer committed
-
- 09 May, 2016 1 commit
-
-
wajeeha-khalid committed
-
- 15 Mar, 2016 1 commit
-
-
George Schneeloch committed
-
- 10 Mar, 2016 2 commits
- 09 Mar, 2016 2 commits
- 29 Feb, 2016 2 commits
- 18 Feb, 2016 1 commit
-
-
Nimisha Asthagiri committed
-
- 03 Feb, 2016 2 commits
-
-
MA-1368
Nimisha Asthagiri committed -
Nimisha Asthagiri committed
-
- 26 Jan, 2016 1 commit
-
-
Nimisha Asthagiri committed
-
- 05 Jan, 2016 1 commit
-
-
Nimisha Asthagiri committed
-
- 05 Nov, 2015 1 commit
-
-
Nimisha Asthagiri committed
-