This text is the last part of a series of posts I wrote about one of the technologies that have had the most impact on me in recent years: WebAssembly.

Recently, in a code review, the great Cassio Botaro gave me a handy tip: refactor some tests to use the test helpers feature from the testing package.

In the previous post, we saw that there are different types of load tests and what their objectives and characteristics are.

When we talk about “load testing,” perhaps the first thing that comes to mind is “sending traffic to the application until it cries.

This post is the second part of a series about WebAssembly and Go. In the first post, we saw how to run Go code in a web browser.

Occasionally, a technology emerges that significantly impacts developers’ daily lives—things like Linux, Git, Docker, and Kubernetes, among others.

The version 1.21 of the language implemented an essential new feature. According to the documentation:

In the last post, we saw how to create a Kubernetes operator using operator-sdk. As that text was quite long, I decided to write this second post to focus on the application’s testing part.

If you develop APIs or microservices, especially in medium to large environments, you probably use Kubernetes.

I came across an exciting project called Google Developer Experts. According to the official website, this is a group of “experienced Google technology experts, influencers, and thought leaders.