This post confused me initially b/c I could swear Filippo worked at Google now. Turns out the article is from 2016. Could the title be edited to match that to clear up any confusion?
It was a super useful guide to me because I have some integration tests that run against a Node version of a program and a new implementation of the same program in Go. It’s helpful to see what lines/functions/whatnot are actually covered by the integration tests vs needing unit tests as well. Eventually the in-process unit tests should cover all lines but since this 2nd Go implementation is work-in-progress I wanted to know coverage through the existing integration tests.
This post confused me initially b/c I could swear Filippo worked at Google now. Turns out the article is from 2016. Could the title be edited to match that to clear up any confusion?
Edited.
My strong preference is to never have more than one line in func main, so there is nothing to test.
It was a super useful guide to me because I have some integration tests that run against a Node version of a program and a new implementation of the same program in Go. It’s helpful to see what lines/functions/whatnot are actually covered by the integration tests vs needing unit tests as well. Eventually the in-process unit tests should cover all lines but since this 2nd Go implementation is work-in-progress I wanted to know coverage through the existing integration tests.