"I wanted the tests to be in separate methods so that you can see each assertion independently" not sure I understand the logic here. If you have three assertions in one function and you fail one, py.test will tell you which assertion it was and display the data that caused the failure, specific to that assertion.

If you're seeing many failures at the same time you can always use the ``-x`` option with ``py.test`` so you can examine the failure output 1 failure at a time. I'm not seeing a strong argument for iterating over the buildernames 3X when you could just iterate over it once and run 3 tests. My fear here is that we won't regularly run the slow tests and errors will creep into the regexes. If it's still too slow with a single iteration through buildernames we should probably reduce the number of buildernames examined and save the ``@slow`` test for the builds4h test.