
Due to mock.Mock's nature, using an undefined method will not result in an AttributeError, since the object will be created silently. This changed in Python 3.5, where accessing a member which doesn't exist will raise an AttributeError explicitly. This uncovered a couple of bugs in the test suite. Change-Id: Idbfa92d82b01ff4710dfdd4556500b5c61d20db6