- 07 Aug, 2017 1 commit
-
-
cahrens committed
-
- 12 Jun, 2017 1 commit
-
-
Andy Armstrong committed
-
- 03 Aug, 2016 1 commit
-
-
Calen Pennington committed
-
- 02 May, 2016 3 commits
-
-
TEST_DATA_MIXED_MODULESTORE Remove these test mixed modulestores: TEST_DATA_MIXED_TOY_MODULESTORE TEST_DATA_MIXED_CLOSED_MODULESTORE TEST_DATA_MIXED_GRADED_MODULESTORE
John Eskew committed -
John Eskew committed
-
John Eskew committed
-
- 12 Apr, 2016 3 commits
-
-
TEST_DATA_MIXED_MODULESTORE Remove these test mixed modulestores: TEST_DATA_MIXED_TOY_MODULESTORE TEST_DATA_MIXED_CLOSED_MODULESTORE TEST_DATA_MIXED_GRADED_MODULESTORE
John Eskew committed -
John Eskew committed
-
John Eskew committed
-
- 17 Feb, 2016 1 commit
-
-
Qubad786 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
-
- 13 Dec, 2014 1 commit
-
-
Move lms.lib.xblock into lms.djangoapps.lms_xblock in preparation add database backed configuration to it
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
-
- 08 Aug, 2014 1 commit
-
-
Nimisha Asthagiri committed
-
- 10 Jul, 2014 1 commit
-
-
Nimisha Asthagiri committed
-
- 26 Jun, 2014 1 commit
-
-
Refactor get_parent_locations STUD-1663
Nimisha Asthagiri committed
-
- 29 May, 2014 1 commit
-
-
[LMS-2757]
Calen Pennington committed
-
- 24 May, 2014 2 commits
-
-
Julia Hansbrough committed
-
Julia Hansbrough committed
-
- 06 May, 2014 1 commit
-
-
This commit updates lms/djangoapps/courseware. These keys are now objects with a limited interface, and the particular internal representation is managed by the data storage layer (the modulestore). For the LMS, there should be no outward-facing changes to the system. The keys are, for now, a change to internal representation only. For Studio, the new serialized form of the keys is used in urls, to allow for further migration in the future. Co-Author: Andy Armstrong <andya@edx.org> Co-Author: Christina Roberts <christina@edx.org> Co-Author: David Baumgold <db@edx.org> Co-Author: Diana Huang <dkh@edx.org> Co-Author: Don Mitchell <dmitchell@edx.org> Co-Author: Julia Hansbrough <julia@edx.org> Co-Author: Nimisha Asthagiri <nasthagiri@edx.org> Co-Author: Sarina Canelake <sarina@edx.org> [LMS-2370]
Calen Pennington committed
-
- 08 Nov, 2013 1 commit
-
-
Calen Pennington committed
-
- 25 Oct, 2013 1 commit
-
-
Previously, whenever a XModule was created from a XDescriptor, we created another level of nesting of FieldData objects. This change prevents that nesting. [TKTS-393]
Calen Pennington committed
-
- 06 Sep, 2013 1 commit
-
-
Calen Pennington committed
-
- 22 Aug, 2013 3 commits
- 21 Aug, 2013 2 commits
-
-
Fixed test_masquerade failure due to not clearing the modulestore between tests.
Will Daly committed -
Modified navigation tests to use MixedModulestore Updated factories to find editable modulestore Updated test_submitting_problems Updated test_tabs.py Updated test_view_authentication Updated test_views Updated courseware/tests/tests.py Updated test_masquerade Updated test_module_render Pylint fixes Updated video and word cloud tests Updated course wiki tests Updated license and open_ended tests. One open_ended test still failing due to Mako initialization issues Updated staticbook Updated django_comment_client tests Updated instructor tests Updated instructor task tests Updated external_auth tests Updated course_groups
Will Daly committed
-
- 20 Aug, 2013 1 commit
-
-
Chris Dodge committed
-
- 31 Jul, 2013 1 commit
-
-
Calen Pennington committed
-
- 16 Jul, 2013 2 commits
-
-
Instead, we use XModule field default values when creating an empty XModule. Driven by this use case, we also allow for XModules to be created in memory without being persisted to the database at all. This necessitates a change to the Modulestore api, replacing clone_item with create_draft and save_xmodule.
Don Mitchell committed -
DraftModuleStore was originally designed as a mixin, but never used that way, and with the upcoming changes to use the versioned module store, never will be. This changes removes a circular dependency between mongo.py and draft.py.
Don Mitchell committed
-
- 11 Jul, 2013 1 commit
-
-
JonahStanley committed
-
- 01 Jul, 2013 1 commit
-
-
Moved xml_store_config, mongo_store_config, and draft_mongo_store_config to xmodule/modulestore/tests/django_util.py Removed some repeated instances of xml_store_config. Reverted some changes to mongo_store_config so each modulestore gets it's own uuid.
Jean Manuel Nater committed
-
- 26 Jun, 2013 1 commit
-
-
Don Mitchell committed
-
- 21 Jun, 2013 1 commit
-
-
Jean Manuel Nater committed
-
- 18 Jun, 2013 1 commit
-
-
Jean Manuel Nater committed
-