Contract testing negesahake manawa rong serbis setuju babagan API lan tanpa njalanake dadi tunggal ing test integrasi lengkap. Ing consumer-driven contracts (CDC), consumer nggawe apa sing dibutuhake, lan provider negesahake yen bisa nyedhiyakke.
Test end-to-end lengkap ing akeh serbis iku alon, gampang mbrebes, lan angel kanggo njalanake ing saben commit. Contract test ngenteni owah-owahan API sing mecah ing awal, terisolasi.
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 provider muter maneh iki lan gagal yen ora bali marang bentuke kasebut.
| Contract test | Integration test | |
|---|---|---|
| Serbis njalani | Siji-siji | Kabeh bebarengan |
| Kecepatan | Cepet | Alon |
| Tanggap | Putuse kontrak | Isu wiring nyata |
Contract test menehi kapanatian bahwa owah-owahan provider ora bakal mecah consumer, tanpa biaya lan ketidakstabilan saka njalanake kabeh sistem.
Kulah nggawe deployment mandiri aman: pipeline saben tim ngerti langsung yen owah-owahane bakal nglanggar kontrak sing ana sing gumantung.