Mtihani wa kontrakta unathibitisha kwamba huduma mbili zinakubali API yao bila kuziendeza pamoja katika mtihani wa ujumuishe kamili. Katika mikataba inaosaagwa na watumiaji (CDC), mtumiaji anabainisha kinachohitajika, na mtoa huduma anathibitisha kwamba anaweza kulifanya.
Mitihani ya end-to-end kamili kwenye huduma nyingi ni polepole, haipo kwa kutegemeka, na ni ngumu kuendeza kwa kila commit. Mtihani wa kontrakta unakamata API yanayokatika mabadiliko mapema, kwa njia ya kujitegemea.
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
});
CI ya mtoa huduma inaeneza hii tena na hufeli ikiwa haikutoi sura hiyo tena.
| Mtihani wa kontrakta | Mtihani wa ujumuishe | |
|---|---|---|
| Huduma zinakutika | Moja kwa wakati | Zote pamoja |
| Kasi | Haraka | Polepole |
| Kunakamata | Kontrakta inayokatika | Masuala halisi ya wiring |
Mtihani wa kontrakta unakupa ujinga kwamba mabadiliko ya mtoa huduma hayatakatakata watumiaji, bila gharama na kutegemeka kwa kuanzisha mfumo mzima.
Hufanya mgawaji huru kuwa salama: bomba la kila timu lijua mara moja ikiwa mabadiliko yake yangevunja kontrakta inayotegemeza mtu mwingine.