This is an unusual question since I don't believe it lends itself to typical software development practices but I hope you can prove me wrong.
In MATLAB, my team have created several signal processing components, where data goes in one end, and different data comes out the other. What each of the components do is unimportant at this stage. What matters is that the typical testing pattern my team have adopted is that they write a script which generates the input data (each around 40MB in size), and then they run each test file through the applicable component (scripted). How they determine that their component passes the test or not is complete signal processing wizardry to me but lets assume its correct.
Typically, test data is generated only once and takes about half a day to do so. The test themselves can take anywhere up to day to run.
Coming from more of an application development background, and being given the task of integrating each component into a so-called "reference chain", I need to try and standardize testing and make it fool proof. One thing I wanted them to do is to use the unit testing framework to wrap their tests up into. The unit testing framework in MATLAB is, for the purposes of this question, just like JUnit.
My question is where does the scripts that generate the test data, and the test data itself fit in to the test ecosystem. Obviously the test data is a fixture, and can be treated as such, but I am a bit nervous about where the scripts that generate the test data fit in.
I would also welcome any critiques of my team's testing approach.