> Effectively I always asked them what they think the code "should" do and what the results should be.
For me I (and the customer) all thought we knew what it should do, but it's always good to spell it out for everyone so we all understand when / or even if we're seeing an exception.
Lots of "Woah hey is that what the protocol really says?" moments too.