The problem when mocks happen when all your unit test passes and the program fails on integration. The mocks are a pristine place where your library unit test w

The problem when mocks happen when all your unit test passes and the program fails on integration. The mocks are a pristine place where your library unit test works like a champ. Bad mocks or bad library? Or both. Developers are then sent to debug the unit test... overhead. I don't much about ML but I would think that they should follow some rules resembling judicial rules of precedence and witness cross-examination techniques.