Golang

🧭 Where we left off Welcome back to our ongoing series on measuring test coverage for binary programs! In part 1 we used Go’s built-in -cover flag — clean and accurate, but only works if you own the source and can recompile. In part 2 we used valgrind and gdb to trace gzip without touching its source. In part 3 we explored Intel PIN, a proper dynamic binary instrumentation framework — powerful, but it came with a ~100MB proprietary C++ SDK and was limited to x86_64. ...

😸 TL;DR Being lazy, I made a tool to run qcow2 images for my convenience. It now supports x86_64, aarch64, s390x, and ppc64le. Feel free to use it if you find it useful! 📖 The back story If you’ve ever typed qemu-system-x86_64 into your terminal, you know the feeling. A creeping dread. A cold sweat. The QEMU headache. It’s that special migraine reserved for developers who know they’re about to spend the next ten minutes deciphering their own shell history to remember that one magic flag for networking. ...

☂️ Intro When your code includes a suite of unit tests, code coverage is an important metric to measure the test effectiveness and it’s rather easy to obtain; there are plenty of tools around. Image credits to: Nataliya Vaitkevich On the other hand, often we also need to do integration or E2E testing, as in our QA journey we are mostly running real world programs instead of single well-chosen functions. Let’s start with a basic use case, and prepare a simple program tailored for this purpose. ...

Intro Since 2015, GoLab is one of the oldest and most renowned conferences about the Go Programming Language ecosystem in the world, attracting a large audience of Gophers from all over the globe. My bad, I forgot to take a picture of the t-shirt 🤷 In recent years, the organizers hosted some of the biggest names in the industry who have shared their insights and experiences with our attendees. ...