Re: [Pharo-users] Why is the root class of tests named TestAsserter?
Pharo Smalltalk Users mailing list wrote
Still I think TestAsserter is not the most intuitive name. Asserter is not even an English word if I am not mistaken.
It came up in a few dictionaries in a google search, but clearly not the most common. My understanding is that [Verb]-er names are usually common names for roles (e.g. in dependency injection), but a code smell for object names. On the other hand (and not having the code in front of me), if it is an object which asserts, then maybe okay? Do you have any suggestions for a better name? ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
On Thu, 11 Oct 2018 at 21:52, Sean P. DeNigris <sean@clipperadams.com> wrote:
Pharo Smalltalk Users mailing list wrote
Still I think TestAsserter is not the most intuitive name. Asserter is not even an English word if I am not mistaken.
The good (and bad) thing about English (since contributes to its complexity) is all rules it adopted from many influences, so its its quite flexible about made up words. As Sean said, TestAsserter satisfies a particular rule. I can't think of a gooder alternative. cheers -ben
It came up in a few dictionaries in a google search, but clearly not the most common. My understanding is that [Verb]-er names are usually common names for roles (e.g. in dependency injection), but a code smell for object names. On the other hand (and not having the code in front of me), if it is an object which asserts, then maybe okay? Do you have any suggestions for a better name?
gooder he he
----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
participants (2)
-
Ben Coman -
Sean P. DeNigris