How I write Go HTTP services after 7 years

Re:How I write Go HTTP services after 7 years by stockkid on Monday May 21, 2018 @05:22PM (#17121947)

Very nice.

> By calling ServeHTTP on the server, we are testing the entire stack including routing and middleware, etc. You can of course call the handler methods directly if you want to avoid this

What is the trade-off between the two? Does it make the tests significantly slower to test the entire stack rather than just a handler?

[ Parent | on HN ]

Re:How I write Go HTTP services after 7 years by carc1n0gen on Monday May 21, 2018 @05:33PM (#17122019)

I usually do both. I like having unit tests that test individual function that describe functionality. But I also like to have tests that ensure everything works as intended ones you throw everything together.

[ Parent | on HN ]

Re:How I write Go HTTP services after 7 years by stockkid on Monday May 21, 2018 @09:46PM (#17123213)

To be clear, you test individual functions handler uses, and to test the handlers themselves, you opt to test the whole stack as described in the article?

[ Parent | on HN ]

Re:How I write Go HTTP services after 7 years by carc1n0gen on Tuesday May 22, 2018 @04:21PM (#17129082)

I test the whole stack to ensure things work as intended when all put together. But I also write very isolated unit tests. I usually have them in separate test suites so I can choose which ones to run

[ Parent | on HN ]