{"id":45719,"date":"2026-11-16T09:11:09","date_gmt":"2026-11-16T06:11:09","guid":{"rendered":"https:\/\/fatihsoysal.com\/blog\/tedarikci-apisini-mocklarken-cii-kurtarmak-ve-mockun-bize-yalan-soylemesi-aci-bir-ders\/"},"modified":"2026-11-16T09:11:46","modified_gmt":"2026-11-16T06:11:46","slug":"tedarikci-apisini-mocklarken-cii-kurtarmak-ve-mockun-bize-yalan-soylemesi-aci-bir-ders","status":"publish","type":"post","link":"https:\/\/fatihsoysal.com\/blog\/tedarikci-apisini-mocklarken-cii-kurtarmak-ve-mockun-bize-yalan-soylemesi-aci-bir-ders\/","title":{"rendered":"Tedarik\u00e7i API&#8217;s\u0131n\u0131 Mock&#8217;larken CI&#8217;\u0131 Kurtarmak ve Mock&#8217;un Bize Yalan S\u00f6ylemesi: Ac\u0131 Bir Ders"},"content":{"rendered":"<h2>Tedarik\u00e7i API&#8217;s\u0131n\u0131 Mock&#8217;larken CI&#8217;\u0131 Kurtarmak ve Mock&#8217;un Bize Yalan S\u00f6ylemesi: Ac\u0131 Bir Ders<\/h2>\n<p>Yaz\u0131l\u0131m geli\u015ftirme s\u00fcre\u00e7lerinde harici ba\u011f\u0131ml\u0131l\u0131klar, \u00f6zellikle de \u00fc\u00e7\u00fcnc\u00fc taraf API&#8217;lar\u0131, s\u00fcrekli entegrasyon (CI) ve s\u00fcrekli teslimat (CD) boru hatlar\u0131m\u0131z i\u00e7in ciddi bir engel te\u015fkil edebilir. Bu t\u00fcr ba\u011f\u0131ml\u0131l\u0131klar\u0131 y\u00f6netmek, test s\u00fcre\u00e7lerimizi h\u0131zland\u0131rmak ve maliyetleri d\u00fc\u015f\u00fcrmek amac\u0131yla API mock&#8217;lama (sahte API olu\u015fturma) yayg\u0131n bir pratik haline gelmi\u015ftir. Ancak, bu pratik bazen beklenmedik ve can s\u0131k\u0131c\u0131 sonu\u00e7lar do\u011furabilir: Mock&#8217;lar bize &#8220;yalan s\u00f6yledi\u011finde&#8221; ne olur? Bu makalede, bir tedarik\u00e7i API&#8217;s\u0131n\u0131 mock&#8217;larken CI&#8217;\u0131 kurtarma \u00e7abalar\u0131m\u0131z\u0131n, mock&#8217;un do\u011frulu\u011funu yitirmesiyle nas\u0131l bir kabusa d\u00f6n\u00fc\u015ft\u00fc\u011f\u00fcn\u00fc ve bu durumdan \u00e7\u0131kar\u0131lacak dersleri ele alaca\u011f\u0131z.<\/p>\n<h2>Neden API Mock&#8217;lama \u0130htiyac\u0131 Duyar\u0131z? Temel Kavramlar Nelerdir?<\/h2>\n<p>Modern yaz\u0131l\u0131m mimarileri genellikle mikroservisler ve harici hizmet entegrasyonlar\u0131 \u00fczerine kuruludur. Bir uygulaman\u0131n \u00f6deme sistemleri, SMS bildirimleri, harita servisleri veya kimlik do\u011frulama gibi fonksiyonlar\u0131 i\u00e7in \u00fc\u00e7\u00fcnc\u00fc taraf API&#8217;lar\u0131na ba\u011f\u0131ml\u0131 olmas\u0131 olduk\u00e7a yayg\u0131nd\u0131r. Bu ba\u011f\u0131ml\u0131l\u0131klar, geli\u015ftirme ve test s\u00fcre\u00e7lerinde \u00e7e\u015fitli zorluklar yarat\u0131r:<\/p>\n<ul>\n<li><strong>Eri\u015fim K\u0131s\u0131tlamalar\u0131 ve Maliyetler:<\/strong> Baz\u0131 API&#8217;lar test ortam\u0131 sa\u011flamayabilir veya her istek i\u00e7in \u00fccret talep edebilir. Geli\u015ftirme a\u015famas\u0131nda binlerce test iste\u011fi g\u00f6ndermek hem maliyetli hem de pratik de\u011fildir.<\/li>\n<li><strong>Performans ve H\u0131z:<\/strong> Harici API \u00e7a\u011fr\u0131lar\u0131 genellikle a\u011f gecikmeleri nedeniyle yava\u015ft\u0131r. Her test \u00e7al\u0131\u015ft\u0131\u011f\u0131nda ger\u00e7ek API&#8217;lar\u0131 \u00e7a\u011f\u0131rmak, CI\/CD boru hatt\u0131n\u0131n s\u00fcresini uzat\u0131r ve geli\u015ftirici verimlili\u011fini d\u00fc\u015f\u00fcr\u00fcr.<\/li>\n<li><strong>G\u00fcvenilirlik ve Tutarl\u0131l\u0131k:<\/strong> \u00dc\u00e7\u00fcnc\u00fc taraf API&#8217;lar\u0131 bazen eri\u015filemez olabilir, yan\u0131t s\u00fcreleri dalgalanabilir veya beklenmedik hatalar d\u00f6nebilir. Bu durum, testlerin tutars\u0131z sonu\u00e7lar vermesine (flaky tests) yol a\u00e7ar ve geli\u015ftiricilerin kendi kodlar\u0131ndaki hatalarla d\u0131\u015f ba\u011f\u0131ml\u0131l\u0131k sorunlar\u0131n\u0131 ay\u0131rt etmesini zorla\u015ft\u0131r\u0131r.<\/li>\n<li><strong>Geli\u015ftirme \u00d6nceli\u011fi:<\/strong> Entegre olunacak harici API hen\u00fcz geli\u015ftirme a\u015famas\u0131nda olabilir veya bizim entegrasyonumuzdan daha yava\u015f ilerleyebilir. Bu durumda, kendi geli\u015ftirmemizi engellememek i\u00e7in mock&#8217;lar kritik rol oynar.<\/li>\n<\/ul>\n<p>\u0130\u015fte bu noktada API mock&#8217;lama devreye girer. Mock&#8217;lama, bir servisin veya bile\u015fenin davran\u0131\u015f\u0131n\u0131 taklit eden sahte bir nesne veya hizmet olu\u015fturma i\u015flemidir. Temel olarak, ger\u00e7ek ba\u011f\u0131ml\u0131l\u0131\u011f\u0131n yerini alarak, uygulaman\u0131z\u0131n onunla etkile\u015fimini sim\u00fcle eder. Bu sayede, uygulaman\u0131z\u0131 ger\u00e7ek d\u0131\u015f ba\u011f\u0131ml\u0131l\u0131\u011fa ihtiya\u00e7 duymadan test edebilirsiniz. Mock&#8217;lar genellikle belirli senaryolar i\u00e7in \u00f6nceden tan\u0131mlanm\u0131\u015f yan\u0131tlar (response) d\u00f6nd\u00fcr\u00fcrler. \u00d6rne\u011fin, bir \u00f6deme API&#8217;s\u0131n\u0131n ba\u015far\u0131l\u0131 bir \u00f6deme yan\u0131t\u0131 veya ba\u015far\u0131s\u0131z bir \u00f6deme yan\u0131t\u0131 gibi senaryolar\u0131 mock edilebilir.<\/p>\n<p>Mock, Stub ve Fake terimleri s\u0131kl\u0131kla birbirinin yerine kullan\u0131lsa da, teknik olarak farkl\u0131l\u0131klar g\u00f6sterirler:<\/p>\n<ul>\n<li><strong>Stub (Sahte Nesne):<\/strong> Test s\u0131ras\u0131nda belirli bir senaryo i\u00e7in \u00f6nceden tan\u0131mlanm\u0131\u015f sabit yan\u0131tlar d\u00f6ner. Genellikle testin durumunu etkilemez, sadece gerekli veriyi sa\u011flar.<\/li>\n<li><strong>Mock (Taklit Nesne):<\/strong> Stub&#8217;dan daha fazlas\u0131d\u0131r. Sadece yan\u0131t d\u00f6nd\u00fcrmekle kalmaz, ayn\u0131 zamanda gelen \u00e7a\u011fr\u0131lar\u0131 da kaydeder ve testin sonunda bu \u00e7a\u011fr\u0131lar\u0131n do\u011fru parametrelerle yap\u0131l\u0131p yap\u0131lmad\u0131\u011f\u0131n\u0131 do\u011frulamak i\u00e7in kullan\u0131l\u0131r. Testin davran\u0131\u015f\u0131n\u0131 do\u011frulamaya odaklan\u0131r.<\/li>\n<li><strong>Fake (Sahte Uygulama):<\/strong> Ger\u00e7ek uygulaman\u0131n basitle\u015ftirilmi\u015f bir versiyonudur. \u00d6rne\u011fin, bir veritaban\u0131 yerine bellek i\u00e7i bir veritaban\u0131 kullanmak bir fake \u00f6rne\u011fidir. Daha karma\u015f\u0131k davran\u0131\u015flar\u0131 taklit edebilir.<\/li>\n<\/ul>\n<p>Bu makalede &#8220;mock&#8221; terimini, genellikle API davran\u0131\u015f\u0131n\u0131 taklit eden ve hem yan\u0131t sa\u011flayan hem de \u00e7a\u011fr\u0131lar\u0131 do\u011frulayabilen genel bir sahte hizmet anlam\u0131nda kullanaca\u011f\u0131z. Mock&#8217;lama sayesinde, geli\u015ftiriciler h\u0131zl\u0131 geri bildirim alabilir, test ortamlar\u0131n\u0131n kararl\u0131l\u0131\u011f\u0131n\u0131 art\u0131rabilir ve d\u0131\u015f ba\u011f\u0131ml\u0131l\u0131klar\u0131n olu\u015fturdu\u011fu darbo\u011fazlar\u0131 ortadan kald\u0131rabilirler. Ancak bu avantajlar, mock&#8217;lar\u0131n do\u011frulu\u011funa ba\u011fl\u0131d\u0131r. Aksi takdirde, &#8220;yalan s\u00f6yleyen&#8221; bir mock, CI s\u00fcrecimizi kurtarmak yerine daha b\u00fcy\u00fck sorunlara yol a\u00e7abilir.<\/p>\n<h2>Mock&#8217;un &#8220;Yalan S\u00f6ylemesi&#8221; Ne Demektir ve CI&#8217;\u0131 Nas\u0131l Etkiler?<\/h2>\n<p>Bir mock&#8217;un &#8220;yalan s\u00f6ylemesi&#8221; durumu, temel olarak mock&#8217;un sim\u00fcle etti\u011fi ger\u00e7ek API&#8217;n\u0131n davran\u0131\u015f\u0131n\u0131 do\u011fru bir \u015fekilde yans\u0131tmamas\u0131 anlam\u0131na gelir. Bu, \u00e7e\u015fitli \u015fekillerde ortaya \u00e7\u0131kabilir ve genellikle fark edilmesi zor, sinsi hatalara yol a\u00e7ar. Bir mock&#8217;un yalan s\u00f6ylemesinin ba\u015fl\u0131ca nedenleri ve bunun CI\/CD \u00fczerindeki etkileri \u015funlard\u0131r:<\/p>\n<ol>\n<li><strong>G\u00fcncel Olmayan Veriler veya Yap\u0131:<\/strong> En s\u0131k kar\u015f\u0131la\u015f\u0131lan senaryo budur. Ger\u00e7ek API zamanla de\u011fi\u015febilir: yeni alanlar eklenebilir, mevcut alanlar\u0131n veri tipleri de\u011fi\u015febilir, baz\u0131 alanlar kald\u0131r\u0131labilir, hata kodlar\u0131 g\u00fcncellenebilir veya yan\u0131t yap\u0131lar\u0131 tamamen farkl\u0131la\u015fabilir. E\u011fer mock&#8217;umuz bu de\u011fi\u015fikliklere ayak uyduramazsa, eski veya yanl\u0131\u015f verilerle test yapmaya devam ederiz.<\/li>\n<li><strong>Eksik Senaryolar:<\/strong> Mock&#8217;lar genellikle sadece en yayg\u0131n veya &#8220;mutlu yol&#8221; (happy path) senaryolar\u0131n\u0131 kapsar. Kenar durumlar (edge cases), hata durumlar\u0131 (\u00f6rne\u011fin, a\u011f kesintisi, ge\u00e7ersiz kimlik bilgisi, yetkilendirme hatas\u0131) veya performans sorunlar\u0131 gibi kritik senaryolar genellikle mock edilmez. Bu durumda, CI&#8217;\u0131m\u0131z bu eksiklikleri g\u00f6zden ka\u00e7\u0131r\u0131r ve ger\u00e7ek d\u00fcnyada kar\u015f\u0131la\u015f\u0131lacak potansiyel hatalara kar\u015f\u0131 bizi koruyamaz.<\/li>\n<li><strong>Yanl\u0131\u015f Davran\u0131\u015f Sim\u00fclasyonu:<\/strong> Bir mock, sadece veri yap\u0131s\u0131n\u0131 de\u011fil, ayn\u0131 zamanda API&#8217;n\u0131n davran\u0131\u015f\u0131n\u0131 da taklit etmelidir. \u00d6rne\u011fin, belirli bir giri\u015fe kar\u015f\u0131l\u0131k gelen belirli bir hata kodu veya bir durum de\u011fi\u015fikli\u011finin (state change) nas\u0131l y\u00f6netildi\u011fi. E\u011fer mock bu davran\u0131\u015fsal incelikleri do\u011fru bir \u015fekilde yans\u0131tmazsa, uygulaman\u0131z ger\u00e7ek API ile farkl\u0131, mock ile farkl\u0131 davran\u0131r.<\/li>\n<li><strong>A\u015f\u0131r\u0131 Basitle\u015ftirme:<\/strong> Geli\u015ftiriciler, testleri h\u0131zl\u0131ca ge\u00e7irmek ad\u0131na mock&#8217;lar\u0131 a\u015f\u0131r\u0131 basitle\u015ftirebilirler. \u00d6rne\u011fin, ger\u00e7ek API&#8217;n\u0131n karma\u015f\u0131k bir do\u011frulama mant\u0131\u011f\u0131 varsa, mock bu mant\u0131\u011f\u0131 tamamen atlayabilir ve her zaman ba\u015far\u0131l\u0131 bir yan\u0131t d\u00f6nebilir. Bu, yan\u0131lt\u0131c\u0131 bir &#8220;her \u015fey yolunda&#8221; hissi yarat\u0131r.<\/li>\n<\/ol>\n<p>Peki, yalan s\u00f6yleyen bir mock&#8217;un CI\/CD boru hatt\u0131 \u00fczerindeki etkileri nelerdir?<\/p>\n<ul>\n<li><strong>Yanl\u0131\u015f Pozitifler (False Positives):<\/strong> En tehlikeli etkilerden biridir. CI boru hatt\u0131 ye\u015fil yanar, t\u00fcm testler ba\u015far\u0131l\u0131 g\u00f6r\u00fcn\u00fcr, ancak bu ba\u015far\u0131 yan\u0131lt\u0131c\u0131d\u0131r. Uygulama, mock&#8217;a kar\u015f\u0131 do\u011fru \u00e7al\u0131\u015f\u0131rken, ger\u00e7ek API&#8217;ya kar\u015f\u0131 \u00e7al\u0131\u015fmayabilir. Bu, geli\u015ftiricilere yanl\u0131\u015f bir g\u00fcvenlik hissi verir.<\/li>\n<li><strong>\u00dcretim Ortam\u0131nda Hatalar:<\/strong> Yanl\u0131\u015f pozitifler nedeniyle, hatal\u0131 kod par\u00e7ac\u0131klar\u0131 \u00fcretim ortam\u0131na kadar ula\u015fabilir. Bu, ger\u00e7ek kullan\u0131c\u0131lar i\u00e7in kesintilere, veri kay\u0131plar\u0131na veya kritik i\u015f s\u00fcre\u00e7lerinin aksamas\u0131na yol a\u00e7abilir. \u00dcretim ortam\u0131nda hata ay\u0131klamak hem maliyetli hem de streslidir.<\/li>\n<li><strong>Geli\u015ftirici G\u00fcveninin Kayb\u0131:<\/strong> CI\/CD boru hatt\u0131na ve testlere olan g\u00fcven azal\u0131r. Geli\u015ftiriciler, &#8220;Testler ge\u00e7iyor ama yine de bozuk&#8221; d\u00fc\u015f\u00fcncesiyle kar\u015f\u0131 kar\u015f\u0131ya kal\u0131r. Bu durum, test yazma motivasyonunu d\u00fc\u015f\u00fcrebilir ve s\u00fcre\u00e7lere \u015f\u00fcpheyle yakla\u015fmaya neden olabilir.<\/li>\n<li><strong>Hata Ay\u0131klama Zorlu\u011fu ve Zaman Kayb\u0131:<\/strong> Ger\u00e7ek API ile entegrasyonda bir sorun \u00e7\u0131kt\u0131\u011f\u0131nda, sorunun kayna\u011f\u0131n\u0131 bulmak \u00e7ok daha zor hale gelir. Sorun, kendi kodumuzda m\u0131, mock&#8217;ta m\u0131, yoksa ger\u00e7ek API&#8217;da m\u0131? Bu belirsizlik, hata ay\u0131klama s\u00fcrecini uzat\u0131r ve de\u011ferli geli\u015ftirme zaman\u0131n\u0131 bo\u015fa harcar.<\/li>\n<li><strong>Gecikmi\u015f Geri Bildirim:<\/strong> Hatalar, CI a\u015famas\u0131nda yakalanmak yerine, genellikle entegrasyon testlerinin daha ileri a\u015famalar\u0131nda (staging, pre-prod) veya en k\u00f6t\u00fcs\u00fc \u00fcretimde ortaya \u00e7\u0131kar. Bu, geri bildirim d\u00f6ng\u00fcs\u00fcn\u00fc uzat\u0131r ve hatan\u0131n d\u00fczeltilme maliyetini art\u0131r\u0131r.<\/li>\n<\/ul>\n<p>\u00d6zetle, mock&#8217;lar bize yalan s\u00f6yledi\u011finde, CI boru hatt\u0131m\u0131z bir bek\u00e7i k\u00f6pe\u011fi olmaktan \u00e7\u0131kar, sadece kap\u0131n\u0131n a\u00e7\u0131k oldu\u011funu d\u00fc\u015f\u00fcnd\u00fcren bir yan\u0131lsamaya d\u00f6n\u00fc\u015f\u00fcr. Bu durum, yaz\u0131l\u0131m geli\u015ftirme ekipleri i\u00e7in ciddi operasyonel ve itibar riskleri ta\u015f\u0131r. Bu nedenle, mock&#8217;lar\u0131n do\u011frulu\u011funu sa\u011flamak, CI\/CD stratejisinin ayr\u0131lmaz bir par\u00e7as\u0131 olmal\u0131d\u0131r.<\/p>\n<h2>Ger\u00e7ek D\u00fcnya Senaryosu: Bir \u00d6deme Sa\u011flay\u0131c\u0131s\u0131 API&#8217;\u0131 ile Ya\u015fanan Kabus<\/h2>\n<p>Bu b\u00f6l\u00fcmde, mock&#8217;un bize yalan s\u00f6ylemesinin somut bir \u00f6rne\u011fini, bir e-ticaret platformunun \u00f6deme entegrasyonu senaryosu \u00fczerinden ele alal\u0131m. Senaryomuzda, &#8220;H\u0131zl\u0131\u00d6deme&#8221; ad\u0131nda pop\u00fcler bir \u00f6deme ge\u00e7idi sa\u011flay\u0131c\u0131s\u0131yla entegre olmaya \u00e7al\u0131\u015fan bir ekibimiz var. Uygulama, kullan\u0131c\u0131lardan kredi kart\u0131 bilgilerini al\u0131p H\u0131zl\u0131\u00d6deme API&#8217;\u0131na g\u00f6ndererek \u00f6deme i\u015flemini tamaml\u0131yor.<\/p>\n<p><strong>Ba\u015flang\u0131\u00e7 Durumu ve Mock&#8217;lama Karar\u0131:<\/strong><\/p>\n<p>Geli\u015ftirme ekibi, H\u0131zl\u0131\u00d6deme API&#8217;\u0131n\u0131n test ortam\u0131n\u0131n yava\u015f ve bazen karars\u0131z oldu\u011funu fark etti. Ayr\u0131ca, her test i\u015flemi i\u00e7in k\u00fc\u00e7\u00fck bir \u00fccret al\u0131nd\u0131\u011f\u0131 bilgisi de vard\u0131. Bu durumlar, CI\/CD boru hatt\u0131n\u0131n her \u00e7al\u0131\u015ft\u0131\u011f\u0131nda ger\u00e7ek API&#8217;ya ba\u011f\u0131ml\u0131 kalman\u0131n s\u00fcrd\u00fcr\u00fclemez oldu\u011funu g\u00f6sterdi. Ekip, birim testleri ve entegrasyon testlerinin ilk a\u015famalar\u0131 i\u00e7in H\u0131zl\u0131\u00d6deme API&#8217;\u0131n\u0131 mock&#8217;lamaya karar verdi. Bu sayede, testler h\u0131zlanacak ve maliyetler d\u00fc\u015fecekti.<\/p>\n<p><strong>\u0130lk Mock Uygulamas\u0131:<\/strong><\/p>\n<p>Ekip, H\u0131zl\u0131\u00d6deme API dok\u00fcmantasyonundan faydalanarak basit bir mock servisi olu\u015fturdu. Bu mock, belirli bir URL&#8217;ye yap\u0131lan POST iste\u011fine kar\u015f\u0131l\u0131k, ba\u015far\u0131l\u0131 bir \u00f6deme i\u00e7in a\u015fa\u011f\u0131daki gibi bir JSON yan\u0131t\u0131 d\u00f6n\u00fcyordu:<\/p>\n<div class=\"code-container\">\n<pre><code>{\n  \"status\": \"success\",\n  \"transactionId\": \"TXN_123456789\",\n  \"amount\": 100.00,\n  \"currency\": \"TRY\",\n  \"message\": \"\u00d6deme ba\u015far\u0131yla tamamland\u0131.\"\n}<\/code><\/pre>\n<\/p><\/div>\n<p>Hata senaryolar\u0131 i\u00e7in de benzer basit mock&#8217;lar tan\u0131mland\u0131 (\u00f6rne\u011fin, ge\u00e7ersiz kart bilgisi i\u00e7in <code>\"status\": \"failed\"<\/code>). Bu mock&#8217;lar, uygulaman\u0131n \u00f6deme servisi katman\u0131n\u0131 test etmek i\u00e7in kullan\u0131ld\u0131. CI boru hatt\u0131 ye\u015fil yan\u0131yor, her \u015fey yolunda g\u00f6r\u00fcn\u00fcyordu. Geli\u015ftirme s\u00fcreci h\u0131zland\u0131, ekip mutlu bir \u015fekilde yeni \u00f6zellikler \u00fczerinde \u00e7al\u0131\u015f\u0131yordu.<\/p>\n<p><strong>Mock&#8217;un Yalan S\u00f6ylemesi An\u0131:<\/strong><\/p>\n<p>Birka\u00e7 ay sonra, H\u0131zl\u0131\u00d6deme, API&#8217;\u0131nda \u00f6nemli bir g\u00fcncelleme yapt\u0131\u011f\u0131n\u0131 duyurdu. G\u00fcncelleme notlar\u0131nda, g\u00fcvenlik ve esneklik ad\u0131na baz\u0131 alanlar\u0131n de\u011fi\u015ftirildi\u011fi ve yeni bir <code>\"paymentMethod\"<\/code> alan\u0131 eklendi\u011fi belirtildi. Ayr\u0131ca, <code>\"transactionId\"<\/code> alan\u0131 yerine art\u0131k <code>\"paymentReference\"<\/code> kullan\u0131laca\u011f\u0131 ve ba\u015far\u0131l\u0131 \u00f6demeler i\u00e7in HTTP durum kodunun 200 yerine 201 olaca\u011f\u0131 bilgisi yer al\u0131yordu. Ekip, bu de\u011fi\u015fiklikleri g\u00f6zden ka\u00e7\u0131rd\u0131 veya \u00f6nceliklendiremedi. Mock servisi g\u00fcncellenmedi.<\/p>\n<p>Uygulama kodunda, <code>transactionId<\/code> alan\u0131n\u0131 bekleyen ve HTTP 200 durum kodunu kontrol eden bir k\u0131s\u0131m vard\u0131. Mock&#8217;lar hala eski yan\u0131tlar\u0131 d\u00f6nd\u00fcrd\u00fc\u011f\u00fc i\u00e7in, CI boru hatt\u0131 bu de\u011fi\u015fikliklerden habersizdi ve t\u00fcm testler ba\u015far\u0131l\u0131 bir \u015fekilde ge\u00e7meye devam etti. Geli\u015ftiriciler, testlerin ye\u015fil yanmas\u0131na g\u00fcvenerek, yeni bir s\u00fcr\u00fcm\u00fc &#8220;staging&#8221; (sahneleme) ortam\u0131na da\u011f\u0131tt\u0131lar.<\/p>\n<p><strong>Kabus Ba\u015fl\u0131yor: Staging Ortam\u0131nda Gelen \u015eok<\/strong><\/p>\n<p>Staging ortam\u0131nda ger\u00e7ek H\u0131zl\u0131\u00d6deme API&#8217;\u0131 kullan\u0131l\u0131yordu. Yeni s\u00fcr\u00fcm da\u011f\u0131t\u0131ld\u0131ktan sonra, test ekibi ve baz\u0131 erken eri\u015fim kullan\u0131c\u0131lar\u0131 \u00f6deme yapmaya \u00e7al\u0131\u015ft\u0131klar\u0131nda, beklenmedik hatalarla kar\u015f\u0131la\u015ft\u0131lar:<\/p>\n<ul>\n<li>\u00d6demeler yap\u0131l\u0131yordu, ancak uygulaman\u0131n kullan\u0131c\u0131 aray\u00fcz\u00fcnde (UI) \u00f6deme ba\u015far\u0131l\u0131 olarak g\u00f6r\u00fcnm\u00fcyor, &#8220;bir hata olu\u015ftu&#8221; mesaj\u0131 g\u00f6steriliyordu.<\/li>\n<li>Veritaban\u0131na kaydedilen i\u015flem kimlikleri (<code>transactionId<\/code>) bo\u015f kal\u0131yordu, \u00e7\u00fcnk\u00fc uygulama ger\u00e7ek API&#8217;dan d\u00f6nen <code>paymentReference<\/code> alan\u0131n\u0131 tan\u0131m\u0131yordu.<\/li>\n<li>Baz\u0131 durumlarda, \u00f6deme ba\u015far\u0131l\u0131 olsa bile, uygulaman\u0131n ak\u0131\u015f\u0131 bir hata durumuna d\u00fc\u015f\u00fcyordu \u00e7\u00fcnk\u00fc HTTP 200 yerine 201 d\u00f6nd\u00fc\u011f\u00fcn\u00fc beklemiyordu.<\/li>\n<\/ul>\n<p>Ekip, durumu h\u0131zla ara\u015ft\u0131rmaya ba\u015flad\u0131. \u0130lk ba\u015fta kendi kodlar\u0131nda bir hata oldu\u011funu d\u00fc\u015f\u00fcnd\u00fcler, ancak birim testleri ve entegrasyon testleri hala ye\u015fil yan\u0131yordu. Saatler s\u00fcren hata ay\u0131klama (debugging) ve a\u011f trafi\u011fi analizi (network traffic analysis) sonucunda, ac\u0131 ger\u00e7ek ortaya \u00e7\u0131kt\u0131: Mock&#8217;lar onlara yalan s\u00f6ylemi\u015fti! Ger\u00e7ek API&#8217;n\u0131n de\u011fi\u015fti\u011fi, ancak mock&#8217;lar\u0131n bu de\u011fi\u015fiklikleri yans\u0131tmad\u0131\u011f\u0131 anla\u015f\u0131ld\u0131.<\/p>\n<p><strong>Al\u0131nan Dersler ve \u00c7\u00f6z\u00fcm:<\/strong><\/p>\n<p>Bu olay, ekibe mock&#8217;lar\u0131n do\u011frulu\u011funun ne kadar kritik oldu\u011funu ac\u0131 bir \u015fekilde g\u00f6sterdi. \u00c7\u00f6z\u00fcm, sadece mock&#8217;lar\u0131 g\u00fcncellemekten ibaret de\u011fildi; ayn\u0131 zamanda gelecekte benzer durumlar\u0131n ya\u015fanmas\u0131n\u0131 engellemek i\u00e7in s\u00fcre\u00e7leri de de\u011fi\u015ftirmekti:<\/p>\n<ul>\n<li><strong>API Dok\u00fcmantasyon Takibi:<\/strong> Tedarik\u00e7i API&#8217;lar\u0131n\u0131n dok\u00fcmantasyon de\u011fi\u015fikliklerini daha yak\u0131ndan takip etmek i\u00e7in bir s\u00fcre\u00e7 olu\u015fturuldu.<\/li>\n<li><strong>S\u00f6zle\u015fme Testleri (Contract Tests):<\/strong> Mock&#8217;lar ile ger\u00e7ek API aras\u0131ndaki s\u00f6zle\u015fmeyi (veri yap\u0131s\u0131, durum kodlar\u0131, alan isimleri vb.) do\u011frulayan otomatik testler yaz\u0131ld\u0131. Bu testler, CI boru hatt\u0131na entegre edildi ve ger\u00e7ek API&#8217;dan gelen \u00f6rnek yan\u0131tlarla mock yan\u0131tlar\u0131n\u0131 kar\u015f\u0131la\u015ft\u0131rd\u0131.<\/li>\n<li><strong>Daha Kapsaml\u0131 Entegrasyon Testleri:<\/strong> Staging ortam\u0131nda ger\u00e7ek API ile \u00e7al\u0131\u015fan daha kapsaml\u0131 ve otomatik entegrasyon testleri yaz\u0131ld\u0131. Bu testler, kritik i\u015f ak\u0131\u015flar\u0131n\u0131 u\u00e7tan uca (end-to-end) do\u011frulad\u0131.<\/li>\n<li><strong>Mock Servisi G\u00fcncelleme Sorumlulu\u011fu:<\/strong> Mock&#8217;lar\u0131n g\u00fcncelli\u011fini korumak i\u00e7in belirli bir ekip \u00fcyesine veya rol\u00fcne sorumluluk atand\u0131.<\/li>\n<\/ul>\n<p>Bu senaryo, mock&#8217;lar\u0131n sadece bir ara\u00e7 oldu\u011funu ve yanl\u0131\u015f y\u00f6netildi\u011finde faydadan \u00e7ok zarar getirebilece\u011fini a\u00e7\u0131k\u00e7a g\u00f6stermektedir. CI&#8217;\u0131 kurtarmak isterken, asl\u0131nda daha b\u00fcy\u00fck bir soruna davetiye \u00e7\u0131karm\u0131\u015ft\u0131k. Bu deneyim, mock&#8217;lama stratejilerinin sadece &#8220;nas\u0131l&#8221; de\u011fil, ayn\u0131 zamanda &#8220;nas\u0131l g\u00fcncel tutulaca\u011f\u0131&#8221; ve &#8220;nas\u0131l do\u011frulanaca\u011f\u0131&#8221; sorular\u0131na da odaklanmas\u0131 gerekti\u011fini vurgulad\u0131.<\/p>\n<h2>Mock&#8217;lar\u0131n Do\u011frulu\u011funu Nas\u0131l Sa\u011flar\u0131z? Stratejiler ve Ara\u00e7lar<\/h2>\n<p>Bir mock&#8217;un bize yalan s\u00f6ylemesini engellemek ve CI\/CD boru hatt\u0131m\u0131z\u0131n g\u00fcvenilirli\u011fini art\u0131rmak i\u00e7in \u00e7e\u015fitli stratejiler ve ara\u00e7lar mevcuttur. Bu yakla\u015f\u0131mlar, mock&#8217;lar\u0131m\u0131z\u0131n ger\u00e7ek API ile olan s\u00f6zle\u015fmesini s\u00fcrekli olarak do\u011frulamay\u0131 ve g\u00fcncel tutmay\u0131 hedefler.<\/p>\n<h3>1. S\u00f6zle\u015fme Testleri (Contract Testing)<\/h3>\n<p>S\u00f6zle\u015fme testi, en g\u00fc\u00e7l\u00fc do\u011frulama y\u00f6ntemlerinden biridir. Bu yakla\u015f\u0131m, bir hizmetin (sa\u011flay\u0131c\u0131) ve onu kullanan bir istemcinin (t\u00fcketici) birbirleriyle nas\u0131l etkile\u015fim kurdu\u011funu tan\u0131mlayan bir &#8220;s\u00f6zle\u015fme&#8221; olu\u015fturur. Bu s\u00f6zle\u015fme, API&#8217;n\u0131n beklenen isteklerini ve yan\u0131tlar\u0131n\u0131, veri yap\u0131lar\u0131n\u0131, HTTP durum kodlar\u0131n\u0131 ve hata mesajlar\u0131n\u0131 i\u00e7erir. S\u00f6zle\u015fme testleri, bu s\u00f6zle\u015fmeye hem t\u00fcketicinin hem de sa\u011flay\u0131c\u0131n\u0131n uydu\u011funu do\u011frular.<\/p>\n<ul>\n<li><strong>T\u00fcketici Taraf\u0131 S\u00f6zle\u015fme Testi (Consumer-Driven Contract Testing):<\/strong> Bu yakla\u015f\u0131mda, t\u00fcketici (yani bizim uygulamam\u0131z), d\u0131\u015f API&#8217;dan bekledi\u011fi s\u00f6zle\u015fmeyi tan\u0131mlar. Bu s\u00f6zle\u015fme daha sonra bir mock olu\u015fturmak ve kendi testlerini \u00e7al\u0131\u015ft\u0131rmak i\u00e7in kullan\u0131l\u0131r. Ayn\u0131 s\u00f6zle\u015fme, ger\u00e7ek API sa\u011flay\u0131c\u0131s\u0131n\u0131n da kendi taraf\u0131nda, API&#8217;\u0131n\u0131n bu s\u00f6zle\u015fmeye uydu\u011funu do\u011frulamak i\u00e7in kullan\u0131l\u0131r. Pop\u00fcler ara\u00e7lar aras\u0131nda <a href=\"https:\/\/pact.io\/\">Pact<\/a> ve Spring Cloud Contract bulunur.<\/li>\n<li><strong>Faydalar\u0131:<\/strong> Mock&#8217;lar\u0131m\u0131z\u0131n ger\u00e7ek API ile uyumlu olmas\u0131n\u0131 sa\u011flar, API de\u011fi\u015fiklikleri durumunda erken uyar\u0131 verir, ba\u011f\u0131ms\u0131z ekiplerin paralel \u00e7al\u0131\u015fmas\u0131n\u0131 kolayla\u015ft\u0131r\u0131r.<\/li>\n<\/ul>\n<p>\u00d6rnek bir Pact testi (pseudo-code):<\/p>\n<div class=\"code-container\">\n<pre><code>\/\/ T\u00fcketici taraf\u0131nda (bizim uygulamam\u0131z)\n\/\/ H\u0131zl\u0131\u00d6deme API'\u0131ndan beklenen bir s\u00f6zle\u015fme tan\u0131ml\u0131yoruz\ndescribe('H\u0131zl\u0131\u00d6deme API', () => {\n  it('ba\u015far\u0131l\u0131 bir \u00f6deme yan\u0131t\u0131 d\u00f6nmelidir', async () => {\n    const expectedResponse = {\n      status: 'success',\n      paymentReference: 'REF_987654321', \/\/ Yeni alan\n      amount: 100.00,\n      currency: 'TRY',\n      message: '\u00d6deme ba\u015far\u0131yla tamamland\u0131.'\n    };\n\n    \/\/ Pact mock servisini ba\u015flat ve beklentiyi ayarla\n    await provider.addInteraction({\n      state: '\u00f6deme ba\u015far\u0131l\u0131 bir \u015fekilde i\u015flendi\u011finde',\n      uponReceiving: '\u00f6deme iste\u011fi',\n      withRequest: {\n        method: 'POST',\n        path: '\/api\/v1\/payments',\n        headers: { 'Content-Type': 'application\/json' },\n        body: {\n          cardNumber: '...',\n          expiryDate: '...',\n          cvv: '...',\n          amount: 100.00\n        }\n      },\n      willRespondWith: {\n        status: 201, \/\/ Yeni HTTP durumu\n        headers: { 'Content-Type': 'application\/json' },\n        body: expectedResponse\n      }\n    });\n\n    \/\/ Kendi \u00f6deme servisimizle mock'a kar\u015f\u0131 bir istek yap\n    const result = await myPaymentService.processPayment({ \/* ... kart bilgileri ... *\/ });\n\n    \/\/ Yan\u0131t\u0131n beklenen yap\u0131da oldu\u011funu do\u011frula\n    expect(result.status).toBe('success');\n    expect(result.paymentReference).toBeDefined();\n\n    \/\/ Pact etkile\u015fimini do\u011frula (mock'a do\u011fru \u00e7a\u011fr\u0131 yap\u0131ld\u0131\u011f\u0131n\u0131 kontrol eder)\n    await provider.verify();\n  });\n});<\/code><\/pre>\n<\/p><\/div>\n<h3>2. OpenAPI\/Swagger Tan\u0131mlar\u0131ndan Mock \u00dcretimi<\/h3>\n<p>Bir\u00e7ok harici API, davran\u0131\u015flar\u0131n\u0131 OpenAPI (eski ad\u0131yla Swagger) spesifikasyonlar\u0131 arac\u0131l\u0131\u011f\u0131yla tan\u0131mlar. Bu dosyalar, API&#8217;n\u0131n t\u00fcm u\u00e7 noktalar\u0131n\u0131 (endpoints), istek ve yan\u0131t \u015femalar\u0131n\u0131, parametrelerini ve HTTP durum kodlar\u0131n\u0131 detayl\u0131 bir \u015fekilde a\u00e7\u0131klar. Bu spesifikasyonlar\u0131 kullanarak otomatik olarak mock servisleri veya istemci kodlar\u0131 (client code) \u00fcreten ara\u00e7lar mevcuttur.<\/p>\n<ul>\n<li><strong>Ara\u00e7lar:<\/strong> OpenAPI Generator, Stoplight Prism, Postman Mock Servers.<\/li>\n<li><strong>Faydalar\u0131:<\/strong> Mock&#8217;lar\u0131n her zaman API spesifikasyonuyla uyumlu olmas\u0131n\u0131 sa\u011flar, manuel hata riskini azalt\u0131r, API g\u00fcncellendi\u011finde mock&#8217;lar\u0131n otomatik olarak yeniden \u00fcretilmesine olanak tan\u0131r.<\/li>\n<\/ul>\n<h3>3. D\u00fczenli Senkronizasyon ve Do\u011frulama<\/h3>\n<p>E\u011fer s\u00f6zle\u015fme testleri veya otomatik \u00fcretim m\u00fcmk\u00fcn de\u011filse, mock&#8217;lar\u0131n\u0131z\u0131 d\u00fczenli olarak ger\u00e7ek API ile senkronize etmek i\u00e7in manuel veya yar\u0131 otomatik s\u00fcre\u00e7ler olu\u015fturmal\u0131s\u0131n\u0131z.<\/p>\n<ul>\n<li><strong>Manuel \u0130nceleme:<\/strong> API sa\u011flay\u0131c\u0131s\u0131n\u0131n dok\u00fcmantasyonunu ve de\u011fi\u015fiklik g\u00fcnl\u00fcklerini (changelogs) periyodik olarak kontrol edin.<\/li>\n<li><strong>Ger\u00e7ek API Yan\u0131tlar\u0131n\u0131 Kullanma:<\/strong> Ger\u00e7ek API&#8217;dan al\u0131nan \u00f6rnek yan\u0131tlar\u0131 (\u00f6rne\u011fin, <code>curl<\/code> veya Postman ile) mock tan\u0131mlar\u0131n\u0131z\u0131 g\u00fcncellemek i\u00e7in kullan\u0131n.<\/li>\n<li><strong>Test Ortam\u0131nda U\u00e7tan Uca Testler:<\/strong> CI boru hatt\u0131n\u0131n ileri a\u015famalar\u0131nda (staging veya pre-prod), ger\u00e7ek API&#8217;lar ile \u00e7al\u0131\u015fan u\u00e7tan uca (end-to-end) entegrasyon testleri \u00e7al\u0131\u015ft\u0131rmak, mock&#8217;lar\u0131n g\u00f6zden ka\u00e7\u0131rd\u0131\u011f\u0131 sorunlar\u0131 yakalamak i\u00e7in hayati \u00f6neme sahiptir.<\/li>\n<\/ul>\n<h3>4. Dinamik Mock Servisleri<\/h3>\n<p>Basit JSON dosyalar\u0131 yerine, daha geli\u015fmi\u015f mock sunucular\u0131 (\u00f6rne\u011fin <a href=\"http:\/\/wiremock.org\/\">WireMock<\/a>, <a href=\"https:\/\/mock-server.com\/\">MockServer<\/a>) kullanarak daha dinamik ve esnek mock&#8217;lar olu\u015fturabilirsiniz. Bu ara\u00e7lar \u015funlar\u0131 yapman\u0131z\u0131 sa\u011flar:<\/p>\n<ul>\n<li><strong>Ko\u015fullu Yan\u0131tlar:<\/strong> Belirli istek parametrelerine, ba\u015fl\u0131klar\u0131na veya g\u00f6vdelerine (body) g\u00f6re farkl\u0131 yan\u0131tlar d\u00f6nd\u00fcrme.<\/li>\n<li><strong>Durum Y\u00f6netimi (Stateful Mocks):<\/strong> API&#8217;n\u0131n durumunu taklit etme (\u00f6rne\u011fin, bir kaynak olu\u015fturulduktan sonra onu &#8220;get&#8221; iste\u011fiyle alabilme).<\/li>\n<li><strong>Gecikme Sim\u00fclasyonu:<\/strong> Ger\u00e7ek API&#8217;n\u0131n yan\u0131t gecikmelerini taklit ederek performans testleri yapma.<\/li>\n<li><strong>Hata Enjeksiyonu:<\/strong> Belirli senaryolarda kas\u0131tl\u0131 olarak hata yan\u0131tlar\u0131 d\u00f6nd\u00fcrme.<\/li>\n<\/ul>\n<p>WireMock ile basit bir mock tan\u0131m\u0131:<\/p>\n<div class=\"code-container\">\n<pre><code>\/\/ Java (WireMock) \u00f6rne\u011fi\nWireMock.stubFor(WireMock.post(WireMock.urlEqualTo(\"\/api\/v1\/payments\"))\n    .withRequestBody(WireMock.matchingJsonPath(\"$.amount\", WireMock.equalTo(\"100.00\")))\n    .willReturn(WireMock.aResponse()\n        .withStatus(201)\n        .withHeader(\"Content-Type\", \"application\/json\")\n        .withBody(\"{ \\\"status\\\": \\\"success\\\", \\\"paymentReference\\\": \\\"REF_987654321\\\" }\")));<\/code><\/pre>\n<\/p><\/div>\n<h3>5. Versiyonlama ve Dok\u00fcmantasyon<\/h3>\n<p>Mock&#8217;lar\u0131n\u0131z\u0131 uygulaman\u0131z\u0131n di\u011fer kodlar\u0131 gibi versiyonlay\u0131n ve iyi dok\u00fcmante edin. Hangi mock&#8217;un hangi API versiyonunu taklit etti\u011fini a\u00e7\u0131k\u00e7a belirtin. Bu, \u00f6zellikle b\u00fcy\u00fck ekiplerde ve birden fazla entegrasyonu olan projelerde karma\u015f\u0131kl\u0131\u011f\u0131 y\u00f6netmek i\u00e7in \u00f6nemlidir.<\/p>\n<p>Bu stratejilerin kombinasyonu, mock&#8217;lar\u0131n\u0131z\u0131n yaln\u0131zca testleri ge\u00e7mesini de\u011fil, ayn\u0131 zamanda ger\u00e7ek API&#8217;n\u0131n davran\u0131\u015f\u0131n\u0131 do\u011fru bir \u015fekilde yans\u0131tmas\u0131n\u0131 sa\u011flayarak CI\/CD boru hatt\u0131n\u0131z\u0131n ger\u00e7ek de\u011ferini koruman\u0131za yard\u0131mc\u0131 olacakt\u0131r. Unutmay\u0131n, mock&#8217;lar bir amaca hizmet eder, ancak bu amaca hizmet etmeyi b\u0131rakt\u0131klar\u0131nda, birer y\u00fck haline gelirler.<\/p>\n<h2>Geli\u015fmi\u015f Mock&#8217;lama Teknikleri ve En \u0130yi Uygulamalar<\/h2>\n<p>Mock&#8217;lama, basit statik yan\u0131tlar d\u00f6nd\u00fcrmekten \u00e7ok daha fazlas\u0131n\u0131 sunar. Geli\u015fmi\u015f teknikler ve en iyi uygulamalar, mock&#8217;lar\u0131n\u0131z\u0131 daha dinamik, ger\u00e7ek\u00e7i ve s\u00fcrd\u00fcr\u00fclebilir hale getirerek test stratejinizi g\u00fc\u00e7lendirir. Bu b\u00f6l\u00fcmde, daha deneyimli kullan\u0131c\u0131lar i\u00e7in ipu\u00e7lar\u0131 ve p\u00fcf noktalar\u0131 ele alaca\u011f\u0131z.<\/p>\n<h3>1. Durum Y\u00f6netimi (Stateful Mocks)<\/h3>\n<p>\u00c7o\u011fu API, basit bir istek-yan\u0131t d\u00f6ng\u00fcs\u00fcnden daha karma\u015f\u0131k bir ya\u015fam d\u00f6ng\u00fcs\u00fcne sahiptir. \u00d6rne\u011fin, bir kaynak \u00f6nce olu\u015fturulur, sonra g\u00fcncellenir ve ard\u0131ndan silinir. Stateless (durumsuz) mock&#8217;lar bu t\u00fcr senaryolar\u0131 taklit edemez. Stateful mock&#8217;lar ise, gelen isteklere g\u00f6re i\u00e7 durumlar\u0131n\u0131 de\u011fi\u015ftirebilir ve sonraki isteklere farkl\u0131 yan\u0131tlar verebilir.<\/p>\n<ul>\n<li><strong>Nas\u0131l Uygulan\u0131r:<\/strong> WireMock gibi ara\u00e7lar, durumu y\u00f6netmek i\u00e7in &#8220;senaryolar&#8221; (scenarios) veya &#8220;durum makinesi&#8221; (state machine) kavramlar\u0131n\u0131 destekler. Bir iste\u011fe yan\u0131t verdikten sonra, mock&#8217;un durumunu &#8220;bekleyen&#8221;den &#8220;i\u015flendi&#8221;ye de\u011fi\u015ftirebilir ve bu duruma g\u00f6re farkl\u0131 yan\u0131tlar tan\u0131mlayabilirsiniz.<\/li>\n<li><strong>\u00d6rnek Senaryo:<\/strong> Bir sipari\u015f API&#8217;\u0131. Sipari\u015f olu\u015fturuldu\u011funda 201 yan\u0131t\u0131 d\u00f6ner ve durum &#8220;pending&#8221; olur. Ard\u0131ndan bir &#8220;sipari\u015f durumu sorgula&#8221; iste\u011fi yap\u0131ld\u0131\u011f\u0131nda, sipari\u015fin durumuna g\u00f6re &#8220;pending&#8221;, &#8220;shipped&#8221; veya &#8220;delivered&#8221; gibi farkl\u0131 yan\u0131tlar d\u00f6nebilir.<\/li>\n<\/ul>\n<h3>2. Dinamik Yan\u0131tlar ve \u015eablonlama<\/h3>\n<p>Bazen mock yan\u0131tlar\u0131n\u0131n, gelen iste\u011fin i\u00e7eri\u011fine g\u00f6re dinamik olarak de\u011fi\u015fmesi gerekir. \u00d6rne\u011fin, bir kullan\u0131c\u0131 ID&#8217;si ile yap\u0131lan bir istek i\u00e7in, yan\u0131tta o ID&#8217;nin tekrar d\u00f6nmesi beklenebilir. \u015eablonlama (templating) motorlar\u0131 bu ihtiyac\u0131 kar\u015f\u0131lar.<\/p>\n<ul>\n<li><strong>Ara\u00e7lar:<\/strong> Handlebars (WireMock&#8217;ta), Apache Velocity, Jinja2.<\/li>\n<li><strong>Nas\u0131l Uygulan\u0131r:<\/strong> Mock tan\u0131m\u0131n\u0131zda, yan\u0131ta dinamik de\u011ferler eklemek i\u00e7in \u015fablon de\u011fi\u015fkenleri kullan\u0131rs\u0131n\u0131z. \u00d6rne\u011fin, istek g\u00f6vdesindeki bir alan\u0131 al\u0131p yan\u0131t g\u00f6vdesine yerle\u015ftirebilirsiniz.<\/li>\n<\/ul>\n<div class=\"code-container\">\n<pre><code>\/\/ WireMock (Handlebars ile dinamik yan\u0131t)\nWireMock.stubFor(WireMock.post(WireMock.urlEqualTo(\"\/api\/v1\/users\"))\n    .willReturn(WireMock.aResponse()\n        .withStatus(201)\n        .withHeader(\"Content-Type\", \"application\/json\")\n        .withBody(\"{ \\\"id\\\": \\\"{{jsonPath request.body '$.id'}}\\\", \\\"name\\\": \\\"{{jsonPath request.body '$.name'}}\\\", \\\"status\\\": \\\"created\\\" }\")));<\/code><\/pre>\n<\/p><\/div>\n<h3>3. Hata Enjeksiyonu ve Gecikme Sim\u00fclasyonu<\/h3>\n<p>Uygulamalar\u0131m\u0131z\u0131n sadece &#8220;mutlu yol&#8221; senaryolar\u0131nda de\u011fil, ayn\u0131 zamanda API&#8217;n\u0131n hata d\u00f6nd\u00fcrd\u00fc\u011f\u00fc veya yava\u015f yan\u0131t verdi\u011fi durumlarda da d\u00fczg\u00fcn \u00e7al\u0131\u015f\u0131p \u00e7al\u0131\u015fmad\u0131\u011f\u0131n\u0131 test etmek kritiktir. Mock&#8217;lar, bu t\u00fcr senaryolar\u0131 sim\u00fcle etmek i\u00e7in idealdir.<\/p>\n<ul>\n<li><strong>Hata Enjeksiyonu:<\/strong> Belirli bir y\u00fczdeyle veya belirli bir iste\u011fe kar\u015f\u0131l\u0131k 500 Internal Server Error, 401 Unauthorized gibi hata kodlar\u0131 d\u00f6nd\u00fcr\u00fcn. Bu, uygulaman\u0131z\u0131n hata y\u00f6netimi (error handling) ve geri d\u00f6n\u00fc\u015f (fallback) mekanizmalar\u0131n\u0131 test etmenize olanak tan\u0131r.<\/li>\n<li><strong>Gecikme Sim\u00fclasyonu:<\/strong> Mock yan\u0131tlar\u0131na kas\u0131tl\u0131 gecikmeler (latency) ekleyin. Bu, uygulaman\u0131z\u0131n kullan\u0131c\u0131 aray\u00fcz\u00fcnde y\u00fckleme g\u00f6stergelerinin (loading indicators) do\u011fru \u00e7al\u0131\u015f\u0131p \u00e7al\u0131\u015fmad\u0131\u011f\u0131n\u0131, zaman a\u015f\u0131mlar\u0131n\u0131n (timeouts) beklendi\u011fi gibi i\u015fleyip i\u015flemedi\u011fini veya asenkron i\u015flemlerin do\u011fru y\u00f6netilip y\u00f6netilmedi\u011fini test etmenizi sa\u011flar.<\/li>\n<\/ul>\n<h3>4. CI\/CD Boru Hatt\u0131na Entegrasyon<\/h3>\n<p>Mock&#8217;lama \u00e7\u00f6z\u00fcmlerinizin CI\/CD boru hatt\u0131n\u0131zla sorunsuz bir \u015fekilde entegre olmas\u0131, onlar\u0131n etkinli\u011fini art\u0131r\u0131r.<\/p>\n<ul>\n<li><strong>Otomatik Ba\u015flatma\/Durdurma:<\/strong> Testler ba\u015flamadan \u00f6nce mock servislerini otomatik olarak ba\u015flat\u0131n ve testler bittikten sonra durdurun. Docker konteynerleri bu konuda olduk\u00e7a kullan\u0131\u015fl\u0131d\u0131r.<\/li>\n<li><strong>Yap\u0131land\u0131rma Y\u00f6netimi:<\/strong> Mock&#8217;lar\u0131n yap\u0131land\u0131rmas\u0131n\u0131 (\u00f6rne\u011fin, farkl\u0131 ortamlar i\u00e7in farkl\u0131 mock senaryolar\u0131) CI\/CD de\u011fi\u015fkenleri veya yap\u0131land\u0131rma dosyalar\u0131 arac\u0131l\u0131\u011f\u0131yla y\u00f6netin.<\/li>\n<li><strong>Raporlama:<\/strong> Mock&#8217;lar arac\u0131l\u0131\u011f\u0131yla yap\u0131lan \u00e7a\u011fr\u0131lar\u0131n ve do\u011frulama sonu\u00e7lar\u0131n\u0131n CI raporlar\u0131na dahil edildi\u011finden emin olun.<\/li>\n<\/ul>\n<h3>5. Mock&#8217;lar\u0131n Sahipli\u011fi ve Bak\u0131m\u0131<\/h3>\n<p>Mock&#8217;lar\u0131n &#8220;yalan s\u00f6ylemesini&#8221; engellemek i\u00e7in, onlar\u0131n da kod gibi sahiplenilmesi ve bak\u0131m\u0131n\u0131n yap\u0131lmas\u0131 gerekir.<\/p>\n<ul>\n<li><strong>Sorumluluk Atamas\u0131:<\/strong> Hangi ekibin veya ki\u015finin belirli bir mock&#8217;un g\u00fcncelli\u011finden sorumlu oldu\u011funu belirleyin.<\/li>\n<li><strong>Kod Olarak Mock&#8217;lar (Mocks as Code):<\/strong> Mock tan\u0131mlar\u0131n\u0131 versiyon kontrol sisteminde (Git gibi) saklay\u0131n. Bu, de\u011fi\u015fikliklerin izlenmesini, g\u00f6zden ge\u00e7irilmesini ve geri al\u0131nmas\u0131n\u0131 kolayla\u015ft\u0131r\u0131r.<\/li>\n<li><strong>Dok\u00fcmantasyon:<\/strong> Her mock&#8217;un neyi taklit etti\u011fini, hangi senaryolar\u0131 kapsad\u0131\u011f\u0131n\u0131 ve neden kullan\u0131ld\u0131\u011f\u0131n\u0131 a\u00e7\u0131klayan iyi bir dok\u00fcmantasyon sa\u011flay\u0131n.<\/li>\n<\/ul>\n<h3>6. Ger\u00e7ek API Yan\u0131tlar\u0131n\u0131 Kaydetme ve Oynatma (Record\/Replay)<\/h3>\n<p>Baz\u0131 ara\u00e7lar (\u00f6rne\u011fin WireMock, VCR), ger\u00e7ek API \u00e7a\u011fr\u0131lar\u0131n\u0131 kaydedip daha sonra bu kay\u0131tlar\u0131 mock olarak oynatma yetene\u011fi sunar. Bu, mock&#8217;lar\u0131 olu\u015fturman\u0131n ve g\u00fcncellemenin h\u0131zl\u0131 bir yoludur, ancak kaydedilen yan\u0131tlar\u0131n g\u00fcncelli\u011fini yine de kontrol etmek gerekir.<\/p>\n<p>Bu geli\u015fmi\u015f teknikler ve en iyi uygulamalar, mock&#8217;lama stratejinizi olgunla\u015ft\u0131rarak, testlerinizin sadece h\u0131zl\u0131 de\u011fil, ayn\u0131 zamanda g\u00fcvenilir olmas\u0131n\u0131 sa\u011flar. Mock&#8217;lar, do\u011fru kullan\u0131ld\u0131\u011f\u0131nda, yaz\u0131l\u0131m geli\u015ftirme s\u00fcrecinizin h\u0131z\u0131n\u0131 ve kalitesini \u00f6nemli \u00f6l\u00e7\u00fcde art\u0131rabilir.<\/p>\n<h2>Mock&#8217;lar\u0131n\u0131z\u0131 Canl\u0131 Tutmak: S\u00fcrekli Bak\u0131m ve Otomasyon<\/h2>\n<p>API mock&#8217;lama, geli\u015ftirme ve test s\u00fcre\u00e7lerimize h\u0131z ve esneklik katarken, bu mock&#8217;lar\u0131n do\u011frulu\u011funu ve g\u00fcncelli\u011fini s\u00fcrekli olarak sa\u011flamak kritik bir zorluktur. Bir mock&#8217;un &#8220;yalan s\u00f6ylemesi&#8221; durumunu ya\u015famamak i\u00e7in, onlar\u0131 ya\u015fayan bir varl\u0131k gibi g\u00f6r\u00fcp d\u00fczenli bak\u0131m\u0131n\u0131 yapmak ve m\u00fcmk\u00fcn oldu\u011funca otomatikle\u015ftirmek gerekir. \u0130\u015fte bu konuda izlenebilecek ad\u0131mlar ve en iyi uygulamalar:<\/p>\n<h3>1. Otomatik Do\u011frulama Mekanizmalar\u0131<\/h3>\n<p>Mock&#8217;lar\u0131n\u0131z\u0131 manuel olarak kontrol etmek zaman al\u0131c\u0131 ve hataya a\u00e7\u0131k bir s\u00fcre\u00e7tir. Bu nedenle, otomatik do\u011frulama mekanizmalar\u0131 kurmak esast\u0131r.<\/p>\n<ul>\n<li><strong>S\u00f6zle\u015fme Testlerinin CI&#8217;a Entegrasyonu:<\/strong> Daha \u00f6nce bahsedildi\u011fi gibi, Pact gibi ara\u00e7larla yaz\u0131lan s\u00f6zle\u015fme testlerini CI boru hatt\u0131n\u0131z\u0131n ayr\u0131lmaz bir par\u00e7as\u0131 haline getirin. Bu testler, hem mock&#8217;lar\u0131n\u0131z\u0131n hem de ger\u00e7ek API&#8217;n\u0131n s\u00f6zle\u015fmeye uyup uymad\u0131\u011f\u0131n\u0131 otomatik olarak kontrol eder. Ger\u00e7ek API&#8217;da bir de\u011fi\u015fiklik oldu\u011funda, bu testler hemen ba\u015far\u0131s\u0131z olur ve size erken uyar\u0131 verir.<\/li>\n<li><strong>Periyodik Ger\u00e7ek API Kar\u015f\u0131la\u015ft\u0131rmalar\u0131:<\/strong> Belirli aral\u0131klarla (\u00f6rne\u011fin, her gece veya haftal\u0131k), mock&#8217;lar\u0131n\u0131z\u0131n d\u00f6nd\u00fcrd\u00fc\u011f\u00fc yan\u0131tlar\u0131, ger\u00e7ek API&#8217;dan al\u0131nan g\u00fcncel yan\u0131tlarla otomatik olarak kar\u015f\u0131la\u015ft\u0131ran bir i\u015f (job) \u00e7al\u0131\u015ft\u0131r\u0131n. Bu, yan\u0131t yap\u0131lar\u0131ndaki veya veri tiplerindeki beklenmedik farklar\u0131 tespit etmenize yard\u0131mc\u0131 olur. Bu kar\u015f\u0131la\u015ft\u0131rmalar\u0131 yapmak i\u00e7in \u00f6zel olarak yaz\u0131lm\u0131\u015f betikler (scripts) veya test otomasyon ara\u00e7lar\u0131 kullan\u0131labilir.<\/li>\n<li><strong>API \u015eemas\u0131 Do\u011frulamas\u0131:<\/strong> E\u011fer API&#8217;n\u0131n OpenAPI\/Swagger \u015femas\u0131 mevcutsa, mock yan\u0131tlar\u0131n\u0131z\u0131n bu \u015femaya uygunlu\u011funu otomatik olarak do\u011frulayan testler yaz\u0131n. Bu, veri tiplerinin, zorunlu alanlar\u0131n ve alan isimlerinin do\u011fru olmas\u0131n\u0131 sa\u011flar.<\/li>\n<\/ul>\n<h3>2. D\u00fczenli G\u00f6zden Ge\u00e7irme ve G\u00fcncelleme D\u00f6ng\u00fcleri<\/h3>\n<p>Otomasyon ne kadar g\u00fc\u00e7l\u00fc olursa olsun, insan fakt\u00f6r\u00fc ve d\u00fczenli g\u00f6zden ge\u00e7irme d\u00f6ng\u00fcleri vazge\u00e7ilmezdir.<\/p>\n<ul>\n<li><strong>API Sa\u011flay\u0131c\u0131 De\u011fi\u015fiklik G\u00fcnl\u00fcklerinin Takibi:<\/strong> Tedarik\u00e7i API&#8217;lar\u0131n\u0131n dok\u00fcmantasyonunu, de\u011fi\u015fiklik g\u00fcnl\u00fcklerini (changelogs) ve duyurular\u0131n\u0131 d\u00fczenli olarak takip edin. Bu de\u011fi\u015fiklikler, mock&#8217;lar\u0131n\u0131z\u0131n g\u00fcncellenmesi gerekti\u011finin ilk i\u015faretleridir. Bir &#8220;API de\u011fi\u015fiklik takip\u00e7isi&#8221; rol\u00fc atamak faydal\u0131 olabilir.<\/li>\n<li><strong>Periyodik Mock G\u00f6zden Ge\u00e7irme Toplant\u0131lar\u0131:<\/strong> Geli\u015ftirme ekibi olarak, belirli aral\u0131klarla (\u00f6rne\u011fin, ayl\u0131k) mock&#8217;lar\u0131n\u0131z\u0131 g\u00f6zden ge\u00e7irin. Hangi mock&#8217;lar\u0131n hala ge\u00e7erli oldu\u011funu, hangilerinin g\u00fcncellenmesi gerekti\u011fini veya hangilerinin art\u0131k gereksiz oldu\u011funu tart\u0131\u015f\u0131n.<\/li>\n<li><strong>Kapsam Analizi:<\/strong> Mevcut mock&#8217;lar\u0131n\u0131z\u0131n, uygulaman\u0131z\u0131n kulland\u0131\u011f\u0131 t\u00fcm kritik API u\u00e7 noktalar\u0131n\u0131 ve senaryolar\u0131n\u0131 (ba\u015far\u0131l\u0131, hata, kenar durumlar\u0131) kapsay\u0131p kapsamad\u0131\u011f\u0131n\u0131 de\u011ferlendirin. Yeni geli\u015ftirilen \u00f6zellikler veya eklenen ba\u011f\u0131ml\u0131l\u0131klar i\u00e7in yeni mock&#8217;lar olu\u015fturulmas\u0131 gerekebilir.<\/li>\n<\/ul>\n<h3>3. Geri Bildirim Mekanizmalar\u0131 ve Uyar\u0131lar<\/h3>\n<p>Bir mock&#8217;un g\u00fcncelli\u011fini yitirdi\u011fini veya ger\u00e7ek API&#8217;dan farkl\u0131la\u015ft\u0131\u011f\u0131n\u0131 m\u00fcmk\u00fcn olan en k\u0131sa s\u00fcrede \u00f6\u011frenmelisiniz.<\/p>\n<ul>\n<li><strong>CI\/CD Boru Hatt\u0131 Bildirimleri:<\/strong> Otomatik do\u011frulama testleri ba\u015far\u0131s\u0131z oldu\u011funda, ekibe (Slack, e-posta vb. arac\u0131l\u0131\u011f\u0131yla) an\u0131nda bildirim g\u00f6nderin. Bu, sorunun h\u0131zl\u0131ca fark edilip \u00e7\u00f6z\u00fclmesini sa\u011flar.<\/li>\n<li><strong>Performans ve Hata \u0130zleme (Monitoring):<\/strong> \u00dcretim ortam\u0131nda ger\u00e7ek API entegrasyonlar\u0131n\u0131z\u0131n performans\u0131n\u0131 ve hata oranlar\u0131n\u0131 izleyin. E\u011fer mock&#8217;lar\u0131n\u0131z yeterince ger\u00e7ek\u00e7i de\u011filse, \u00fcretimdeki hatalar veya performans d\u00fc\u015f\u00fc\u015fleri, mock&#8217;lar\u0131n\u0131z\u0131n iyile\u015ftirilmesi gerekti\u011fini i\u015faret edebilir.<\/li>\n<\/ul>\n<h3>4. &#8220;Kod Olarak Mock&#8221; Yakla\u015f\u0131m\u0131<\/h3>\n<p>Mock tan\u0131mlar\u0131n\u0131 ve yap\u0131land\u0131rmalar\u0131n\u0131 di\u011fer t\u00fcm kod varl\u0131klar\u0131 gibi versiyon kontrol sisteminde (Git) saklay\u0131n. Bu yakla\u015f\u0131m, mock&#8217;lar\u0131n ya\u015fam d\u00f6ng\u00fcs\u00fcn\u00fc y\u00f6netmeyi kolayla\u015ft\u0131r\u0131r:<\/p>\n<ul>\n<li><strong>Versiyonlama:<\/strong> Mock&#8217;lar da kod gibi versiyonlan\u0131r. Bu, belirli bir uygulama s\u00fcr\u00fcm\u00fcn\u00fcn hangi mock versiyonunu kulland\u0131\u011f\u0131n\u0131 takip etmenizi sa\u011flar.<\/li>\n<li><strong>De\u011fi\u015fiklik Takibi:<\/strong> Mock&#8217;larda yap\u0131lan de\u011fi\u015fiklikler Git ge\u00e7mi\u015finde izlenebilir. Kimin, ne zaman, hangi de\u011fi\u015fikli\u011fi yapt\u0131\u011f\u0131n\u0131 g\u00f6rmek m\u00fcmk\u00fcnd\u00fcr.<\/li>\n<li><strong>Kod \u0130ncelemesi (Code Review):<\/strong> Mock de\u011fi\u015fiklikleri de di\u011fer kod de\u011fi\u015fiklikleri gibi g\u00f6zden ge\u00e7irme s\u00fcre\u00e7lerinden ge\u00e7ebilir. Bu, hatal\u0131 veya eksik mock tan\u0131mlar\u0131n\u0131n tespit edilmesine yard\u0131mc\u0131 olur.<\/li>\n<li><strong>Da\u011f\u0131t\u0131m Otomasyonu:<\/strong> Mock servislerinizin da\u011f\u0131t\u0131m\u0131n\u0131 (\u00f6rne\u011fin, Docker konteynerleri olarak) otomatikle\u015ftirebilirsiniz.<\/li>\n<\/ul>\n<h3>5. Ekip \u0130\u00e7i \u0130\u015fbirli\u011fi ve E\u011fitim<\/h3>\n<p>Mock&#8217;lar\u0131n etkinli\u011fi, t\u00fcm ekibin bu konudaki bilincine ve i\u015fbirli\u011fine ba\u011fl\u0131d\u0131r.<\/p>\n<ul>\n<li><strong>Bilgi Payla\u015f\u0131m\u0131:<\/strong> API de\u011fi\u015fiklikleri veya mock g\u00fcncellemeleri hakk\u0131nda ekip i\u00e7inde d\u00fczenli bilgi payla\u015f\u0131m\u0131 yap\u0131n.<\/li>\n<li><strong>E\u011fitim:<\/strong> Yeni ekip \u00fcyelerine mock&#8217;lama stratejileri, ara\u00e7lar\u0131 ve en iyi uygulamalar hakk\u0131nda e\u011fitim verin.<\/li>\n<li><strong>Sahiplik:<\/strong> Mock&#8217;lar\u0131n sadece &#8220;test ekibinin&#8221; de\u011fil, t\u00fcm geli\u015ftirme ekibinin ortak sorumlulu\u011funda oldu\u011funu vurgulay\u0131n.<\/li>\n<\/ul>\n<p>Mock&#8217;lar\u0131 canl\u0131 tutmak, s\u00fcrekli bir \u00e7aba gerektirir. Ancak bu \u00e7aba, CI\/CD boru hatt\u0131n\u0131z\u0131n g\u00fcvenilirli\u011fini, geli\u015ftirme h\u0131z\u0131n\u0131z\u0131 ve nihayetinde yaz\u0131l\u0131m\u0131n\u0131z\u0131n kalitesini art\u0131rarak fazlas\u0131yla kar\u015f\u0131l\u0131\u011f\u0131n\u0131 verir. Unutmay\u0131n, iyi y\u00f6netilmeyen bir mock, testlerinizi ge\u00e7irse bile sizi \u00fcretimde ba\u015far\u0131s\u0131zl\u0131\u011fa s\u00fcr\u00fckleyebilir.<\/p>\n<h2>Sonu\u00e7 ve S\u0131k\u00e7a Sorulan Sorular<\/h2>\n<p>API mock&#8217;lama, modern yaz\u0131l\u0131m geli\u015ftirme s\u00fcre\u00e7lerinde harici ba\u011f\u0131ml\u0131l\u0131klar\u0131 y\u00f6netmek, testleri h\u0131zland\u0131rmak ve maliyetleri d\u00fc\u015f\u00fcrmek i\u00e7in vazge\u00e7ilmez bir tekniktir. Ancak, bu makalede detayl\u0131ca inceledi\u011fimiz gibi, mock&#8217;lar bize &#8220;yalan s\u00f6yledi\u011finde&#8221;, yani ger\u00e7ek API&#8217;n\u0131n davran\u0131\u015f\u0131n\u0131 do\u011fru bir \u015fekilde yans\u0131tmad\u0131\u011f\u0131nda, bu avantajlar h\u0131zla kabusa d\u00f6n\u00fc\u015febilir. CI boru hatt\u0131n\u0131n ye\u015fil yanmas\u0131yla gelen yanl\u0131\u015f pozitifler, \u00fcretim ortam\u0131nda beklenmedik hatalara, geli\u015ftirici g\u00fcveninin kayb\u0131na ve uzun s\u00fcren hata ay\u0131klama s\u00fcre\u00e7lerine yol a\u00e7abilir.<\/p>\n<p>Bu deneyimden \u00e7\u0131kar\u0131lacak en \u00f6nemli ders, mock&#8217;lar\u0131n sadece bir ara\u00e7 oldu\u011fu ve di\u011fer t\u00fcm kod varl\u0131klar\u0131 gibi d\u00fczenli bak\u0131m, do\u011frulama ve otomasyon gerektirdi\u011fidir. S\u00f6zle\u015fme testleri, OpenAPI\/Swagger spesifikasyonlar\u0131ndan mock \u00fcretimi, dinamik mock servisleri ve s\u00fcrekli entegrasyon boru hatt\u0131na derinlemesine entegrasyon gibi stratejiler, mock&#8217;lar\u0131n\u0131z\u0131n do\u011frulu\u011funu sa\u011flaman\u0131n anahtar\u0131d\u0131r. Mock&#8217;lar\u0131n\u0131z\u0131 &#8220;canl\u0131&#8221; tutarak, CI\/CD boru hatt\u0131n\u0131z\u0131n ger\u00e7ek bir kalite g\u00fcvencesi mekanizmas\u0131 olmas\u0131n\u0131 sa\u011flayabilir, geli\u015ftirme h\u0131z\u0131n\u0131z\u0131 koruyabilir ve son kullan\u0131c\u0131lar\u0131n\u0131za daha g\u00fcvenilir \u00fcr\u00fcnler sunabilirsiniz.<\/p>\n<h3>S\u0131k\u00e7a Sorulan Sorular (SSS)<\/h3>\n<h4>1. API mock&#8217;lama neden bu kadar \u00f6nemli?<\/h4>\n<p>API mock&#8217;lama, harici ba\u011f\u0131ml\u0131l\u0131klar\u0131 (\u00fc\u00e7\u00fcnc\u00fc taraf API&#8217;lar\u0131) izole ederek test s\u00fcre\u00e7lerini h\u0131zland\u0131r\u0131r, maliyetleri d\u00fc\u015f\u00fcr\u00fcr ve CI\/CD boru hatt\u0131n\u0131n kararl\u0131l\u0131\u011f\u0131n\u0131 art\u0131r\u0131r. Ger\u00e7ek API&#8217;lar\u0131n yava\u015fl\u0131\u011f\u0131, maliyeti veya eri\u015filemezli\u011fi gibi sorunlar\u0131 ortadan kald\u0131rarak geli\u015ftiricilerin kendi kodlar\u0131na odaklanmas\u0131n\u0131 sa\u011flar.<\/p>\n<h4>2. Bir mock&#8217;un &#8220;yalan s\u00f6ylemesi&#8221; ne anlama gelir?<\/h4>\n<p>Bir mock&#8217;un &#8220;yalan s\u00f6ylemesi&#8221;, sim\u00fcle etti\u011fi ger\u00e7ek API&#8217;n\u0131n davran\u0131\u015f\u0131n\u0131, veri yap\u0131s\u0131n\u0131 veya hata senaryolar\u0131n\u0131 do\u011fru bir \u015fekilde yans\u0131tmamas\u0131 demektir. Bu durum, ger\u00e7ek API&#8217;n\u0131n de\u011fi\u015fmesi ancak mock&#8217;un g\u00fcncellenmemesi, eksik senaryolar\u0131n mock edilmesi veya mock&#8217;un a\u015f\u0131r\u0131 basitle\u015ftirilmesi gibi nedenlerle ortaya \u00e7\u0131kabilir.<\/p>\n<h4>3. Yalan s\u00f6yleyen bir mock&#8217;un CI\/CD boru hatt\u0131na etkisi nedir?<\/h4>\n<p>Yalan s\u00f6yleyen bir mock, CI boru hatt\u0131nda yanl\u0131\u015f pozitiflere (t\u00fcm testler ge\u00e7se bile kodun hatal\u0131 olmas\u0131) yol a\u00e7ar. Bu durum, hatal\u0131 kodun \u00fcretim ortam\u0131na ula\u015fmas\u0131na, geli\u015ftirici g\u00fcveninin sars\u0131lmas\u0131na ve hata ay\u0131klama s\u00fcre\u00e7lerinin uzamas\u0131na neden olur.<\/p>\n<h4>4. Mock&#8217;lar\u0131n do\u011frulu\u011funu nas\u0131l sa\u011flayabiliriz?<\/h4>\n<p>Mock&#8217;lar\u0131n do\u011frulu\u011funu sa\u011flamak i\u00e7in s\u00f6zle\u015fme testleri (Pact gibi), OpenAPI\/Swagger spesifikasyonlar\u0131ndan otomatik mock \u00fcretimi, dinamik mock servisleri (WireMock gibi), d\u00fczenli senkronizasyon ve otomasyon ara\u00e7lar\u0131 kullan\u0131labilir. Ayr\u0131ca, mock&#8217;lar\u0131n da kod gibi versiyonlanmas\u0131 ve d\u00fczenli olarak g\u00f6zden ge\u00e7irilmesi \u00f6nemlidir.<\/p>\n<h4>5. S\u00f6zle\u015fme testleri (Contract Testing) mock&#8217;larla nas\u0131l ili\u015fkilidir?<\/h4>\n<p>S\u00f6zle\u015fme testleri, mock&#8217;lar\u0131n do\u011frulu\u011funu sa\u011flaman\u0131n en etkili yollar\u0131ndan biridir. Bu testler, uygulaman\u0131z\u0131n (t\u00fcketici) harici bir API&#8217;dan (sa\u011flay\u0131c\u0131) bekledi\u011fi s\u00f6zle\u015fmeyi tan\u0131mlar. Bu s\u00f6zle\u015fme hem mock&#8217;lar\u0131n\u0131z\u0131 olu\u015fturmak hem de ger\u00e7ek API&#8217;n\u0131n bu s\u00f6zle\u015fmeye uydu\u011funu do\u011frulamak i\u00e7in kullan\u0131l\u0131r. B\u00f6ylece, mock&#8217;unuzun ger\u00e7ek API ile her zaman uyumlu kalmas\u0131 sa\u011flan\u0131r.<\/p>\n<p>#API #Mocklama #CI\/CD #Yaz\u0131l\u0131mGeli\u015ftirme #TestOtomasyonu #S\u00f6zle\u015fmeTesti #WebServisleri #DevOps<\/p>\n<div class=\"github-example-link\"><strong>\u00d6rnek kod:<\/strong> <a href=\"https:\/\/github.com\/fatihsoysalcom\/mock-lying-bitter-lesson\" target=\"_blank\" rel=\"noopener noreferrer\">github.com\/fatihsoysalcom\/mock-lying-bitter-lesson<\/a><\/div>\n","protected":false},"excerpt":{"rendered":"Yaz\u0131l\u0131m geli\u015ftirme s\u00fcre\u00e7lerinde harici ba\u011f\u0131ml\u0131l\u0131klar, \u00f6zellikle de \u00fc\u00e7\u00fcnc\u00fc taraf API&#8217;lar\u0131, s\u00fcrekli entegrasyon (CI) ve s\u00fcrekli teslimat (CD) boru hatlar\u0131m\u0131z i\u00e7in ciddi bir engel te\u015fkil edebilir.","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"csco_page_header_type":"","csco_page_load_nextpost":"","csco_page_subscribe_form":"","csco_page_contact_form":"","footnotes":""},"categories":[1],"tags":[],"class_list":{"0":"post-45719","1":"post","2":"type-post","3":"status-publish","4":"format-standard","6":"category-genel","7":"cs-entry","8":"cs-video-wrap"},"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v20.5 (Yoast SEO v25.3.1) - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>Tedarik\u00e7i API&#039;s\u0131n\u0131 Mock&#039;larken CI&#039;\u0131 Kurtarmak ve Mock&#039;un Bize Yalan S\u00f6ylemesi: Ac\u0131 Bir Ders - Kodlar\u0131n Gizemli D\u00fcnyas\u0131<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/fatihsoysal.com\/blog\/tedarikci-apisini-mocklarken-cii-kurtarmak-ve-mockun-bize-yalan-soylemesi-aci-bir-ders\/\" \/>\n<meta property=\"og:locale\" content=\"tr_TR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Tedarik\u00e7i API&#039;s\u0131n\u0131 Mock&#039;larken CI&#039;\u0131 Kurtarmak ve Mock&#039;un Bize Yalan S\u00f6ylemesi: Ac\u0131 Bir Ders\" \/>\n<meta property=\"og:description\" content=\"Yaz\u0131l\u0131m geli\u015ftirme s\u00fcre\u00e7lerinde harici ba\u011f\u0131ml\u0131l\u0131klar, \u00f6zellikle de \u00fc\u00e7\u00fcnc\u00fc taraf API&#039;lar\u0131, s\u00fcrekli entegrasyon (CI) ve s\u00fcrekli teslimat (CD) boru hatlar\u0131m\u0131z i\u00e7in ciddi bir engel te\u015fkil edebilir.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/fatihsoysal.com\/blog\/tedarikci-apisini-mocklarken-cii-kurtarmak-ve-mockun-bize-yalan-soylemesi-aci-bir-ders\/\" \/>\n<meta property=\"og:site_name\" content=\"Kodlar\u0131n Gizemli D\u00fcnyas\u0131\" \/>\n<meta property=\"article:published_time\" content=\"2026-11-16T06:11:09+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-11-16T06:11:46+00:00\" \/>\n<meta name=\"author\" content=\"Fatih Soysal\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Yazan:\" \/>\n\t<meta name=\"twitter:data1\" content=\"Fatih Soysal\" \/>\n\t<meta name=\"twitter:label2\" content=\"Tahmini okuma s\u00fcresi\" \/>\n\t<meta name=\"twitter:data2\" content=\"29 dakika\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/tedarikci-apisini-mocklarken-cii-kurtarmak-ve-mockun-bize-yalan-soylemesi-aci-bir-ders\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/tedarikci-apisini-mocklarken-cii-kurtarmak-ve-mockun-bize-yalan-soylemesi-aci-bir-ders\/\"},\"author\":{\"name\":\"Fatih Soysal\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\"},\"headline\":\"Tedarik\u00e7i API&#8217;s\u0131n\u0131 Mock&#8217;larken CI&#8217;\u0131 Kurtarmak ve Mock&#8217;un Bize Yalan S\u00f6ylemesi: Ac\u0131 Bir Ders\",\"datePublished\":\"2026-11-16T06:11:09+00:00\",\"dateModified\":\"2026-11-16T06:11:46+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/tedarikci-apisini-mocklarken-cii-kurtarmak-ve-mockun-bize-yalan-soylemesi-aci-bir-ders\/\"},\"wordCount\":5652,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\"},\"inLanguage\":\"tr\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/fatihsoysal.com\/blog\/tedarikci-apisini-mocklarken-cii-kurtarmak-ve-mockun-bize-yalan-soylemesi-aci-bir-ders\/#respond\"]}],\"copyrightYear\":\"2026\",\"copyrightHolder\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#organization\"}},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/tedarikci-apisini-mocklarken-cii-kurtarmak-ve-mockun-bize-yalan-soylemesi-aci-bir-ders\/\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/tedarikci-apisini-mocklarken-cii-kurtarmak-ve-mockun-bize-yalan-soylemesi-aci-bir-ders\/\",\"name\":\"Tedarik\u00e7i API's\u0131n\u0131 Mock'larken CI'\u0131 Kurtarmak ve Mock'un Bize Yalan S\u00f6ylemesi: Ac\u0131 Bir Ders - Kodlar\u0131n Gizemli D\u00fcnyas\u0131\",\"isPartOf\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#website\"},\"datePublished\":\"2026-11-16T06:11:09+00:00\",\"dateModified\":\"2026-11-16T06:11:46+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/tedarikci-apisini-mocklarken-cii-kurtarmak-ve-mockun-bize-yalan-soylemesi-aci-bir-ders\/#breadcrumb\"},\"inLanguage\":\"tr\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/fatihsoysal.com\/blog\/tedarikci-apisini-mocklarken-cii-kurtarmak-ve-mockun-bize-yalan-soylemesi-aci-bir-ders\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/tedarikci-apisini-mocklarken-cii-kurtarmak-ve-mockun-bize-yalan-soylemesi-aci-bir-ders\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Anasayfa\",\"item\":\"https:\/\/fatihsoysal.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Tedarik\u00e7i API&#8217;s\u0131n\u0131 Mock&#8217;larken CI&#8217;\u0131 Kurtarmak ve Mock&#8217;un Bize Yalan S\u00f6ylemesi: Ac\u0131 Bir Ders\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#website\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/\",\"name\":\"Fatihsoysal.com\",\"description\":\"Blog - Yaz\u0131l\u0131m D\u00fcnyas\u0131 Tecr\u00fcbelerim\",\"publisher\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/fatihsoysal.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"tr\"},{\"@type\":[\"Person\",\"Organization\"],\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\",\"name\":\"Fatih Soysal\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"tr\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png\",\"contentUrl\":\"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png\",\"width\":512,\"height\":512,\"caption\":\"Fatih Soysal\"},\"logo\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/\"},\"description\":\"Kullan\u0131m ve kodlama m\u00fckemmeliyetini odak alan uygulamalar olu\u015fturma deneyimine sahip, profesyonel olarak 15+ y\u0131l \u00fczeri deneyime sahip bir yaz\u0131l\u0131m m\u00fchendisi.\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/author\/fatihsoysal\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Tedarik\u00e7i API's\u0131n\u0131 Mock'larken CI'\u0131 Kurtarmak ve Mock'un Bize Yalan S\u00f6ylemesi: Ac\u0131 Bir Ders - Kodlar\u0131n Gizemli D\u00fcnyas\u0131","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/fatihsoysal.com\/blog\/tedarikci-apisini-mocklarken-cii-kurtarmak-ve-mockun-bize-yalan-soylemesi-aci-bir-ders\/","og_locale":"tr_TR","og_type":"article","og_title":"Tedarik\u00e7i API's\u0131n\u0131 Mock'larken CI'\u0131 Kurtarmak ve Mock'un Bize Yalan S\u00f6ylemesi: Ac\u0131 Bir Ders","og_description":"Yaz\u0131l\u0131m geli\u015ftirme s\u00fcre\u00e7lerinde harici ba\u011f\u0131ml\u0131l\u0131klar, \u00f6zellikle de \u00fc\u00e7\u00fcnc\u00fc taraf API'lar\u0131, s\u00fcrekli entegrasyon (CI) ve s\u00fcrekli teslimat (CD) boru hatlar\u0131m\u0131z i\u00e7in ciddi bir engel te\u015fkil edebilir.","og_url":"https:\/\/fatihsoysal.com\/blog\/tedarikci-apisini-mocklarken-cii-kurtarmak-ve-mockun-bize-yalan-soylemesi-aci-bir-ders\/","og_site_name":"Kodlar\u0131n Gizemli D\u00fcnyas\u0131","article_published_time":"2026-11-16T06:11:09+00:00","article_modified_time":"2026-11-16T06:11:46+00:00","author":"Fatih Soysal","twitter_card":"summary_large_image","twitter_misc":{"Yazan:":"Fatih Soysal","Tahmini okuma s\u00fcresi":"29 dakika"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/fatihsoysal.com\/blog\/tedarikci-apisini-mocklarken-cii-kurtarmak-ve-mockun-bize-yalan-soylemesi-aci-bir-ders\/#article","isPartOf":{"@id":"https:\/\/fatihsoysal.com\/blog\/tedarikci-apisini-mocklarken-cii-kurtarmak-ve-mockun-bize-yalan-soylemesi-aci-bir-ders\/"},"author":{"name":"Fatih Soysal","@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1"},"headline":"Tedarik\u00e7i API&#8217;s\u0131n\u0131 Mock&#8217;larken CI&#8217;\u0131 Kurtarmak ve Mock&#8217;un Bize Yalan S\u00f6ylemesi: Ac\u0131 Bir Ders","datePublished":"2026-11-16T06:11:09+00:00","dateModified":"2026-11-16T06:11:46+00:00","mainEntityOfPage":{"@id":"https:\/\/fatihsoysal.com\/blog\/tedarikci-apisini-mocklarken-cii-kurtarmak-ve-mockun-bize-yalan-soylemesi-aci-bir-ders\/"},"wordCount":5652,"commentCount":0,"publisher":{"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1"},"inLanguage":"tr","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/fatihsoysal.com\/blog\/tedarikci-apisini-mocklarken-cii-kurtarmak-ve-mockun-bize-yalan-soylemesi-aci-bir-ders\/#respond"]}],"copyrightYear":"2026","copyrightHolder":{"@id":"https:\/\/fatihsoysal.com\/blog\/#organization"}},{"@type":"WebPage","@id":"https:\/\/fatihsoysal.com\/blog\/tedarikci-apisini-mocklarken-cii-kurtarmak-ve-mockun-bize-yalan-soylemesi-aci-bir-ders\/","url":"https:\/\/fatihsoysal.com\/blog\/tedarikci-apisini-mocklarken-cii-kurtarmak-ve-mockun-bize-yalan-soylemesi-aci-bir-ders\/","name":"Tedarik\u00e7i API's\u0131n\u0131 Mock'larken CI'\u0131 Kurtarmak ve Mock'un Bize Yalan S\u00f6ylemesi: Ac\u0131 Bir Ders - Kodlar\u0131n Gizemli D\u00fcnyas\u0131","isPartOf":{"@id":"https:\/\/fatihsoysal.com\/blog\/#website"},"datePublished":"2026-11-16T06:11:09+00:00","dateModified":"2026-11-16T06:11:46+00:00","breadcrumb":{"@id":"https:\/\/fatihsoysal.com\/blog\/tedarikci-apisini-mocklarken-cii-kurtarmak-ve-mockun-bize-yalan-soylemesi-aci-bir-ders\/#breadcrumb"},"inLanguage":"tr","potentialAction":[{"@type":"ReadAction","target":["https:\/\/fatihsoysal.com\/blog\/tedarikci-apisini-mocklarken-cii-kurtarmak-ve-mockun-bize-yalan-soylemesi-aci-bir-ders\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/fatihsoysal.com\/blog\/tedarikci-apisini-mocklarken-cii-kurtarmak-ve-mockun-bize-yalan-soylemesi-aci-bir-ders\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Anasayfa","item":"https:\/\/fatihsoysal.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Tedarik\u00e7i API&#8217;s\u0131n\u0131 Mock&#8217;larken CI&#8217;\u0131 Kurtarmak ve Mock&#8217;un Bize Yalan S\u00f6ylemesi: Ac\u0131 Bir Ders"}]},{"@type":"WebSite","@id":"https:\/\/fatihsoysal.com\/blog\/#website","url":"https:\/\/fatihsoysal.com\/blog\/","name":"Fatihsoysal.com","description":"Blog - Yaz\u0131l\u0131m D\u00fcnyas\u0131 Tecr\u00fcbelerim","publisher":{"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/fatihsoysal.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"tr"},{"@type":["Person","Organization"],"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1","name":"Fatih Soysal","image":{"@type":"ImageObject","inLanguage":"tr","@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/","url":"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png","contentUrl":"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png","width":512,"height":512,"caption":"Fatih Soysal"},"logo":{"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/"},"description":"Kullan\u0131m ve kodlama m\u00fckemmeliyetini odak alan uygulamalar olu\u015fturma deneyimine sahip, profesyonel olarak 15+ y\u0131l \u00fczeri deneyime sahip bir yaz\u0131l\u0131m m\u00fchendisi.","url":"https:\/\/fatihsoysal.com\/blog\/author\/fatihsoysal\/"}]}},"yoast_meta":{"yoast_wpseo_title":"","yoast_wpseo_metadesc":"","yoast_wpseo_canonical":""},"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts\/45719","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/comments?post=45719"}],"version-history":[{"count":1,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts\/45719\/revisions"}],"predecessor-version":[{"id":45720,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts\/45719\/revisions\/45720"}],"wp:attachment":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/media?parent=45719"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/categories?post=45719"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/tags?post=45719"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}