...
A) You are probably right in all aspects you mention. But the most important aspect from your question is that you do not question the fact that each mfile should have an associated test file in the first place. You only question where to put this test file. And the aspect of having a test file in the first place is the most important part of what we try to achieve. Therefore we put the test file between the regular m files, so that people who are not yet test-minded will start to make tests too. An additional advantage of putting test files next to the regular mfiles is that test files are a working code example, and can be considered as an extension of the documentation. Not until the majority of OpenEarth participants actually makes test, can we start to think where to relocate them. Actually we already investigated that, we decided to relocate all test data to another directory to keep the tools collection small (https://repos.deltares.nl/repos/OpenEarthTools/test/
). In addition there is already a testing toolbox (Mtest) that scrolls all directories and filters all _test.m files. This toolbox is part of the OET maintenance tools (https://repos.deltares.nl/repos/OpenEarthTools/trunk/matlab/maintenance/).
We run this toolbox on a teamcity built server (currently not yet available for non-Deltares participants, but will be in 2011) that also includes all the test data (simple adds all directories to matlab path).