On Wed, Jul 27, 2011 at 9:40 PM, Gabriel Beddingfield
<gabrbedd(a)gmail.com> wrote:
The mock library wouldn't necc. /work/... just
simply do just enough for
testing.
you have to define "testing" for that to be viable.
suppose you want to test internal client latency or data "movement"
that relies on JACK port connectivity.
this pretty much requires a working libjack that does everything
except talk to a real backend. aka jackd -d dummy
remember that "time" is an important component of any code that uses a
JACK-like API. a test framework has to replicate the periodic nature
of it, at the very least, even if its not RT-ish.