Rather than use the SelfShuntPattern, it might be just as easy, and more clear, to define an instance of the ShuntPattern or MockObject right there in your test method. Then, each method may use a different variation of the "shunt" appropriate for whatever is being tested. StevenNewton provided this example:
I HaveThisPattern, but in a slightly different implementation than described in the above paper. Inner classes (either anonymous or not) can serve as your shunt for classes you would like to test but you can't because your test already extends TestCase. The example in the above referenced paper like so:

when I only need it for the current test. I extract the Mock later if I find myself tempted to copy/paste the original test. (Sometimes I extract the Mock after giving in to temptation, with two or three copies of the anonymous inner class already lying around.)