It’s been almost three and a half years since I published “Database Testing Patterns in Go“. The post was about how at clypd we were using dependency injection to test functions that would access external data sources. It’s a testament to the effectiveness of the pattern that it lasted so long. However, as our code base has grown over these years, we eventually started to run into some growing pains associated with the way we were doing things. Read More
At clypd, we place a lot of value on testing as a mechanism for ensuring code correctness and our approach to testing constantly evolves. We’ve spent the past few months learning and creating a new approach to mocking and testing functions that need to access data, whether from a database, a file, or over the network.