> Use Mock and assert_called_with: > http://www.voidspace.org.uk/python/mock/mock.html#mock.Mock.assert_ca... > In this case you'd set theAPI.call as your mock and check that under > different conditions it is called correctly.
Oh, perfect -- thank you, that will help a lot! > You don't need mocks or dependency injection in this case. Just separate the > message construction code, so you can test it in isolation: Yeah, it looks like that may be a next step, but I'm hesitant to do even that much refactoring without tests already in place, due to the complexity and fragility of the logic. -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
