We do, but that prints the rather ungainly "CommandError:" prefix before any message and so kind of screws up multi-line error messages (like this). Not sure what the best approach is.

The command stuff is tested using call_command with verbosity=0, so the output itself is untested.