- 12 Jun, 2017 1 commit
-
-
Andy Armstrong committed
-
- 27 Apr, 2017 1 commit
-
-
Ned Batchelder 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 Aug, 2016 1 commit
-
-
Calen Pennington committed
-
- 27 Jul, 2016 1 commit
-
-
2. Add site configuration overrides to theming/helpers.py 3. Move microsite.get_value from theming/helpers to site_configuration/helpers 4. Move microsite_configuration.microsite.get_value usages to site_configuration.helpers.values
Saleem Latif committed
-
- 16 Feb, 2016 2 commits
-
-
Dmitry Viskov committed
-
Toby Lawrence committed
-
- 11 Feb, 2016 1 commit
-
-
Toby Lawrence committed
-
- 08 Feb, 2016 1 commit
-
-
Toby Lawrence committed
-
- 22 Jan, 2016 1 commit
-
-
Ibrahim committed
-
- 14 Dec, 2015 1 commit
-
-
Nimisha Asthagiri committed
-
- 25 Nov, 2015 1 commit
-
-
ECOM-2972
Peter Fogg committed
-
- 08 Oct, 2015 1 commit
-
-
openedx-newbie committed
-
- 19 Aug, 2015 1 commit
-
-
ECOM-2114
Ahsan Ulhaq committed
-
- 07 May, 2015 1 commit
-
-
Christine Lytwynec committed
-
- 17 Mar, 2015 1 commit
-
-
Ned Batchelder committed
-
- 04 Feb, 2015 2 commits
-
-
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 -
Calen Pennington committed
-
- 02 Dec, 2014 1 commit
-
-
Move modulestore config for tests to an importable location Disable pylnt warning for lms imports in common tests Refactor all testcases that loaded all xml courses TE-610 TE-489
Jesse Zoldak committed
-
- 30 Nov, 2014 1 commit
-
-
Chris Dodge committed
-
- 12 Nov, 2014 1 commit
-
-
Chris Dodge committed
-
- 10 Nov, 2014 1 commit
-
-
stv committed
-
- 09 Nov, 2014 1 commit
-
-
Add new course_module field which describes what the catalog visibility should be (both, about, none)
Chris Dodge committed
-
- 24 Sep, 2014 2 commits
-
-
chrisndodge committed
-
chrisndodge committed
-
- 23 Sep, 2014 1 commit
-
-
add tests fix use org
Chris Dodge committed
-
- 16 Sep, 2014 1 commit
-
-
only redirect to dashboard if user has course enrollments, otherwise remain on the course catalog page (aka homepage or root) update lettuce test to match new expected behavior add Jason's feedback only apply new redirect logic for microsites switch to use a feature flag to determine whether to support redirect behavior
Chris Dodge committed
-
- 10 Jul, 2014 1 commit
-
-
We need to use an Open edX footer by default (and that's what all non-edx.org instances should base their footer off) and only use the edX footer on edx.org. This commit uses `SITE_NAME` to determine which footer to use. Sites using theming or micro-sites with a `SITE_NAME` not ending in `edx.org` should not be affected.
James Tauber committed
-
- 28 Feb, 2014 1 commit
-
-
Chris Dodge committed
-
- 10 Feb, 2014 1 commit
-
-
Ned Batchelder committed
-
- 30 Jan, 2014 2 commits
-
-
Dave St.Germain committed
-
update test to reflect that the non-microsite homepage has been changed to remove all the partnership content
Chris Dodge committed
-
- 23 Jan, 2014 1 commit
-
-
Move microsite test assets to common/test Rename helper method to not have test in the name Rename test css file
Jay Zoldak committed
-
- 14 Jan, 2014 1 commit
-
-
Introduction of the Microsite feature which allows for limited multi-tenant branding on a subdomain basis, e.g. foo.edx.org and bar.edx.org fix errorenous logic when running a microsite that could reside in a hosting environment with a marketing site in front of it pep8/pylint fixes address PR feedback, remove underscore from test hostname more pep8/pylint cleanup. Skip test_microsites test, it works on localdev, not on Jenkins. Need to talk with QA team manually add Ned's single-to-double quote fix change aws.py runtimes so that the microsite_dir that is read from configuration is changed to a python path Conflicts: lms/templates/help_modal.html
Chris Dodge committed
-