I recently saw a case [1] where a misspelled assertion method
(asoptt_called_once_with vs assert_called_once_with) did not result in a test
failure because the object it was called on was created by mock.patch() without
any of the spec/spec_set/autospec parameters being set. Might it make
+1 but fixing this looks like take not small time
2014/1/10 Maru Newby ma...@redhat.com:
I recently saw a case [1] where a misspelled assertion method
(asoptt_called_once_with vs assert_called_once_with) did not result in a test
failure because the object it was called on was created by
