Testing in Go: philosophy and tools
Testing in Go: philosophy and tools
Posted Jun 1, 2020 5:30 UTC (Mon) by jezuch (subscriber, #52988)In reply to: Testing in Go: philosophy and tools by kunitz
Parent article: Testing in Go: philosophy and tools
> the pedestrian approach feels often dull, but it gets the job done in a way that you will understand in 5 years from now
In the case of tests written as a not-very-structured mass-of-code, I'm pretty sure I won't understand the intent behind the test after 5 days :) The most important thing is not the code itself - it's the intent behind the code. That's something imperative programming is inherently bad at - and the language makes it even worse when it doesn't support concept X.