LinuxMusicians

Currently the unit tests (make check) cannot be performed when running from the tar-ball source tree.
The reason is that the test folder in the git tree contains a lot wav files used by the tests and these files are not (yet) included in the tarball.

The question is:
Do we even want to include these files in the tar-ball? They are rather big (29MB) and has no value whatsoever to the end-user.

I see unit testing as a dev-thing, not an enduser-task. So I'd not include that wav files, but refer to it through readme.

As viccuad said in the IRC channel: Debian tries to "make check" as many packages as possible before providing them. Our "make check" runs the unit tests. I think it makes sense to provide this to package maintainers.

An idea I already had a while back would be to just algorithmically generate (e.g., random with a fixed seed) a test drumkit and then check with this one. Then we wouldn't need much memory for this and still provide the unit tests for the tarballs.

Oh, and to also answer deva's initial question: No, I don't think we want to include 28MB just for the tests. Especially when we can also just solve it using the above mentioned approach.

Algorithmically generating the test wav files is a brilliant idea. They don't have to sound anything like a drum, just be there and contain samples with varying values.
A simple white-noise generator should do the trick.

I added this point to the roadmap and assigned myself.

Awesome!

Just for the record: we now generate the wav files algorithmically and this is on master since quite some time.