· Manikandan · Microservices
Day 51: Consumer-Driven Contract Test
A consumer-driven contract test lets the team that *calls* an API write down exactly what it needs from that API (requests it sends, response fields it reads).
A consumer-driven contract test lets the team that *calls* an API write down exactly what it needs from that API (requests it sends, response fields it reads).
A service component test starts one real microservice (its real controllers, validation, business logic, EF Core mappings and messaging code) inside a test process, replaces everything *outside* the service boundary...