Testing Java Microservices

With traditional software unit tests, there's never a guarantee that an application will actually function correctly in the production environment. When you add microservices, testing becomes even more tricky. \n \n \n \n Testing Java Microservices teaches readers how to write tests like unit, component, integration, container, contract, chaos, and more. Along the way, it also covers technologies like the Arquillian ecosystem, Wiremock, Mockito, AssertJ, Pact or Gatling. Finally, the book demonstrates how everything fits together into the Continuous Delivery pipeline. \n \n \n \n Key Features: \n \n * Practical hands-on guide \n \n * Writing Persistence tests \n \n * Teaches test strategies \n \n * Shows how everything fits together in the Continuous Delivery Pipeline \n \n \n \n Readers should be comfortable programming in Java. Experience with testing tools like jUnit is helpful but not required. Some experience in Java EE, Spring and Docker is also helpful. \n \n \n \n About the Technology: \n \n A microservice may consist of several, several hundred, or even several thousand of lines of code. Microservices enable programmers to isolate and scale smaller pieces of an application, rather than the entire application. \n