You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
assignee='https://github.com/voidspace'closed_at=<Date2014-04-16.18:06:58.274>created_at=<Date2014-04-15.15:51:18.917>labels= ['type-bug', 'library']
title='unittest.mock.Mock should not allow you to use non-existent assert methods'updated_at=<Date2015-07-16.22:51:51.947>user='https://github.com/voidspace'
A common problem with unittest.mock.Mock is to mistype an assert method. Because mocks create attributes on demand your test will pass without error.
We should raise an AttributeError if you access any attribute name (that doesn't exist) starting with assert or assret. There should also be a keyword argument allowing you to get the old behaviour if you need it (but this new feature should be on by default).