Tony Morris

@davetchepak @pjimmy @TheColonial ie. separate pure and impure, and only test the pure code?

@liammclennan @davetchepak @pjimmy I think that's a great approach. Put more effort into writing pure and leaving impure at the edges.

@TheColonial @liammclennan @pjimmy Can still test impure code if that helps. But if majority is pure then majority should be easy to test.

@davetchepak @TheColonial @pjimmy doesn't that bring you back to mocks?

@liammclennan @TheColonial @pjimmy I think automating it encourages us to always inject objects, where pure functions might be appropriate.

@davetchepak @liammclennan @thecolonial @pjimmy use message passing /w sum types, fakes can then be lists

@robertream @davetchepak @TheColonial @pjimmy Interesting. Can you elaborate?

@liammclennan @robertream @davetchepak @pjimmy The point is abstracting to a list, then your mock literally means “pass in a list”.