This looks good at a glance, but we should have a test. And actually, there's no way to do that easily because .query's response is hardcoded to go to the post window. This would be a good opportunity to make query more flexible. It could take an action argument like all the other buffer methods. When nil, it would have the current behavior (backwards compatibility). Otherwise, the function would be called with bufnum, numFrames, numChannels, sampleRate as arguments.

Writing tests is actually a pretty good way to catch interface design flaws IMO. :)

Thoughts @jamshark70 @telephon ?

yes, like this perhaps?

query { |action|
	if(bufnum.isNil) { Error("Cannot call % on a % that has been freed".format(thisMethod.name, this.class.name)).throw };
	action = action ?? {
		{ |bufnum, numFrames, numChannels, sampleRate|
			"bufnum: %\nnumFrames: %\nnumChannels: %\nsampleRate: %\n".format(
				bufnum, numFrames, numChannels, sampleRate
			).postln
		}
	};
	OSCFunc({ |msg| 
		action.valueArray(msg.drop(1)) 
	}, \b_info, server.addr, nil, [bufnum]).oneShot;
	server.listSendMsg([\b_query, bufnum])
}

Exactly! Then the test becomes trivial to write and the method is much more flexible.

Sorry for the delay on this. I've modified the query method as suggested and added a simple UnitTest. Please review 👍

FYI - I can't spell.

Will do the doc addition and change the test to use a non-default server.

Thanks for this! I think the unit tests are very well written and would make good examples.

Merci, mon ami! 😀