&gt; I&#x27;m always very amused when people say OCaml can&#x27;t work at &quot;enterprise scale&quot;<p>Yeah, you will notice that quotes that show you shouldn&#x27;t take it too literally. ;) (also I have no doubt that Ocaml <i>can</i> work in a business. I just saw no one speak about it appart Jane Street, so I am curious)<p>What I was meaning that &quot;a team with a hierarchical organization, not-ony-geniuses, and more than 4 people&quot;. Few of the serious Ocaml projects (if any) fall in this category, which is common for all businesses.<p>About the testing tooling, I am well aware of the state of these technologies. I even contributed to some of them. Sorry but it&#x27;s light. It doesn&#x27;t cover all the spectrum of what you&#x27;ll want to test in a product.<p>Let&#x27;s take your (excellent) libs and see:<p>- OUnit: unit tests<p>- QCheck: unit tests<p>- iTeML: unit tests<p>Where is integration and functional testing ? Unit Testing only test a very strict subset of the &quot;does this work as intended&quot; question. I recommend you to see how some projects do their testing. For example any classic Rails project. You could be surprised.<p>Some open questions I struggle myself to answer correctly:<p>- Mocking modules without having a build mess with oasis<p>- Managing the model in a sane way<p>- Integration testing is an horror<p>And many more that I can&#x27;t recall now.