As we mentioned in the Technical requirements section of Chapter 1, An Introduction to Microservices, deployment and QA requirements can be very demanding. The only way to effectively handle this scenario would be through preemptive planning. I have always favored the inclusion of the QA team during the early requirement gathering and design phase. In the case of microservices, it becomes a necessity to have a close collaboration between the architecture group and the QA group. Not only will the QA team's input be helpful, but they will be able to draw up a strategy to test the microservices effectively.
Test strategies are merely a map or outlined plan that describes the complete approach of testing. Different systems require different testing approaches. It isn't possible to implement a pure testing approach, to a system that has...