I’m currently trying to work out how to best manage data for integration tests, and I’m wondering if it’s a “solved” problem, or one for which there is community consensus?
I have an application + library that processes audio files, and I would like to be able to run tests with example audio workloads. I’ve struggled so far to find a neat solution. So far, I have tried and been unsiatisfired with:
- git-lfs to store test data in a
- downloading data in a cargo build script
The former makes it slow to check out the code, while the latter is brittle and does not guarantee a coupling between the data being present, and the test that requires it.
Are there any better options?