Although a discussion regarding “How to approach testing” is out of the scope of this post, I would say I am more on the side of J. B. (Joe) Rainsberger and I usually avoid Integration tests. This is not to say I have 0, it’s just I prefer not having to deal with them as they are quite hard to maintain.
I am usually on the side of “If I know I am sending the correct information to Manager, then I don’t care what happens next because it is not my problem”. This is why I have the Manager behaviour in the first place. technically I don’t need it, but since I am using Hammox then I must have a behaviour so I can have my unit tests. Thus, I place the Public API in the same file of the behaviour.
This allows me to test that I am “sending messages with the correct format” to Manager (because Hammox will blow up at compile time if I am not) and the test itself makes sure I am sending the “messages with the correct content”.
For these reasons I am leaning on going with the alternate code of my question. I was wondering if there was another solution I was missing, but after reading (and trying) the options everyone provided me here I am still not convinced that all the extra work will be worth it.
A very interesting discussion and I thank everyone for their participation (special kudos to @LostKobrakai !)
