Do you mean switch the db config in test.py to use mysql?  My local dev uses mysql for dev.py anyway. 

On Aug 21, 2013, at 2:32 PM, David Ormsbee <notifications@github.com> wrote:

> In lms/djangoapps/shoppingcart/tests.py:
> 
> > +        reg1 = PaidCourseRegistration.objects.get(id=reg1.id)  # reload from DB to get side-effect
> > +        self.assertEqual(reg1.status, "purchased")
> > +
> > +    def test_purchased_callback_exception(self):
> > +        reg1 = PaidCourseRegistration.add_to_order(self.cart, self.course_id)
> > +        reg1.course_id = "changedforsomereason"
> > +        reg1.save()
> > +        with self.assertRaises(PurchasedCallbackException):
> > +            reg1.purchased_callback()
> > +        self.assertFalse(CourseEnrollment.is_enrolled(self.user, self.course_id))
> > +
> > +        reg1.course_id = "abc/efg/hij"
> > +        reg1.save()
> > +        with self.assertRaises(PurchasedCallbackException):
> > +            reg1.purchased_callback()
> > +        self.assertFalse(CourseEnrollment.is_enrolled(self.user, self.course_id))
> Also, given that we're in the land of transactions, is it relatively easy for you to test this on mysql?
> 
> —
> Reply to this email directly or view it on GitHub.
>