In-reply-to » Writing and running full e2e integration tests using Go and for Go CLI applications. Lookingo into one of:

@prologic@twtxt.net Logging is different, I meant regular errors messages. E.g. you invoke the program with an invalid argument or something else goes wrong. That should then be reported on stderr and not stdout. When striving for a good coverage rate, error cases should not be forgotten in my opinion. Ideally, error messages are tested, too. I’ve seen a bunch of cases in the past, where something was broken, because there weren’t any tests. But to be fair, I neglect them most of time, too. :-( Just checked, go-cmdtest merges both stdout and -err, that’s a no-go in my books.

⤋ Read More