I've used gospec to implement the tests. I have keep commits for the implementation separate from commits creating specifications. If you don't like where gospec is heading I'll go back and rewrite the specs using native gotest style.
Reasons for doing this
I want to write a test suite for the backend specific SQL with the filesystem tree resembling this.
I have no problems using the stock testing package, I just enjoy the readability of BDD style assertions/expectations. I'll write them up after we decide how to implement this feature as a command flag instead of a property in the yml config file.