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.Dismiss alert
MockAcceptanceTests>>testUnexpectedMessageDefinedInObjectUsingAnotherObjectMethod
| actual |
actual := mock printString.
actual should be:'a GHEmptyMetaMessages'
The unexpected message leads to #stubDoesNotExpect: hook which is trying to use Object real methods as default action to handle the message. It does not work well for Object methods with self sends.
Possible improvement would be to use standard meta level for meta messages sent under deep meta call (which is happens in the example).
The text was updated successfully, but these errors were encountered:
dionisiydk
changed the title
Better unexpected message behaviour for complex method defined in Object
Better unexpected message behaviour for methods with self-sends
Dec 20, 2022
The following test shows the issue:
The unexpected message leads to #stubDoesNotExpect: hook which is trying to use Object real methods as default action to handle the message. It does not work well for Object methods with self sends.
Possible improvement would be to use standard meta level for meta messages sent under deep meta call (which is happens in the example).
The text was updated successfully, but these errors were encountered: