Timeline for Unit testing a REST API in Go
Current License: CC BY-SA 4.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 9, 2019 at 22:23 | history | edited | Eyal | CC BY-SA 4.0 |
typo
|
| Dec 9, 2019 at 16:57 | history | edited | Elias Van Ootegem | CC BY-SA 4.0 |
deleted 17 characters in body
|
| Dec 9, 2019 at 16:31 | comment | added | Eyal | @EliasVanOotegem per your suggestion, I updated my answer with an emphasis and explanation about unit and integration tests. | |
| Dec 9, 2019 at 16:29 | history | edited | Eyal | CC BY-SA 4.0 |
added 406 characters in body
|
| Dec 9, 2019 at 15:44 | comment | added | Elias Van Ootegem | Just to point an important takeway from this answer is, and maybe @Eyal could place some more emphasis on this, is that you're running integration tests, rather than unit tests. | |
| Dec 8, 2019 at 8:45 | comment | added | Eyal | @RolandIllig didn't think about it. I removed this suggestion from my answer. | |
| Dec 8, 2019 at 8:44 | history | edited | Eyal | CC BY-SA 4.0 |
deleted 237 characters in body
|
| Dec 8, 2019 at 7:34 | comment | added | Sasha Shpota | Thank you (+1). It looks better with docker-compose, I'll rework it. | |
| Dec 8, 2019 at 0:19 | comment | added | Roland Illig |
If the error message contains "}, you are screwed. The sensible way to produce JSON is json.Marshal.
|
|
| Dec 7, 2019 at 23:43 | history | edited | Eyal | CC BY-SA 4.0 |
Added docker-compose.yml suggestion
|
| Dec 7, 2019 at 23:16 | history | answered | Eyal | CC BY-SA 4.0 |