As mentioned in the Prerequisites section of Chapter 1, An Introduction to Microservices, deployment and QA requirements can become more 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 is not possible to implement a pure testing approach to a system that is developed using a newer approach rather than the earlier developed system. Testing strategies should be clear to everyone so that the created tests can help non-technical members of the team (such as stakeholders) understand how the system is working. Such tests can be automated, simply testing the business flow, or they could be manual tests, which can be simply performed by a user working on the User Acceptance Testing system.
Testing strategies or approaches have the following techniques:
- Proactive: This is a kind of early approach and tries to fix defects before the build is created from the initial test designs
- Reactive: In this approach, testing is started once coding is completed