Unlike pytest or JUnit, Go’s standard testing framework doesn’t give you as many knobs for tuning the lifecycle of your tests. By lifecycle I mean the usual setup and teardown hooks or fixtures that are common in other languages. I think this is a good thing because y...
Master Go test lifecycle with t.Cleanup(), subtests, and TestMain. Learn per-test, grouped, and package-wide setup patterns effectively.
How do you test functions that can’t be tested? That’s easy: you don’t! Instead, you use the magic function technique to break down the elephants—excuse me, functions—into smaller bites that you can test.
I first ran into Forth about 20 years ago when reading a book about designing embedded hardware. The reason I got the book back then was to actually learn more about the HW aspects, so having skimmed the Forth chapter I just registered an "oh, this is neat" mental note...
#567 — August 27, 2025 Read the Web Version Go Weekly Container-Aware GOMAXPROCS — The official Go blog kicks off a promised series of posts on Go 1.25’s new features with a look at some tweaked container-aware behavior around GOM...
Go’s garbage collector is designed not only to manage memory safely but also to pace itself intelligently, striking a balance between low latency and high throughput. This blogpost explores how the GC adapts its pace to workload demands, demonstrated through both sequential and...
A discussion of testing asynchronous code and an exploration of the `testing/synctest` package. Based on the GopherCon Europe 2025 talk with the same title.
#566 — August 20, 2025 Read the Web Version ☀️ We're back from a week off – the previous issue is here if you want to check it out again – and we should now be back every week until October at least :-)__Peter Cooper, your editor Go Wee...
New GOMAXPROCS defaults in Go 1.25 improve behavior in containers.