automated connection testing across multiple plugin projects

[atsushieno]

Now we have various combination of testable audio plugins (LV2-based plugins e.g. mda, and JUCE-based plugins e.g. andes and SARAH) as well as hosts (aaphostsample, JuceAAPAudioPluginHost), there should be some automated connection tests.

Although unlike normal Android apps it is not very straightforward, as we have to install more than just one app, and create a test matrix for all combinations. Also, those hosts need to become testable without UI (or we write UI testing).

To make it harder, there is still no way to automate JUCE-based projects on various CI servers (none successfully built them).

So far, here is what I usually test manually (not always everything):

• aaphostsample can apply mda effects (mda-Delay or mda-Detune)
• aaphostsample can play mda synths (mda-EPiano)
• aaphostsample can play JUCE synths (andes)
• JuceAAPAudioPluginHost can play mda synths (mda-EPiano)
• JuceAAPAudioPluginHost can play JUCE synths (andes)
• JuceAAPAudioPluginHost can play mda synths (mda-EPiano and then apply mda effects (mda-Delay or mda-Detune)