A first performance problem: sequencing some tests

[briangmilnes]

I was writing some test code. Yes, I know you all probably think its a bit passe, but it helps while learning to see that my specifications are what I think they are.

I wrote a test function that sequenced 7 calls (to a printing function) and it was slow enough to cause condition splitting.

Is there a way to avoid this?