From bcea53d4b7b0bc3fbf6c602bb3575d08694695c9 Mon Sep 17 00:00:00 2001 From: Chris Dodge Date: Sat, 2 Mar 2013 19:36:11 -0500 Subject: [PATCH] do the metadata comparison on the parent not the course as we don't actually know which vertical we ended up picking (could be arbitrary). --- cms/djangoapps/contentstore/tests/test_contentstore.py | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/cms/djangoapps/contentstore/tests/test_contentstore.py b/cms/djangoapps/contentstore/tests/test_contentstore.py index 66e6551019..b4d2afbef0 100644 --- a/cms/djangoapps/contentstore/tests/test_contentstore.py +++ b/cms/djangoapps/contentstore/tests/test_contentstore.py @@ -465,7 +465,9 @@ class ContentStoreTest(ModuleStoreTestCase): # check for grace period definition which should be defined at the course level self.assertIn('graceperiod', new_module.metadata) - self.assertEqual(course.metadata['graceperiod'], new_module.metadata['graceperiod']) + self.assertEqual(parent.metadata['graceperiod'], new_module.metadata['graceperiod']) + + self.assertEqual(course.metadata['xqa_key'], new_module.metadata['xqa_key']) # # now let's define an override at the leaf node level