So, just to explain my logic in my earlier statement.  Each of the tests, as I have it, tests a largely orthogonal code path to the others.  They all use the same buildername, but do something different with it. We could easily get two types of failures on two separate code paths.  But if we have 3 assertions in a single test, then it'll fail on the first assertion and won't run the second two until you fix the first one.  It's probably just a matter of style preference.  I tend to run the set and look for patterns of failures to help me identify where my bug is.  Again, not a huge deal, and I understand the savings of not iterating the loop multiple times.  So I'll go ahead and make those changes.