One thing I'm a little afraid about is, these types of modules easily/quickly turn into a dumping ground for "Stuff that doesn't fit someplace else and could someday maybe possibly be used by more than one test" :grinning: 

So, this module may work better as a package, following a kind of mixin-pattern with functionality organized by module names.  Thus we allowing the "Tooling" class (or metaclass) to grow quite and avoid the "Garsh! Where I done did put that code again?" maintenance-headache.  It would also help out with unittesting, since unittests would have a convenient place/way to mock/inject code.

Whatcha think?