From a64dad56d764cf346988474fdad34937ad637da0 Mon Sep 17 00:00:00 2001 From: Feanil Patel Date: Mon, 23 Sep 2024 13:28:39 -0400 Subject: [PATCH] fixup! test: Update the course in the cache after it's got new content. --- .../grades/rest_api/v1/tests/test_gradebook_views.py | 3 --- 1 file changed, 3 deletions(-) diff --git a/lms/djangoapps/grades/rest_api/v1/tests/test_gradebook_views.py b/lms/djangoapps/grades/rest_api/v1/tests/test_gradebook_views.py index ab11daf36576..42dd9139ee21 100644 --- a/lms/djangoapps/grades/rest_api/v1/tests/test_gradebook_views.py +++ b/lms/djangoapps/grades/rest_api/v1/tests/test_gradebook_views.py @@ -2230,9 +2230,6 @@ def test_get_override_for_unreleased_block(self): ) # We need to update the course in the cache after we create the new block. - # Review Question: Should we be doing this here? Does it make sense to do - # this in the xmodule/modulestore/tests/factories.py BlockFactory class - # as a part of the publish there? bs_api.update_course_in_cache(self.course_data.course_key) resp = self.client.get(