Contract testing jivverifika li żewġ servizzi huma d'acordo fuq l-API tagħhom mingħajr li jħaddmu flimkien f'test ta' integrazione kompletu. Fl-consumer-driven contracts (CDC), il-konsumatur jiddefinixxi dak li għandu bżonn, u l-provveditur jivverifikat li jista' jipprovvedi.
Testaw end-to-end kumpleti fuq ħafna servizzi huma bil-ħin, instabbli, u diffiċli biex jixtieġu fuq kull commit. Contract testaw jaqbdu bidla API li timkissħa kmieni, b'mod iżolat.
1. Consumer writes expectations ─▶ generates a CONTRACT (Pact file)
2. Contract published to a broker
3. Provider runs the contract against itself in its own pipeline
4. Provider build FAILS if it would break the consumer
// consumer declares exactly what it expects from the provider
provider.given('order 42 exists')
.uponReceiving('a request for order 42')
.withRequest({ method: 'GET', path: '/orders/42' })
.willRespondWith({
status: 200,
body: { id: '42', total: 99.5 } // the shape the consumer relies on
});
IC tal-provveditur tirriprodwċi dan u tagħfal jekk ma jirritornax dik il-forma.
| Contract test | Integration test | |
|---|---|---|
| Servizzi jitqallgħu | Wieħed alla ħin | Kollha flimkien |
| Veloċità | Mhux | Bil-ħin |
| Jaqbdu | Tkissir il-kuntratt | Problemi reali tal-ħamsa |
Contract testaw jegħluk ikun fiduċa li bidla tal-provveditur ma taqsarx konsumaturin, mingħajr il-kost u l-instabbiltà ta' spin up tas-sistema kollha.
Jaħdmu d-deployment indipendenti sikur: il-pipeline ta' kull tim jaf immedjatament jekk il-bidla tiegħu tkun teksser kuntratt li xi ħadd jiddependi fuqu.