Part 3 of 3
Rapid integration testing is a key to delivering frequent, high quality software. But, environment availability is often a limiting factor. In Part 1 we took a look at the limitations on environments, in part 2 ek we will conclude this 3 part blog by looking at a realistic scenario that brings the techniques together.
A realistic scenario that brings the techniques together
The fictitious example of a major system called Marketplace shows how to use the tools together. Marketplace is made up of many pieces.
- 60 web services that are somewhat tightly coupled. Four teams each own 15 services.
- Mainframe components contribute to 20% of transactions; the components rarely change and are owned by another team.
- The front end website, in front of the services, is owned by the dot-com team.
- Data feeds from 2 third parties are used (via web service). One is metered on transactions, the second is not.
The Marketplace release team had one large Integration Test Environment (INT) and a Performance Testing Environment (PERF). Each of the six teams now has a small test lab where they can test some of the components, but they cannot test any integrated scenarios. Integration testing is on the release schedule and release management has governed access to the INT and PERF environments.Read More