ewintr
/
go-kit
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

text edit

This commit is contained in:
Erik Winter 2022-02-21 06:45:09 +01:00
parent 6d53923d82
commit c47c4c53fd
2 changed files with 2 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
doc/httpmock_tutorial.adoc
View File

@ -1,10 +1,6 @@
= Unit Test Outbound HTTP Requests in Golang
= Unit Test Outbound HTTP Requests in Go
Erik Winter <ik@erikwinter.nl>
2020-07-04
:kind: tutorial
:public: yes
:language: en
:tags: golang, tdd, http, rest, go-kit
In general, when one wants to test the interaction of multiple services and systems, one tries to set up an integration test. This often involves spinning up some Docker containers and a docker-compose file that orchestrates the dependencies between them and starts the integration test suite. In other words, this can be a lot of work.

6
doc/logging-in-golang.adoc
View File

@ -1,10 +1,6 @@
= My Take on Logging in Golang
= My Take on logging in go
Erik Winter <ik@erikwinter.nl>
2021-04-08
:kind: tutorial
:public: yes
:language: en
:tags: golang, go-kit
The subject of logging comes up every now and then, in every group of developers. Apparently it is something to be opinionated about, like code formatting. Or to something complain about, like leaving off the cap of the toothpaste. If only there was a `go fmt` for logging. Or toothpaste.