Amen!
“One should not complexify a class’s API purely to make testing easier. Testing exists to serve the model code, not the other way around. To cite the classic dependency injection example, if the only reason you pass a Clock object to a constructor instead of creating one privately inside the class is to support unit testing, then don’t do it. Unit testing is no excuse for heavily coupled classes exposing their private parts and violating
VMWare Fusion 2.0 (beta)
I just love my VMWare Fusion and with the upcoming version 2.0 I’m going to love it even more. Just watch the below YouTube video to see why!