From bf8a30d71b3f517d91045989824802ea7a77c995 Mon Sep 17 00:00:00 2001 From: Ben Patterson Date: Sun, 20 Dec 2015 09:19:53 -0500 Subject: [PATCH] bok-choy: Additional detail to assist when a course fixture error surfaces. When receiving an error explained in TNL-3942, I found this kind of instrumentation to be helpful. --- common/test/acceptance/fixtures/course.py | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/common/test/acceptance/fixtures/course.py b/common/test/acceptance/fixtures/course.py index 2ea327ea0b..f48fe74ea4 100644 --- a/common/test/acceptance/fixtures/course.py +++ b/common/test/acceptance/fixtures/course.py @@ -298,8 +298,8 @@ class CourseFixture(XBlockContainerFixture): self._course_key = response.json()['course_key'] else: raise FixtureError( - "Could not create course {0}. Status was {1}".format( - self._course_dict, response.status_code)) + "Could not create course {0}. Status was {1}\nResponse content was: {2}".format( + self._course_dict, response.status_code, response.content)) def _configure_course(self): """