[issue31541] Mock called_with does not ensure self/cls argument is used

Pablo Galindo Salgado added the comment: Will -- resolution: -> not a bug stage: -> resolved status: open -> closed ___ Python tracker ___ __

[issue31541] Mock called_with does not ensure self/cls argument is used

Change by Pablo Galindo Salgado : -- Removed message: https://bugs.python.org/msg329801 ___ Python tracker ___ ___ Python-bugs-list

[issue31541] Mock called_with does not ensure self/cls argument is used

Pablo Galindo Salgado added the comment: I agree with Karthikeyan: This is is the expected behaviour. The moment you use a mock, any implementation details are lost unless you use wraps or similar to also transfer the call to the/a real object. -- nosy: +pablogsal __

[issue31541] Mock called_with does not ensure self/cls argument is used

Karthikeyan Singaravelan added the comment: mock can only verify if the function is called with the correct number of arguments as you have passed spec. It doesn't verify whether the function implementation is correct like calling Something.foobar() because it's not designed to verify the fu

[issue31541] Mock called_with does not ensure self/cls argument is used

Change by Karthikeyan Singaravelan : -- nosy: +xtreak ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https:/

[issue31541] Mock called_with does not ensure self/cls argument is used

New submission from JonathanHuot: Mock "assert_called_with" does not contain a possibility to verify if "self" or "cls" is used when mock is called. So, in unittests, all tests are passing but code is broken. Example : Steps to reproduce: == class Something(object): def f