The What, When, Why, and How of Testing (Part 3)
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.
The What, When, Why, and How of Testing (Part 2)
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.
The What, When, Why, and How of 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.
Getting Started with SRE – Step 2 – Dashboards
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...
Getting Started with SRE – Step 1 – Instrumentation
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...
Book Sneak Peak: Slow Consumers
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...
How-to fix tightly coupled Go code
Have you ever added a new feature only to have another one break? After fixing the break, something else breaks, like some kind of bug whack-a-mole?
Have you ever...
Testing External Services
There seems to have been a lot of talk around me lately in relation to "dev boxes" and "testing on staging".
After unsuccessfully trying to convince folks of why I think this is a bad...
5 IntelliJ Tricks for Gophers
A small collection of IntelliJ tips and tricks for getting more out of your day or simply doing the same amount for work with less effort.
1. Install the IntelliJ Go plugin from here
Enough said.
2....