Fair point. I have several other custom grunt tasks I'm authoring that output TC messages. There is a specific TC escaping syntax, as well as a few things that are nice to have abstracted (like flowIds). For me, it made sense to wrap that stuff up in its own module. There is a lot more this reporter can do (like provide diffs, and other more detailed test information). Down the road the TC dependency should become more handy.