Hi all,<div><br></div><div>I&#39;m writing some library code and I have hunit-tests and quickcheck-tests. I&#39;m facing the problem of where to put these tests. These are the options I can think of:</div><div><ul><li>Put the tests for a function in the same file where the function is defined. This is good because tests are close to the code being tested and work as a sort of documentation for it. But it&#39;s bad because the file requires HUnit, QuickCheck, Test.Framework, etc. to compile.</li>
<li>Same as above, but use some sort of preprocessing flag to ignore the Test suite when compiling the library (hence no dependencies on test libraries), but leave the code in place. No dependencies, but ugly.</li><li>Put the tests in completely separate files. Good because library dependencies are reduced, but bad because tests are somewhat &quot;disconnected&quot; from the functions they are testing.</li>
</ul><div>What do you expert suggest? How should I organize my test suites?</div></div><div>(The same conundrum applies to benchmarking code.)</div><div><br></div><div>Thanks,</div><div>Lorenzo</div>