A microservice architecture is made of single responsibility-focused services that are small, independently and deployable. A complete business application can be obtained aggregating and orchestrating this kind of service. These services are independent of each other, giving you the ability to easily test and deploy each one individually. . A single instance of a microservice […]
Continue Reading
Much like we gain knowledge about the behavior of the physical universe via the scientific method, we gain knowledge about the behavior of our software via a system of assertion, observation, and experimentation called “testing.” There are many things one could desire to know about a software system. It seems that most often we want […]
Continue Reading
Continuous Integration The first step to delivering consistent and high-quality software is Continuous Integration (CI). CI is all about ensuring your software is in a deployable state at all times. That is, the code compiles and the quality of the code can be assumed to be of reasonably good quality. Source control CI starts with […]
Continue Reading
Test Double is a generic term for any case where you replace a production object for testing purposes. We now introduce a significant piece of the unit testing approach—test doubles. Using test doubles is a way of creating a class whose behavior can be changed at runtime. These classes can be used to unit test […]
Continue Reading
I know that Martin Fowler has written about this extensively, but I wanted to write a concise version, since this point seems to bear reiterating from time to time. Mocks aren’t stubs. Specifically, I recommend against setting an expectation on a method (“mocking” it) when you really want to simulate a specific response from that […]
Continue Reading