I introduce the process I went through to diagnose the bug and determine the correct integration test solution to fix it the right way. In doing so, I had to create a test that accurately reproduced the scenario my service was experiencing in PROD. I had to create a fix that took my test from failing to passing. And finally, I worked to increase confidence in the correctness of code for all future releases, which is only possible through automated testing.
When it comes to brewing, one of the most critical considerations is sanitization. The same fact can be said for development. In brewing you can introduce unintended flavors, create a lesser end product, or completely ruin your hard work. With development, you can introduce inaccuracies or bad data, errors can be caused or exposed to attack, and security holes can be created.
With best practices in sanitization, we can all enjoy better applications and better beer. In this blog, I discuss the importance of data sanitization in development (with tips for success), with parallels to sanitization in brewing.
There are very good reasons to use immutable objects in certain languages. In JavaScript, however, I’m still kind of…. meh.
In this blog post, I plan to discuss my reasonings with the hope that I might spark discussion on the use of Immutable Objects in JavaScript…
In this post, Matthew Brown first discusses why we need unit tests. He then demonstrates writing unit tests for an existing reference Angular application with an eye for how to make good use of testing tools for Angular.
Attention: This article was published over 10 years ago, and the information provided may be aged or outdated. While some topics are evergreen, technology moves fast, so please keep that in mind as you read the post.At Keyhole, we have published several blogs about Microservices. We’ve talked about architectural patterns used in a Microservices environment such as service discovery and …