CoreyScott.dev

In the previous posts, we examined the Why, When, and How Much of testing. In this post, we will complete the thread with an examination of What we should be testing and What we should not be testing.

In the previous post, we examined the Why and When of testing in this post, we will build on that foundation and look at How much we should be testing.

When it comes to testing, the most common misunderstanding is the motivations of testing itself. Some folks see testing as a burden imposed from on high. Some folks see testing, or more specifically, test coverage, as a metric that determines how well they did their job. Sorry, but neither of these is true. This post will address these fallacies and give you a different perspective on testing.

Introduction In Part 1 of this series, we introduced the goal of understanding how our system performs by adding instrumentation. This article expands on this goal by taking...

Introduction After we set ourselves the goal of system reliability, our first goal must be awareness.  Simply put, we must be fully aware of how...

The following content is a small extract from my latest book Beyond Effective Go – Part 1 – Achieving High-Performance Code. Slow consumers When designing function...

A small extract from my latest book about deadlocks

This is my light-hearted attempt to help engineering managers get the most value out of a downtime incident. Introduction So you had an incident? Condolences.On...

This is my light-hearted attempt to help engineers get the most value out of a downtime incident.

This post can also be found on the Grab Engineering blog In Southeast Asia, when it rains, it pours. It’s a major mood dampener especially if you are stuck...