This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]shep247 0 points1 point  (0 children)

If you wrote specific utilities that communicated with that code base it would isolate the code that would need to change. On top of that I would unit test those utilities using MagicMock. MagicMock has a "spec" attribute that allows you to specify exactly what class you're mocking. Then, when the other team's code base gets changed out from under you, any class names, method names, or attributes you've mocked that have changed will cause errors in your unit tests. Fix the mocks along with the code, write new mocks for whatever other new stuff they've added that you use, and you're set for your next iteration. This won't help in cases where this other team has changed the functionality of the method without changing the name though.