Hmmm, though is this the case really?  99.9% of test runtime (over the long-term) people aren't going to care about seeing every single docker command (especially if they're accessible in a log file somewhere).  Though I agree it is helpful for test-development, it's not necessarily true during 'normal' operation.  Also console/logging output is ssslllloooowwwww, multiplied by every message in every test, it very quickly adds up.

If you want to setup a way to log / record every docker command into a separate log or results or stream for historical reference, that would be **a totally cool idea**  I just don't want to see them all on my console, all the time, for every test.  Having the option to switch it on/off during development is key.   So I'm going to reverse now, I think I prefer having this just as a  global config. option, defaulting to "off" is the better option.  Sound reasonable?