I had my sort of tester by using the shell object and printing time and messages. I have come across some pd patch that tests the audio latency and so forth.. I think its in the browser of pd-extended somewhere.
if you know a good way to measure this (cputime or whatever), a nice thing could be an abstraction that makes a test and outputs the results.p.s.: interesting exercise for those that wanna see how much time your cpu
wastes with gui in pd is running a patch without gui. I had a project that
used my DTW in pd and a long patch (for my standards) and when we ran it for
the first time without gui... wow. Somethings went faster than expected and
some didn't work because it was all too fast :) A bit of cleaning solved it,
but its an interesting test for non-visual patches.