no need to be sorry, thanks for the ‘fix’, hope you work out what broke things in v2 at a non-stressful pace…
1 Like
Plug here for unit tests. Makes is possible to re-factor the code without breaking it.
It’s alright if you’re testing logic, for example I use Catch2 daily. But for audio, and especially reverb algorithms, you’d need a test harness wouldn’t you. Otherwise you only have scopes, spectrograms, plots, and your ears.
Do you have suggestions for an automated test harness for audio processing?
I wrote my own. In this particular case just looking at the peak output would do. For some stuff I do crude feature recognition in a high res fft. If you are interested you should look at me (old) repo.
Of if by test harness you mean something like gtest, I just use a dumb command line build and asserts.
FWIW I think my repo is 2/3 unit test and 1/3 code. Like 40,000 lines of test code.
3 Likes