Simplicity is prerequisite for reliability ― Edsger W. Dijkstra

Spring Boot makes it easy to setup and start a microservice project. But in microservice’s world, it is hard to test changes in all architecture. Because it is hard to setup same environment in local. So each service should responsible their own changes and guarantee that it won’t break any RPC call or business logic with new changes. Integration tests help in that manner to release the changes in more confident. So it is important to create an environment which is as much as close to production.

Spring Test provides have few options to test our controllers. So in this post let’s take a look to how to test controllers with TestRestTemplate. These tests are run as an integration tests. In that kind of tests are no difference what are our application doing on production(ignoring other system components proxy servers, load-balancing etc.). These kind of tests are suitable to test any HTTP related problems. You also have more argument when some of your client/friend come to your table and blame you that your endpoints are not working.

How are you testing your Controllers? Are you ignore unit tests for them? Or you just write some time consuming, heavyweight integration tests. Let’s take a look to MockMvcTest.

Nowadays I am reading Thomas Colmen’s book, Algorithms Unlocked. I like one example in it which demostrate that how good programmer perform better in a slow computer.

Spring Transaction Management uygulama için basit ve yönetilebilir bir uygulama çatısı sunar. Java Transaction yönetimi JTA(Java Transaction API),JDBC(Java Database Connectivity),JPA(Java Persistence APİ), JDO(Java Data Objects) gibi standartlar altında toplanmıştır.