Contract testing yana tabbatar da cewa sabis gida biyu suna jira jiya jiye ga kansu kan API ba tare da aiki tare a cikakken gwaji na haɗa. A cikin consumer-driven contracts (CDC), mai ƙarewa ya bayyana abin da yake buƙata, kuma mai samarwa yana tabbatar cewa zai iya isar da shi.
Cikakken gwaji na ƙarshen-ƙarshe zuwa sabis da yawa suna jiya jiye, suna karye, kuma suna da wahala a aiki akan kowane tarawa. Contract tests suna kama saurin karya API, a cikin keɓi.
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 na mai samarwa yana maimaita haka kuma yana gazawa idan ba ya dawowa da shari'ar nan.
| Contract test | Integration test | |
|---|---|---|
| Services running | Ɗaya a lokaci | Duka tare |
| Saurin | Sauri | Jiya |
| Suna kama | Contract breaks | Ainihin wiring issues |
Contract tests suna ba da tabbatacciyar rai cewa canjin mai samarwa ba zai kayyade mai ƙarewa, ba tare da kudin da karye na kunna tsarin gida.
Suna sa naimanin sadarwa mara iyaka da aminci: pipeline na kowane ƙungiya ta san nan da nan idan canjin sa zai ɓata kwafi wanda kowa ya dogara.
Ɗakin karatu na tambayoyin hira na IT tare da amsoshi cikakke — daga Junior zuwa Senior.
Ba da Gudummawa