Michael Whatcott

@DisposaBoy - Staying up to date with the things we've chosen to depend on is, in general, a good practice. Using a package manager to manage the things we've decided...

Unfortunately, use of `t.Parallel()` has never been supported when using the `convey` library in conjunction with the web ui. Totally breaks the test output parser.

Well, it depends on your definition of "working" is. The tests execute, but the printing of the assertions is wacky.

I've accepted it as a known limitation because of the work required to resolve. I know that I'm the creator of GoConvey and all, but I've actually moved to [gunit](https://github.com/smartystreets/gunit),...

@ghostsquad - This is a great question. I've touched on it before in various instances but haven't ever put together a comprehensive answer to those questions. The answers probably deserve...

@ghostsquad - As promised, a comprehensive [blog post](https://smartystreets.com/blog/2018/03/history-of-go-testing) that _hopefully_ answers your questions, you know, for when you have trouble getting to sleep. :)

@tyranron - No reason to abandon GoConvey if it meets your needs.

Have you tried setting them in a .goconvey file? https://github.com/smartystreets/goconvey/wiki/Profiles I'm not sure if it would work, but it's worth a try.

Hmm, the function that exits is being called by the test harness. If the function causes the process to exit, you lose the ability to assert within the same process...

I see now. You want to pass a reference to the function (without calling it in the assertion), and then have the assertions package spin up a subprocess to call...