![\"consumer-contract-test-geek\"](\"\/wp-content\/uploads\/2017\/01\/consumer-contract-test-geek.jpg\")
<\/p>\n
Sistemimizde -n tane servis’in var oldu\u011funu d\u00fc\u015f\u00fcnelim ve hepsi loosely coupled bir \u015fekilde hayatlar\u0131n\u0131 s\u00fcrd\u00fcrmektedir. Biliyoruz ki bitmek bilmeyen business ihtiya\u00e7lar\u0131n\u0131n kar\u015f\u0131s\u0131nda, sisteme s\u00fcrekli ek \u00f6zellikler kat\u0131lmaktad\u0131r. Bunlar\u0131n yan\u0131 s\u0131ra ger\u00e7ek hayatta legacy application’lar\u0131n, bir anda yeni mimarilere de ge\u00e7irilebilmesi de m\u00fcmk\u00fcn olmamaktad\u0131r. Bu sebep ile her bir mod\u00fcl\u00fc par\u00e7a par\u00e7a microservis’lere ta\u015f\u0131mam\u0131z gerekebilece\u011fi i\u00e7in s\u00fcrekli bir deployment<\/strong> ihtiyac\u0131 do\u011facakt\u0131r. Peki bu deployment’lar s\u0131ras\u0131nda hangi servisin nereyi etkileyece\u011fini nas\u0131l bilebiliriz ve ilgili servisi t\u00fcketen di\u011fer servislerin bozulmayaca\u011f\u0131n\u0131 nas\u0131l test edebiliriz?<\/p>\n En s\u0131k kar\u015f\u0131la\u015f\u0131lan durumlardan birisi, endpoint’lerin client’\u0131n etkile\u015fimi olmaks\u0131z\u0131n de\u011fi\u015ftirilmesidir.<\/p>\n \u0130\u015fte bu tarz durumlar kar\u015f\u0131s\u0131nda insan bazen, ke\u015fke monolith bir application geli\u015ftiriyor olsayd\u0131k demiyor de\u011fil. :) \u0130\u015fin geyi\u011fi bir\u00a0yana monolith bir application i\u00e7in integration test’ler yazmak, birden \u00e7ok distributed microservice’lere implemente etmekten \u00e7ok daha basit.<\/p>\n Konumuza geri d\u00f6necek olursak e\u011fer, microservice yap\u0131lar\u0131nda bu tarz problemler i\u00e7in asl\u0131nda yeni olmayan bir yakla\u015f\u0131m\/pattern mevcuttur. Bir ka\u00e7 d\u00f6nemdir\u00a0microservice mimarilerinin pop\u00fclerle\u015fmesi ile \u00f6nem kazanan bu yakla\u015f\u0131m, Consumer Driven Contracts Testing<\/strong>\u00a0olarak ge\u00e7mektedir.<\/p>\n Consumer Driven Contract temel olarak API contract’lar\u0131n\u0131n kullan\u0131mlar\u0131n\u0131 client’lara\u00a0tan\u0131mlayarak, de\u011fi\u015fimler s\u0131ras\u0131nda ya\u015fanabilecek problemlerin bir nebze \u00f6n\u00fcne ge\u00e7ebilmeye yard\u0131mc\u0131 olmaktad\u0131r. Consumer Driven Contracts’\u0131 .NET taraf\u0131nda implementasyonu i\u00e7in Pact<\/strong> <\/em><\/a>isminde harika bir framework mevcuttur. Makale s\u0131ras\u0131nda ger\u00e7ekle\u015ftirecek oldu\u011fumuz \u00f6rne\u011fimizde, Pact framework’\u00fcn\u00fc kullanarak contract specification<\/strong>, contract verification<\/strong> ve contract distribution<\/strong> nas\u0131l ger\u00e7ekle\u015ftirilir gibi konular\u0131 ele al\u0131yor olaca\u011f\u0131z.<\/p>\n Consumer Driven Contracts’\u0131n \u00e7al\u0131\u015fma mant\u0131\u011f\u0131 basic concept olarak a\u015fa\u011f\u0131daki gibidir.<\/p>\n Bunlara ek olarak, farkl\u0131 teknolojiler ile geli\u015ftirilmi\u015f service’ler aras\u0131ndaki entegrasyonu da m\u00fcmk\u00fcn k\u0131lar. Pact\u00a0initial olarak Ruby i\u00e7in geli\u015ftirilmi\u015f bir framework’d\u00fcr ve \u015fuan bir \u00e7ok programlama dilinde yayg\u0131n bir hale gelmi\u015f durumdad\u0131r. Contract verify i\u015flemi i\u00e7in olu\u015fturulacak olan pact file’\u0131 JSON format\u0131nda olaca\u011f\u0131 i\u00e7in, farkl\u0131 platformlar aras\u0131nda da kolayl\u0131kla implemente edilebilmesi m\u00fcmk\u00fcnd\u00fcr.<\/p>\n Implementasyon s\u0131ras\u0131nda ilk ger\u00e7ekle\u015ftirecek oldu\u011fumuz k\u0131s\u0131m, yukar\u0131daki diyagram\u0131n sol taraf\u0131 olacakt\u0131r. Burada sonras\u0131nda olu\u015fturacak oldu\u011fumuz Provider’\u0131 yani API’\u0131 consume edecek bir Consumer yazaca\u011f\u0131z. Consumer i\u00e7erisinde API contract’lar\u0131na y\u00f6nelik request ve response’lar\u0131n Pact’leri \u00e7\u0131kart\u0131p, file system’da verify i\u015flemi i\u00e7in persist edece\u011fiz.<\/p>\n \u0130kinci k\u0131s\u0131mda olu\u015fturacak oldu\u011fumuz Provider, m\u00fc\u015fteri bilgilerini \u00e7eken bir API olsun. Bu API’\u0131n GET method’u “\/api\/customers\/1” URI’\u0131 ile, “1” numaral\u0131 id’ye sahip customer’\u0131 d\u00f6ns\u00fcn. \u00d6ncelikle ilk ad\u0131m olarak serialization i\u015flemlerinde kolayl\u0131k sa\u011flamas\u0131 a\u00e7\u0131s\u0131ndan, API’dan repsonse olarak d\u00f6n\u00fcyor olaca\u011f\u0131m\u0131z contract’\u0131 ekleyerek ba\u015flayal\u0131m. Bunun i\u00e7in “ConsumerDrivenContractsTestingSample” isminde yeni bir blank solution olu\u015fturup, i\u00e7erisine “Contracts” isminde bir class library ekleyelim.<\/p>\n Eklemi\u015f oldu\u011fumuz bu library i\u00e7erisinde, “Customer.cs” isminde yeni bir class ekleyelim ve a\u015fa\u011f\u0131daki gibi kodlayal\u0131m.<\/p>\n Contract k\u0131sm\u0131 bu kadar.<\/p>\n Diyagram\u0131n ilk k\u0131s\u0131mdaki Consumer taraf\u0131n\u0131 kodlamaya ba\u015flayabiliriz. Solution \u00fczerine structured g\u00f6r\u00fcnebilmesi a\u00e7\u0131s\u0131ndan “Service Consumer” isminde bir klas\u00f6r olu\u015fturup, i\u00e7erisine “CustomerApiServiceConsumer” isminde bir class library ekleyelim. Bu library i\u00e7erisinde, biraz \u00f6nce bahsetmi\u015f oldu\u011fum Customer API’\u0131 consume edebilmemizi sa\u011flayan client k\u0131sm\u0131n\u0131 kodlayaca\u011f\u0131z. Client’\u0131 olu\u015fturma i\u015flemine ba\u015flamadan \u00f6nce REST call’lar\u0131 s\u0131ras\u0131nda, kolayl\u0131k sa\u011flamas\u0131 a\u00e7\u0131s\u0131ndan Nuget Package Manager \u00fczerinden “RestSharp” paketini “CustomerApiServiceConsumer” library’sine kural\u0131m ve “Contracts” library’sini referans olarak da g\u00f6sterelim.<\/p>\n Kurulum i\u015fleminden sonra “CustomerApiClient.cs” isminde yeni bir class ekleyelim ve client’\u0131\u00a0a\u015fa\u011f\u0131daki gibi kodlayal\u0131m.<\/p>\n Olu\u015fturmu\u015f oldu\u011fumuz “CustomerApiClient” i\u00e7erisinde “RestSharp” \u0131n client’\u0131n\u0131 kullanarak, “\/api\/customers\/{id}” resource’una basic bir GET request’i\u00a0yap\u0131yoruz. Request sonucunda ise geriye “Customer” result’\u0131n\u0131 d\u00f6n\u00fcyoruz.<\/p>\n \u015eimdi s\u0131ra geldi test projesini olu\u015fturmaya. Olu\u015fturacak oldu\u011fumuz bu test projesi, servis’i kullanacak\u00a0olan service consumer’\u0131 temsil ediyor olacak ve burada “Customer API” a y\u00f6nelik Pact<\/strong>‘leri \u00e7\u0131kart\u0131p, test case’lerini yazaca\u011f\u0131z. Solution \u00fczerindeki “Service Consumer” klas\u00f6r\u00fcn\u00fcn i\u00e7erisine, “CustomerApiServiceConsumer.Tests” isminde yeni bir Unit Test projesi\u00a0olu\u015ftural\u0131m. Unit Test projesinin \u00fczerine, \u00f6ncelikle test i\u015flemlerinde baz\u0131 fonksiyonlar\u0131ndan yararlanabilmek i\u00e7in “xunit” test framework’\u00fcn\u00fc ve “xunit.runner.visualstudio” paketini, Nuget Package Manager \u00fczerinden kural\u0131m. Kurulum i\u015fleminin ard\u0131ndan makale giri\u015finde de bahsetmi\u015f oldu\u011fumuz, Consumer Driven Contracts Testing yazabilmemize olanak sa\u011flayan “PactNet” paketini de Nuget Package Manager \u00fczerinden kural\u0131m.\u00a0Nuget \u00fczerindeki kurulumlar\u0131n ard\u0131ndan, “Contracts” ve “CustomerApiServiceConsumer” library’lerini referans olarak ekleyelim.<\/p>\n Burada kodlamaya ilk olarak Customer API’\u0131n pact’ini olu\u015fturmak ile ba\u015flayaca\u011f\u0131z. Bu k\u0131s\u0131mlarda referans ald\u0131\u011f\u0131m yer ise, Pact framework’\u00fcn\u00fcn .net implementasyon\u00a0k\u0131sm\u0131n\u0131n bulundu\u011fu github adresidir. Makale sonunda sizlerle payla\u015f\u0131yor olaca\u011f\u0131m. Konumuza devam edecek olursak, “ConsumerCustomerApiPact.cs” isminde yeni bir class ekleyelim ve a\u015fa\u011f\u0131daki gibi kodlayal\u0131m.<\/p>\n “ConsumerCustomerApiPact” class’\u0131 i\u00e7erisinde bulunan “PactBuilder” ile, bir adet mock servis aya\u011fa kald\u0131r\u0131yoruz. Bu mock servis, “MockServerPort” property’si \u00fczerinden alm\u0131\u015f oldu\u011fu port bilgisi ile arka plan\u0131nda Nancy Self Hosting paketini kullanarak\u00a0olu\u015fmaktad\u0131r. Buradaki dikkat edilmesi gereken nokta ise “PactBuilder.ServiceConsumer()” method’unda servis’i consume edecek yerin neresi oldu\u011fu, “HasPactWith()” method’unda ise hangi provider ile pact’e sahip oldu\u011funu belirtiyoruz. Dispose method’u ile ger\u00e7ekle\u015ftirilen deferred execution\u00a0<\/strong>i\u015flemi ile bu pact’i kullanacak olan test case’inin, ilgili test senaryosunu ger\u00e7ekle\u015ftirmesinden sonra Customer API’a ait pact’leri olu\u015fturmas\u0131\u00a0sa\u011flanmaktad\u0131r.<\/p>\n \u015eimdi yine “CustomerApiServiceConsumer.Tests” projesi i\u00e7erisine, “CustomerApiConsumerTests.cs” isminde bir Unit Test class’\u0131 ekleyelim ve a\u015fa\u011f\u0131daki gibi kodlayal\u0131m.<\/p>\n “xunit” test paketi ile gelen “IClassFixture<T>” interface’inin i\u00e7erisine set etti\u011fimiz “ConsumerCustomerApiPact” class’\u0131n\u0131, herhangi bir test case’i execute olmadan \u00f6nce pact class’\u0131n\u0131 execute ediyor ve constructor \u00fczerinden pact’in instance’\u0131n\u0131 inject ediyor. “MockProviderService.ClearInteractions()” method’u ile de, \u00f6nceden kay\u0131t edilmi\u015f bir\u00a0interaction varsa, test run edilmeden \u00f6nce temizlemektedir.<\/p>\n \u015eimdi gelelim as\u0131l test case’ine. “GetCustomer_WhenTheCustomerIdGreaterThanZero_ReturnCustomer” ismindeki test case’i ile isminden de anla\u015f\u0131labilece\u011fi gibi, customer id’si s\u0131f\u0131rdan b\u00fcy\u00fck ise ilgili customer’\u0131 getirmesini istiyoruz. Buradaki i\u015flemleri fluent bir \u015fekilde “ConsumerCustomerApiPact” i\u00e7erisinden gelen “IMockProviderService” ile ger\u00e7ekle\u015ftiriyoruz. Burada yer alan “Given()” ve “UponReceiving()” fluent method’lar\u0131 ile, pact’in readability a\u00e7\u0131s\u0131ndan anla\u015f\u0131l\u0131r\u00a0olabilmesi i\u00e7in ne al\u0131naca\u011f\u0131n\u0131 ve ne al\u0131nd\u0131\u011f\u0131 gibi bilgileri giriyoruz.”With()” ve “WillRespondWith” fluent method’lar\u0131 ile ise, provider’a nas\u0131l bir request ge\u00e7ece\u011fimizi ve bunun sonucunda nas\u0131l bir response elde edece\u011fimizi tan\u0131ml\u0131yoruz. Dikkat ederseniz bu noktada asl\u0131nda bir nevi provider’\u0131n endpoint dok\u00fcmantasyonunu da olu\u015fturuyor gibiyiz. Asl\u0131nda gibiyiz de de\u011fil, olu\u015fturuyoruz her bir endpoint i\u00e7in. :)<\/p>\n Sonras\u0131nda ise art\u0131k, \u00f6ncesinde olu\u015fturmu\u015f oldu\u011fumuz client’\u0131 kullanarak, “_mockProviderServiceBaseUri”\u00a0ile mock servis \u00fczerinden “consumer.Get(1);” method’unu \u00e7a\u011f\u0131r\u0131yoruz. Bu i\u015flemin sonucunda e\u011fer result null de\u011filse, pact’i olu\u015fturabilmesi i\u00e7in interaction’\u0131 verify ederek, mock provider \u00fczerinde tekrardan kay\u0131tl\u0131 hale getiriyoruz.<\/p>\n Test Explorer \u00fczerinden “GetCustomer_WhenTheCustomerIdGreaterThanZero_ReturnCustomer” method’unu \u00e7al\u0131\u015ft\u0131ral\u0131m ve sorunsuz bir \u015fekilde implementasyonu ger\u00e7ekle\u015ftirdi isek, test’in ba\u015far\u0131l\u0131 bir \u015fekilde ge\u00e7ti\u011fini g\u00f6rebilece\u011fiz.<\/p>\n Yukar\u0131daki resimde g\u00f6r\u00fcld\u00fc\u011f\u00fc gibi test’i \u00e7al\u0131\u015ft\u0131rd\u0131\u011f\u0131mda ba\u015far\u0131l\u0131 bir \u015fekilde test i\u015flemi ger\u00e7ekle\u015fti. \u015eimdi as\u0131l bu i\u015flemin sonucunda hat\u0131rlarsak “ConsumerCustomerApiPact” olu\u015ftururken Dispose k\u0131sm\u0131nda\u00a0ger\u00e7ekle\u015ftirilen\u00a0deferred execution ile “MockProviderService” \u00fczerine register edilmi\u015f request ve beklenen response senaryolar\u0131 buradan”Build()” method’u ile tetikleniyordu. Bu i\u015flem pact file’\u0131n\u0131n “\\CustomerApiServiceConsumer.Tests\\pacts<\/em>” dizini alt\u0131nda a\u015fa\u011f\u0131daki gibi olu\u015fmas\u0131n\u0131 sa\u011flam\u0131\u015ft\u0131r.<\/p>\n Pact dosyas\u0131 ne kadar da okunabilir de\u011fil mi? Art\u0131k Provider k\u0131sm\u0131n\u0131 haz\u0131rlamaya ba\u015flayabiliriz.<\/p>\n Art\u0131k bu k\u0131s\u0131mda Provider \u00fczerinden Consumer’\u0131n olu\u015fturmu\u015f oldu\u011fu pact’leri alarak, test API server’\u0131 \u00fczerinden pact’ler do\u011frultusunda verify i\u015flemini ger\u00e7ekle\u015ftirece\u011fiz. Solution \u00fczerine “Service Provider” isminde yeni bir klas\u00f6r daha ekleyerek, i\u00e7erisine “CustomerApi.Host” isminde bir console application projesi olu\u015ftural\u0131m. Projeyi olu\u015fturduktan sonra Nuget Package Manager \u00fczerinden “Microsoft.AspNet.WebApi.OwinSelfHost” paketini kural\u0131m.<\/p>\n Kurulum i\u015flemlerinin ard\u0131ndan API’\u0131 owin ile host edebilmek i\u00e7in “Startup.cs” isminde yeni bir class ekleyelim ve a\u015fa\u011f\u0131daki gibi kodlayal\u0131m.<\/p>\n Startup class’\u0131 ile, owin \u00fczerinden API’\u0131n host i\u015flemini ger\u00e7ekle\u015ftirece\u011fiz. Host i\u015flemi i\u00e7in “Program.cs” class’\u0131n\u0131 a\u015fa\u011f\u0131daki gibi g\u00fcncelleyelim.<\/p>\n “Microsoft.Owin.Hosting” namespace’i alt\u0131nda bulunan “WebApp” ile API’\u0131, localhost \u00fczerinden “8090” portu \u00fczerinden host edece\u011fiz. \u015eimdi s\u0131ra geldi controller’\u0131 eklemeye. Bunun i\u00e7in “Controllers” isminde yeni bir klas\u00f6r olu\u015fturup, “CustomerController.cs” class’\u0131n\u0131 i\u00e7erisine ekleyelim ve a\u015fa\u011f\u0131daki gibi kodlayal\u0131m.<\/p>\n Makale giri\u015finde de bahsetti\u011fimiz gibi art\u0131k “api\/customers\/{id}<\/em>” URI’\u0131 ile, “0” dan b\u00fcy\u00fck bir id de\u011feri geldi\u011finde geriye “G\u00f6khan G\u00f6kalp” kullan\u0131c\u0131s\u0131n\u0131 d\u00f6necektir.<\/p>\n Test edebilmek i\u00e7in “CustomerApi.Host” projesini \u00e7al\u0131\u015ft\u0131ral\u0131m ve “http:\/\/localhost:8090\/api\/customers\/1<\/em>” URI’\u0131na bir GET request’inde bulunal\u0131m.<\/p>\n Yukar\u0131daki resimde oldu\u011fu gibi “1” numaral\u0131 id’ye sahip “G\u00f6khan G\u00f6kalp” kullan\u0131c\u0131s\u0131n\u0131n, response olarak geldi\u011fini g\u00f6r\u00fcyoruz.<\/p>\n \u015eimdi “CustomerApi.Host” projesi i\u00e7in bir Unit Test projesi olu\u015fturaca\u011f\u0131z ve burada consumer’\u0131n olu\u015fturmu\u015f oldu\u011fu pact’lerin verify i\u015flemlerini ger\u00e7ekle\u015ftirece\u011fiz. “Service Provider” klas\u00f6r\u00fc i\u00e7erisine “CustomerApi.Tests” isminde yeni bir Unit Test projesi olu\u015ftural\u0131m ve projenin olu\u015fturma i\u015fleminin ard\u0131ndan Nuget Package Manager \u00fczerinden “xunit”, “xunit.runner.visualstudio” “PactNet” ve “Microsoft.Owin.Testing” paketlerini kural\u0131m. Paketlerin kurulum i\u015fleminin tamamlanmas\u0131ndan sonra “CustomerApi.Host” projesini de referans olarak ekleyelim.<\/p>\n \u0130htiya\u00e7 duydu\u011fumuz paketler haz\u0131r oldu\u011funa g\u00f6re “CustomerTests.cs” isminde bir Unit Test class’\u0131 ekleyelim ve a\u015fa\u011f\u0131daki gibi kodlayal\u0131m.<\/p>\n Burada olu\u015fturmu\u015f oldu\u011fumuz “EnsureCustomerApiHonoursPactWithConsumer” method’unun i\u00e7erisinde bir “PactVerifier” tan\u0131ml\u0131yoruz. Sonras\u0131nda ise verifier \u00fczerinden provider’\u0131n state’ini, “ServiceProvider()” fluent method’u ile hangi provider oldu\u011funu ve Owin TestServer’\u0131 \u00fczerinden gelen http client’\u0131n\u0131 parameter olarak set ediyoruz. “HonoursPactWith()” fluent method’u ile pact’i olu\u015fturan consumer’\u0131n name’ini ve “PactUri()” fluent method’u ile de olu\u015fturulmu\u015f olan pact’in URI adresini parametre olarak set ediyoruz.<\/p>\n T\u00fcm parametrelerin set edilmesinden sonra “Verify()” method’unu \u00e7a\u011f\u0131rarak, provider’\u0131n mock test server’\u0131 \u00fczerinden consumer taraf\u0131ndan olu\u015fturulmu\u015f olan pact’lerin, verify i\u015fleminin ger\u00e7ekle\u015ftirilmesini sa\u011flam\u0131\u015f oluyoruz. T\u00fcm implementasyonumuz tamamlanm\u0131\u015f durumda. Hat\u0131rlarsak consumer taraf\u0131n\u0131 implemente ederken, test etmek ama\u00e7l\u0131 Unit Test case’ini \u00e7al\u0131\u015ft\u0131rm\u0131\u015ft\u0131k ve ba\u015far\u0131l\u0131 bir \u015fekilde pact file’\u0131 olu\u015fmu\u015ftu. \u015eimdi ise verify i\u015flemini deneyebilmek i\u00e7in gelin “EnsureCustomerApiHonoursPactWithConsumer” test case’ini \u00e7al\u0131\u015ft\u0131ral\u0131m ve sonucuna bir bakal\u0131m.<\/p>\n Evet bu test case’i de ba\u015far\u0131l\u0131 bir \u015fekilde sonu\u00e7land\u0131.<\/p>\n Bu demek oluyor ki pact \u00fczerinde consumer’\u0131n provider’dan beklemi\u015f oldu\u011fu request ve response modelleri, mock test server’\u0131 \u00fczerinden \u00e7al\u0131\u015ft\u0131r\u0131larak ba\u015far\u0131l\u0131 bir \u015fekilde verify edildi. \u015eimdi gelelim ger\u00e7ek hayatta kar\u015f\u0131la\u015fabilece\u011fimiz bir problemi test etmeye. Diyelim ki Customer API m\u00fc\u015fteri detaylar\u0131n\u0131 art\u0131k “\/api\/customers\/1” \u015feklinde de\u011fil de, “\/api\/customers\/1\/detail” \u015feklinde veriyor olarak g\u00fcncellensin. Bunun i\u00e7in hemen ilgili controller’\u0131 a\u00e7arak a\u015fa\u011f\u0131daki gibi route’u g\u00fcncelleyelim.<\/p>\n Controller’\u0131 g\u00fcncelleme i\u015fleminden sonra solution’\u0131 derleyelim ve tekrardan “EnsureCustomerApiHonoursPactWithConsumer” test case’ini \u00e7al\u0131\u015ft\u0131ral\u0131m.<\/p>\n\u00d6rne\u011fin:<\/h4>\n
\n
Consumer Driven Contracts Testing Nas\u0131l \u00c7al\u0131\u015f\u0131r?<\/h4>\n
\n
Pact Framework’\u00fcn\u00fcn Baz\u0131 Avantajlar\u0131<\/h4>\n
\n
Pact Framework’\u00fcn\u00fcn Implementasyonu<\/h4>\n
1) Consumer ve Pact’lerinin Olu\u015fturulmas\u0131<\/h5>\n
![\"define-consumer-expectations\"](\"\/wp-content\/uploads\/2017\/01\/define-consumer-expectations.jpg\")
<\/a><\/p>\nnamespace Contracts\r\n{\r\n public class Customer\r\n {\r\n public int Id { get; set; }\r\n public string FullName { get; set; }\r\n }\r\n}<\/pre>\nusing Contracts;\r\nusing RestSharp;\r\n\r\nnamespace CustomerApiServiceConsumer\r\n{\r\n public class CustomerApiClient\r\n {\r\n private readonly RestClient _restClient;\r\n\r\n public CustomerApiClient(string baseUri)\r\n {\r\n _restClient = new RestClient(baseUri);\r\n }\r\n\r\n public Customer Get(int id)\r\n {\r\n var request = new RestRequest($\"\/api\/customers\/{id}\", Method.GET) {RequestFormat = DataFormat.Json};\r\n request.AddHeader(\"Accept\", \"application\/json\");\r\n\r\n var result = _restClient.Execute<Customer>(request);\r\n\r\n return result.Data;\r\n }\r\n }\r\n}<\/pre>\nusing System;\r\nusing PactNet;\r\nusing PactNet.Mocks.MockHttpService;\r\n\r\nnamespace CustomerApiServiceConsumer.Tests\r\n{\r\n public class ConsumerCustomerApiPact : IDisposable\r\n {\r\n public IPactBuilder PactBuilder { get; private set; }\r\n public IMockProviderService MockProviderService { get; private set; }\r\n\r\n public int MockServerPort => 1234;\r\n public string MockProviderServiceBaseUri => $\"http:\/\/localhost:{MockServerPort}\";\r\n\r\n public ConsumerCustomerApiPact()\r\n {\r\n PactBuilder = new PactBuilder();\r\n PactBuilder.ServiceConsumer(\"CustomerApiServiceConsumer\").HasPactWith(\"CustomerApi.Host\");\r\n\r\n MockProviderService = PactBuilder.MockService(MockServerPort);\r\n }\r\n\r\n public void Dispose()\r\n {\r\n PactBuilder.Build();\r\n }\r\n }\r\n}<\/pre>\nusing System.Collections.Generic;\r\nusing Contracts;\r\nusing PactNet.Mocks.MockHttpService;\r\nusing PactNet.Mocks.MockHttpService.Models;\r\nusing Xunit;\r\n\r\nnamespace CustomerApiServiceConsumer.Tests\r\n{\r\n public class CustomerApiConsumerTests : IClassFixture<ConsumerCustomerApiPact>\r\n {\r\n private readonly IMockProviderService _mockProviderService;\r\n private readonly string _mockProviderServiceBaseUri;\r\n\r\n public CustomerApiConsumerTests(ConsumerCustomerApiPact data)\r\n {\r\n _mockProviderService = data.MockProviderService;\r\n _mockProviderServiceBaseUri = data.MockProviderServiceBaseUri;\r\n\r\n data.MockProviderService.ClearInteractions();\r\n }\r\n\r\n [Fact]\r\n public void GetCustomer_WhenTheCustomerIdGreaterThanZero_ReturnCustomer()\r\n {\r\n \/\/Arrange\r\n int customerId = 1;\r\n\r\n _mockProviderService\r\n .Given(\"There is a customer with id 1\")\r\n .UponReceiving(\"A GET request to retrieve the customer\")\r\n .With(new ProviderServiceRequest\r\n {\r\n Method = HttpVerb.Get,\r\n Path = \"\/api\/customers\/\" + customerId,\r\n Headers = new Dictionary<string, string>\r\n {\r\n {\"Accept\", \"application\/json\"}\r\n }\r\n })\r\n .WillRespondWith(new ProviderServiceResponse\r\n {\r\n Status = 200,\r\n Headers = new Dictionary<string, string>\r\n {\r\n {\"Content-Type\", \"application\/json; charset=utf-8\"}\r\n },\r\n Body = new Customer\r\n {\r\n Id = 1,\r\n FullName = \"G\u00f6khan G\u00f6kalp\"\r\n }\r\n });\r\n\r\n var consumer = new CustomerApiClient(_mockProviderServiceBaseUri);\r\n\r\n \/\/Act\r\n var result = consumer.Get(1);\r\n\r\n \/\/Assert\r\n Assert.NotNull(result);\r\n\r\n _mockProviderService.VerifyInteractions();\r\n }\r\n }\r\n}<\/pre>\n![\"test-explorer\"](\"\/wp-content\/uploads\/2017\/01\/test-explorer.jpg\")
<\/a><\/p>\n{\r\n \"provider\": {\r\n \"name\": \"CustomerApi.Host\"\r\n },\r\n \"consumer\": {\r\n \"name\": \"CustomerApiServiceConsumer\"\r\n },\r\n \"interactions\": [\r\n {\r\n \"description\": \"A GET request to retrieve the customer\",\r\n \"provider_state\": \"There is a customer with id 1\",\r\n \"request\": {\r\n \"method\": \"get\",\r\n \"path\": \"\/api\/customers\/1\",\r\n \"headers\": {\r\n \"Accept\": \"application\/json\"\r\n }\r\n },\r\n \"response\": {\r\n \"status\": 200,\r\n \"headers\": {\r\n \"Content-Type\": \"application\/json; charset=utf-8\"\r\n },\r\n \"body\": {\r\n \"Id\": 1,\r\n \"FullName\": \"G\u00f6khan G\u00f6kalp\"\r\n }\r\n }\r\n }\r\n ],\r\n \"metadata\": {\r\n \"pactSpecificationVersion\": \"1.1.0\"\r\n }\r\n}<\/pre>\n2) Provider’\u0131n Olu\u015fturulmas\u0131 ve\u00a0Verification<\/h5>\n
![\"verify-expectations-on-provider\"](\"\/wp-content\/uploads\/2017\/01\/verify-expectations-on-provider.png\")
<\/a><\/p>\nusing System.Web.Http;\r\nusing Owin;\r\n\r\nnamespace CustomerApi.Host\r\n{\r\n public class Startup\r\n {\r\n public void Configuration(IAppBuilder app)\r\n {\r\n \/\/ Configure Web API for self-host. \r\n var config = new HttpConfiguration();\r\n\r\n config.MapHttpAttributeRoutes();\r\n\r\n config.Routes.MapHttpRoute(\r\n name: \"DefaultApi\",\r\n routeTemplate: \"api\/{controller}\/{id}\",\r\n defaults: new { id = RouteParameter.Optional }\r\n );\r\n\r\n app.UseWebApi(config);\r\n }\r\n }\r\n}<\/pre>\nusing System;\r\nusing Microsoft.Owin.Hosting;\r\n\r\nnamespace CustomerApi.Host\r\n{\r\n class Program\r\n {\r\n static void Main(string[] args)\r\n {\r\n using (WebApp.Start<Startup>(\"http:\/\/localhost:8090\"))\r\n {\r\n Console.WriteLine(\"Web Server is running.\");\r\n Console.WriteLine(\"Press any key to quit.\");\r\n Console.ReadLine();\r\n }\r\n }\r\n }\r\n}<\/pre>\nusing System.Web.Http;\r\nusing Contracts;\r\n\r\nnamespace CustomerApi.Host.Controllers\r\n{\r\n [RoutePrefix(\"api\/customers\")]\r\n public class CustomerController : ApiController\r\n {\r\n [HttpGet, Route(\"{id}\")]\r\n public Customer Get(int id)\r\n {\r\n if (id > 0)\r\n {\r\n return new Customer\r\n {\r\n Id = 1,\r\n FullName = \"G\u00f6khan G\u00f6kalp\"\r\n };\r\n }\r\n\r\n return null;\r\n }\r\n }\r\n}<\/pre>\n![\"customer-response\"](\"\/wp-content\/uploads\/2017\/01\/customer-response.jpg\")
<\/a><\/p>\nusing CustomerApi.Host;\r\nusing Microsoft.Owin.Testing;\r\nusing PactNet;\r\nusing Xunit;\r\n\r\nnamespace CustomerApi.Tests\r\n{\r\n public class CustomerTests\r\n {\r\n [Fact]\r\n public void EnsureCustomerApiHonoursPactWithConsumer()\r\n {\r\n \/\/Arrange\r\n IPactVerifier pactVerifier = new PactVerifier(() => { }, () => { });\r\n\r\n pactVerifier\r\n .ProviderState(\"There is a customer with id 1\");\r\n\r\n \/\/Act \/ Assert\r\n using (var testServer = TestServer.Create<Startup>())\r\n {\r\n pactVerifier\r\n .ServiceProvider(\"CustomerApi.Host\", testServer.HttpClient)\r\n .HonoursPactWith(\"CustomerApiServiceConsumer\")\r\n .PactUri(\"..\/..\/..\/CustomerApiServiceConsumer.Tests\/pacts\/customerapiserviceconsumer-customerapi.host.json\")\r\n .Verify();\r\n }\r\n }\r\n }\r\n}<\/pre>\n![\"verify-test\"](\"\/wp-content\/uploads\/2017\/01\/verify-test.jpg\")
<\/a><\/p>\nusing System.Web.Http;\r\nusing Contracts;\r\n\r\nnamespace CustomerApi.Host.Controllers\r\n{\r\n [RoutePrefix(\"api\/customers\")]\r\n public class CustomerController : ApiController\r\n {\r\n [HttpGet, Route(\"{id}\/detail\")]\r\n public Customer Get(int id)\r\n {\r\n if (id > 0)\r\n {\r\n return new Customer\r\n {\r\n Id = 1,\r\n FullName = \"G\u00f6khan G\u00f6kalp\"\r\n };\r\n }\r\n\r\n return null;\r\n }\r\n }\r\n}<\/pre>\n
![\"verify-test-fail\"](\"\/wp-content\/uploads\/2017\/01\/verify-test-fail.jpg\")
<\/a><\/p>\n