<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Tuğkan Boz on Medium]]></title>
        <description><![CDATA[Stories by Tuğkan Boz on Medium]]></description>
        <link>https://medium.com/@tugkan.boz?source=rss-6956c6cfeac0------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*q-2qbYlV8rj4-KWi7FQwBw.png</url>
            <title>Stories by Tuğkan Boz on Medium</title>
            <link>https://medium.com/@tugkan.boz?source=rss-6956c6cfeac0------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 01:25:29 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@tugkan.boz/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Test Ortamında Kaos Tasarımı: Controlled Failure’lar ve Yük Testi
Dayanıklılığı Ölçmenin Yeni…]]></title>
            <link>https://medium.com/@tugkan.boz/test-ortam%C4%B1nda-kaos-tasar%C4%B1m%C4%B1-controlled-failurelar-ve-y%C3%BCk-testi-dayan%C4%B1kl%C4%B1l%C4%B1%C4%9F%C4%B1-%C3%B6l%C3%A7menin-yeni-ae23c4c28e5b?source=rss-6956c6cfeac0------2</link>
            <guid isPermaLink="false">https://medium.com/p/ae23c4c28e5b</guid>
            <category><![CDATA[load-testing]]></category>
            <category><![CDATA[chaos-engineering]]></category>
            <category><![CDATA[locust]]></category>
            <dc:creator><![CDATA[Tuğkan Boz]]></dc:creator>
            <pubDate>Wed, 09 Jul 2025 10:30:56 GMT</pubDate>
            <atom:updated>2025-07-09T10:30:56.308Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Test Ortamında Kaos Tasarımı: Controlled Failure’lar ve Yük Testi<br></strong><em>Dayanıklılığı Ölçmenin Yeni Boyutu</em></p><p>İyi planlanmış bir yük testi, ne kadar yük kaldırdığınızı göstermenin ötesine geçer. Gerçek dünya asla ideal koşullar sunmaz; trafik aniden artar, servisler yavaşlar, queue’lar dolar. Bu makalede, yük testlerinize “kaos” katmanını nasıl ekleyebileceğinizi, sisteminizin beklenmedik durumlar karşısındaki davranışını nasıl gözlemleyeceğinizi ve gerçekten dayanıklı bir altyapıya nasıl ulaşacağınızı göstereceğiz.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9gFj87A-mc_WBy_xW2X9-A.png" /></figure><p><strong>Neden Sadece Rakamlar Yetmez?<br></strong>Standart bir yük testi raporu genellikle şunları içerir:<br><strong>Toplam İstek</strong>: 1.000<br><strong>Başarı Oranı</strong>: %98<br><strong>Ortalama Yanıt Süresi</strong>: 450 ms</p><p>Bu metrikler önemli olsa da, sisteminizin gerçek sınırlarını belirlemez. Gerçek dünyada:<br>Altyapı bileşenleri %90 CPU kullanımıyla tıkanabilir.<br>Cache çökerse yanıt süreleri fırlayabilir.<br>Dış servislerdeki küçük bir yavaşlama tüm akışı etkileyebilir.</p><p>İşte bu yüzden sadece “kaç kullanıcıyı kaldırıyoruz?” değil, “sistem bozulduğunda nasıl tepki veriyor?” sorusuna odaklanmalısınız.</p><p>Chaos Engineering ise sisteminizi gerçek dünya belirsizliklerine karşı sınar: Bilinçli olarak hatalar, gecikmeler veya kaynak kesintileri oluşturarak, bu aksaklıklar anında altyapınızın nasıl tepki verdiğini gözlemlersiniz.</p><p><strong>Controlled Failure ile Kaosu Yönetmek<br>Controlled Failure</strong>, sistemin kritik parçalarını bilinçli olarak zorlayarak veya bozulur gibi davranarak altyapınızın dayanıklılığını test etme yöntemidir. Yük testine şu senaryoları ekleyerek uygulayabilirsiniz:<br><strong>Network Latency Simülasyonu<br>Yavaşlayan Servis Yanıtları<br>Queue Doluluğu ve Gecikmeli İşleme<br>Throttling &amp; Backpressure Testleri<br>Dış Servislerin Geçici Kesintisi</strong></p><p>Bu senaryolarla, sadece yüksek trafik göndermek yerine, sisteminizin “kritik an”lardaki davranışını ölçmüş olursunuz.</p><p><strong>Uygulama Adımları</strong></p><p><strong>Locust ile Gecikmeli Endpoint Testi<br></strong>Aşağıdaki örnek, /api/checkout uç noktasını 5 saniyenin üzerinde yanıt verdiğinde hata kaydı oluşturur:</p><pre>from locust import HttpUser, task<br><br>class WebsiteUser(HttpUser):<br>    @task<br>    def delayed_checkout(self):<br>        with self.client.get(&quot;/api/checkout&quot;, timeout=10, catch_response=True) as response:<br>            if response.elapsed.total_seconds() &gt; 5:<br>                response.failure(&quot;Checkout too slow&quot;)</pre><p>Bu sayede yavaşlama noktası net bir şekilde <strong>belirlenir</strong> ve darboğazın kaynağı <strong>ortaya çıkarılır</strong>.</p><p><strong>Dış Servis Zayıflığı Senaryoları</strong><br>Cache katmanları ve üçüncü parti API’ler için controlled failure senaryoları şöyle oluşturulabilir:<br>1. Cache yanıt süresi normalde beş milisaniye iken test ortamında üç yüz milisaniyeye yükseltilmeli<br>2. Üçüncü parti servis her çağrıda iki ile beş saniye arasında rastgele gecikmeli yanıt vermeli (Mock servisler aracılığıyla yapılabilir)<br>3. Bazı isteklerde kasıtlı olarak 500 Internal Server Error veya timeout simüle edilmeli<br>Bu şartlar altında fallback mekanizmalarının, retry stratejilerinin ve hata bildirimlerinin doğru şekilde tetiklenip tetiklenmediği doğrulanmalı.</p><p><strong>Queue ve Mesajlaşma Gecikmeleri<br></strong>Messaging queue kullanılan sistemlerde aşağıdaki durumlar test edilmeli:<br>1. Consumer işlemi kasıtlı olarak yavaşlatılmalı<br>2. Queue birikimi artırılarak backpressure tetiklenmeli<br>3. Hatalı mesajların dead-letter kuyruğuna yönlendirilme mantığı denenmeli<br>Böylece queue doluluğunun sistem performansına etkisi ölçülmeli ve kritik eşik değerleri belirlenmeli.</p><p><strong>Controlled Failure’ın Faydaları<br></strong>Gerçekçi trafik profilleri simüle edilerek ani trafik sıçramalarına karşı hazırlık sağlanır<br>Altyapı sorunları yavaşlama aşamasında tespit edilerek önleyici aksiyonlar planlanır<br>Kritik anlarda toplanan log ve metric verileri gerçek değeri kazanır<br>Retry, fallback ve circuit breaker yapılarının etkinliği kaos anında test edilerek güvence altına alınır.</p><h4><strong>Sonuç</strong></h4><p>Kaos mühendisliği adımlarını yük testinize dahil ederek, sisteminizin yalnızca yük taşıma kapasitesini değil; beklenmedik aksaklıklar karşısındaki esneklik ve toparlanma mekanizmalarını da ölçmüş olacaksınız. Bu sayede:<br><strong>Gerçekçi Görünürlük:</strong> Altyapınızın en zayıf noktalarını ortaya çıkararak, “gerçek dünyada ne olur?” sorusuna yanıt bulabilirsiniz.<br><strong>Hedefe Yönelik İyileştirme:</strong> Ortaya çıkan darboğaz ve hatalara odaklanarak retry, fallback ve circuit breaker yapılarını önceliklendirebilirsiniz.<br><strong>Periyodik Doğrulama:</strong> Kaos testlerini belirli aralıklarla (örneğin aylık veya özel günlerden önce) tekrarlayarak, sistem dayanıklılığını güncel tutabilirsiniz.<br><strong>Ekip Dayanıklılığı:</strong> Test senaryoları ve elde edilen sonuçları dökümante edip ekip içinde paylaşarak, herkesin hazırlıklı ve bilinçli olmasını sağlayabilirsiniz.</p><p>Bu adımları düzenli bir şekilde uyguladığınızda, altyapınız rastgele hatalara karşı daha dayanıklı hale gelecek ve kritik durumlarda bile kullanıcı deneyimini koruyabileceksiniz.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ae23c4c28e5b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Enhancing Test Automation with AI: Standardization and Efficiency through CursorRules]]></title>
            <link>https://medium.com/@tugkan.boz/enhancing-test-automation-with-ai-standardization-and-efficiency-through-cursorrules-fda45bbbb202?source=rss-6956c6cfeac0------2</link>
            <guid isPermaLink="false">https://medium.com/p/fda45bbbb202</guid>
            <category><![CDATA[cursor]]></category>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[automation-testing]]></category>
            <category><![CDATA[cursorrule]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Tuğkan Boz]]></dc:creator>
            <pubDate>Sun, 29 Dec 2024 18:55:39 GMT</pubDate>
            <atom:updated>2024-12-30T04:11:56.209Z</atom:updated>
            <content:encoded><![CDATA[<p><a href="https://github.com/tugkanboz/awesome-cursorrules/edit/main/README.md">https://github.com/tugkanboz/awesome-cursorrules</a></p><p>In the software development world, AI-assisted development tools are becoming increasingly important. One of these tools, Cursor IDE, offers a notable approach, especially in test automation. Today, we’ll explore .cursorrules files and their implementation in the awesome-cursorrules project, which make test automation more efficient and standardized.</p><p>What are Cursor IDE and .cursorrules?</p><p>Cursor is an AI-powered modern integrated development environment. One of its most significant features is the ability to train its AI assistant using special configuration files called .cursorrules. These files contain rules that determine how artificial intelligence should behave during the test automation development process.</p><p>The Awesome CursorRules Project</p><p>Awesome CursorRules is an open-source project that brings together .cursorrules configurations for test automation. This project hosts customized AI rules for popular test automation frameworks such as Selenium, Cypress, Playwright, and Appium.</p><p>Benefits Provided by the Project</p><p>Intelligent Code Understanding In test automation projects, AI better understands your code by learning project-specific patterns and conventions. It acts like an experienced team member and adapts to your development process.</p><p>Code Style Standardization By automatically adhering to defined coding standards, it ensures consistency in generated code. This significantly reduces time spent on code review processes.</p><p>Project Context Awareness AI understands your project’s architecture, used libraries, and project-specific constraints, providing context-appropriate suggestions.</p><p>Implementation and Usage</p><p>The .cursorrules file resides in your project’s root directory and contains these core components:</p><ul><li>Basic coding standards</li><li>Project-specific requirements</li><li>Common patterns</li><li>Preferred approaches</li></ul><p>For example, a .cursorrules file for Selenium Java might include rules about implementing the Page Object Model pattern, defining element locators, and naming test methods.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BcPQEL6jZbWDFcC_w1CtgQ.png" /></figure><p>Benefits for Different Stakeholders</p><p>For Individual Developers:</p><ul><li>Personalized code suggestions aligned with project standards</li><li>Faster development cycles with AI assistance</li><li>Reduced context switching during development</li></ul><p>For Teams:</p><ul><li>Consistent coding practices across members</li><li>Easier onboarding process for new team members</li><li>Shared understanding of automation standards</li></ul><p>For Projects:</p><ul><li>Maintained code quality through standardization</li><li>Documented best practices in machine-readable format</li><li>Scalable test automation development process</li></ul><p>Best Practices for Implementation</p><p>Structure:</p><ul><li>Organize rules in logical categories</li><li>Use clear, descriptive rule definitions</li><li>Include practical examples where necessary</li></ul><p>Maintenance:</p><ul><li>Regular updates as the project evolves</li><li>Version control for rule modifications</li><li>Team review for major changes</li></ul><p>Conclusion and Recommendations</p><p>The Awesome CursorRules project serves as a valuable resource for teams looking to make their test automation development processes more efficient and standardized. By contributing to the project or creating your own .cursorrules files, you can enhance your AI-assisted test automation development processes.</p><p>This approach provides an effective solution, particularly in large-scale test automation projects, ensuring consistency and accelerating the adaptation process for new team members. As AI continues to evolve in software development, tools like .cursorrules will become increasingly essential for maintaining quality and efficiency in test automation.</p><p>The project’s open-source nature encourages collaboration and continuous improvement, making it a living resource that evolves with the needs of the test automation community. Whether you’re starting a new test automation project or looking to improve an existing one, implementing .cursorrules can significantly enhance your development workflow and team productivity.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fda45bbbb202" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Cypress Element Seçimleri]]></title>
            <link>https://medium.com/@tugkan.boz/cypress-element-se%C3%A7imleri-9483d0b2d103?source=rss-6956c6cfeac0------2</link>
            <guid isPermaLink="false">https://medium.com/p/9483d0b2d103</guid>
            <dc:creator><![CDATA[Tuğkan Boz]]></dc:creator>
            <pubDate>Tue, 03 Sep 2024 21:01:53 GMT</pubDate>
            <atom:updated>2024-09-03T21:01:53.699Z</atom:updated>
            <content:encoded><![CDATA[<p>Bu yazıda, Cypress kullanarak farklı element seçim seçeneklerini nasıl kullanabileceğinizi anlatacağız. Örnekleri takip ederek, Cypress ile elementlerin nasıl seçilebileceğini ve testlerinizde kullanılabileceğini inceleyeceğiz.</p><p>Aşağıdaki kod bloğundaki elementlerin seçimlerini inceleyeceğiz.</p><pre>&lt;div id=&quot;page-wrap&quot;&gt;<br>  <br>  &lt;h1 class=&quot;equality&quot;&gt;Class Equals&lt;/h1&gt;<br>  <br>  &lt;h1 class=&quot;xxxcontainsxxx&quot;&gt;Class Contains&lt;/h1&gt;<br>  <br>  &lt;h1 class=&quot;begin-4fswt&quot;&gt;Class Begins&lt;/h1&gt;<br>  <br>  &lt;h1 class=&quot;5fs35-ends&quot;&gt;Class Ends&lt;/h1&gt;<br>  <br>  &lt;h1 class=&quot;friend space sandwich&quot;&gt;Class Space Separated&lt;/h1&gt;<br>  <br>  &lt;h1 title=&quot;Important note&quot; class=&quot;handsome&quot;&gt;Multiple Attributes&lt;/h1&gt;<br>  <br>  &lt;h1&gt;&lt;a href=&quot;#&quot;&gt;HREF anchor link test&lt;/a&gt;&lt;/h1&gt;<br>      <br> &lt;/div&gt;</pre><p>Cypress’te, bir elementi seçmek için farklı yöntemler kullanabilirsiniz:</p><ul><li>cy.get(): Bu metodu kullanarak, DOM&#39;da bir elementi seçebilirsiniz. Örneğin:</li></ul><pre>cy.get(&#39;#page-wrap&#39;)  // Id&#39;si &#39;page-wrap&#39; olan elementi seçer<br>cy.get(&#39;.equality&#39;)   // Class&#39;ı &#39;equality&#39; olan elementleri seçer</pre><ul><li>cy.contains(): Bu metodu kullanarak, bir elementin içinde belirli bir metin içeren elementleri seçebilirsiniz. Örneğin:</li></ul><pre>cy.contains(&#39;HREF anchor link test&#39;)  // &#39;HREF anchor link test&#39; metnini içeren elementleri seçer</pre><ul><li>Cypress’te, ayrıca bir elementi seçmek için CSS selector’larını da kullanabilirsiniz. Örneğin:</li></ul><pre>//Class adı &#39;equality&#39; olan elementleri seçer<br>cy.get(&#39;h1[class=equality]&#39;)<br><br>//Class adında &#39;contains&#39; içeren elementleri seçer<br>cy.get(&#39;h1[class*=contains]&#39;)<br><br>//Class adı &#39;begins&#39; ile başlayan elementleri seçer<br>cy.get(&#39;h1[class^=begin]&#39;)<br><br>//Class adı &#39;ends&#39; ile biten elementleri seçer<br>cy.get(&#39;h1[class$=ends]&#39;)<br><br>//Class adı &#39;space&#39; olan ve boşlukla ayrılmış elementleri seçer <br>cy.get(&#39;h1[class~=space]&#39;)<br><br>//Class adı &#39;handsome&#39; olan ve title adı &#39;important&#39; ile başlayan elementleri seçer<br>cy.get(&#39;[class=&quot;handsome&quot;][title^=&quot;Important&quot;]&#39;)</pre><p>Referans:<br><a href="https://css-tricks.com/attribute-selectors/">https://css-tricks.com/attribute-selectors/</a><br><a href="https://docs.cypress.io/api/commands/get#Selector">https://docs.cypress.io/api/commands/get#Selector</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9483d0b2d103" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mountebank: An In-depth Look at Inject and Behavior]]></title>
            <link>https://medium.com/@tugkan.boz/mountebank-an-in-depth-look-at-inject-and-behavior-25ad696e612c?source=rss-6956c6cfeac0------2</link>
            <guid isPermaLink="false">https://medium.com/p/25ad696e612c</guid>
            <dc:creator><![CDATA[Tuğkan Boz]]></dc:creator>
            <pubDate>Mon, 02 Sep 2024 21:02:48 GMT</pubDate>
            <atom:updated>2024-09-02T21:02:48.564Z</atom:updated>
            <content:encoded><![CDATA[<p>In this article, we’ll dive deep into two crucial features of Mountebank: <strong>inject</strong> and <strong>behavior</strong>. These two features are key to making your mock services more powerful and flexible. Let’s get started!</p><p><strong>1. Mountebank Inject</strong></p><ul><li>1.1 What is Inject?</li></ul><p>Inject is one of the most powerful features of Mountebank. This feature allows your mock service to produce dynamic responses. Using inject, you can create customized responses based on incoming requests, fetch data from external sources, and simulate complex business logic.</p><ul><li>1.2 How Does Inject Work?</li></ul><p>Inject works through customized templates. These templates take the incoming request as a parameter and dynamically generate the response. Here’s a simple example:</p><pre>{<br> &quot;statusCode&quot;: 200,<br> &quot;headers&quot;: { &quot;Content-Type&quot;: &quot;application/json&quot; },<br> &quot;body&quot;: {<br> &quot;message&quot;: &quot;Hello, &lt;%= request.query.name || &#39;Guest&#39; %&gt;!&quot;,<br> &quot;timestamp&quot;: &quot;&lt;%= new Date().toISOString() %&gt;&quot;<br> }<br>}</pre><p>In this example, the inject template takes a name from the query parameter and returns a personalized message. The expressions inside <strong>&lt;%= %&gt;</strong> are evaluated dynamically, and their results are included in the response.</p><ul><li>1.3 Advantages of Inject</li></ul><p>1. Dynamic Responses: You can better simulate real-world scenarios.<br>2. State Management: You can store data across sessions using the `state` variable within the template.<br>3. External Integration: You can integrate with databases or other APIs.<br>4. Complex Logic: You can mimic complex business logic found in real services.</p><ul><li>1.4 Advanced Inject Example</li></ul><p>Here’s a more complex inject example:</p><pre>&lt;%<br>  const db = {<br>    findUser: (id) =&gt; {<br>      const users = [<br>        { id: 1, name: &#39;John Doe&#39;, email: &#39;john@example.com&#39; },<br>        { id: 2, name: &#39;Jane Doe&#39;, email: &#39;jane@example.com&#39; }<br>      ];<br>      return users.find(u =&gt; u.id === parseInt(id));<br>    }<br>  };<br><br>  const userId = request.headers[&#39;User-Id&#39;];<br>  const user = userId ? db.findUser(userId) : null;<br>  <br>  // Save user&#39;s last access<br>  state.lastAccess = state.lastAccess || {};<br>  if (user) {<br>    state.lastAccess[userId] = new Date().toISOString();<br>  }<br>%&gt;<br><br>{<br>  &quot;statusCode&quot;: &lt;%= user ? 200 : (userId ? 404 : 401) %&gt;,<br>  &quot;headers&quot;: { &quot;Content-Type&quot;: &quot;application/json&quot; },<br>  &quot;body&quot;: {<br>    &lt;% if (!userId) { %&gt;<br>      &quot;error&quot;: &quot;Unauthorized&quot;<br>    &lt;% } else if (!user) { %&gt;<br>      &quot;error&quot;: &quot;User not found&quot;<br>    &lt;% } else { %&gt;<br>      &quot;user&quot;: {<br>        &quot;id&quot;: &lt;%= user.id %&gt;,<br>        &quot;name&quot;: &quot;&lt;%= user.name %&gt;&quot;,<br>        &quot;email&quot;: &quot;&lt;%= user.email %&gt;&quot;<br>      },<br>      &quot;lastAccess&quot;: &quot;&lt;%= state.lastAccess[userId] %&gt;&quot;<br>    &lt;% } %&gt;<br>  }<br>}</pre><p>In this example, we’re using a mock external database, handling error cases, and managing state. Within the <strong>&lt;% %&gt;</strong> blocks at the beginning of the template, we can execute JavaScript code, define variables, and implement complex logic.</p><p><strong>2. Mountebank Behavior</strong></p><ul><li>2.1 What is Behavior?</li></ul><p>Behavior defines the general conduct of your mock service. This includes how responses are generated, how delays are simulated, and how error conditions are handled.</p><ul><li>2.2 Types of Behavior</li></ul><p>1. Stub: Returns fixed responses.<br>2. Proxy: Forwards requests to a real service and records responses.<br>3. Inject: The dynamic response generation mechanism we explained above.<br>4. Fault: Simulates error conditions such as network errors or timeouts.</p><ul><li>2.3 Behavior Example</li></ul><p>Here’s an imposter configuration that includes different types of behavior:</p><pre>{<br>  &quot;port&quot;: 4545,<br>  &quot;protocol&quot;: &quot;http&quot;,<br>  &quot;stubs&quot;: [<br>    {<br>      &quot;predicates&quot;: [{ &quot;equals&quot;: { &quot;path&quot;: &quot;/api/users&quot; } }],<br>      &quot;responses&quot;: [<br>        {<br>          &quot;is&quot;: {<br>            &quot;statusCode&quot;: 200,<br>            &quot;headers&quot;: { &quot;Content-Type&quot;: &quot;application/json&quot; },<br>            &quot;body&quot;: &lt;%-<br>              JSON.stringify([<br>                { &quot;id&quot;: 1, &quot;name&quot;: &quot;John Doe&quot; },<br>                { &quot;id&quot;: 2, &quot;name&quot;: &quot;Jane Doe&quot; }<br>              ])<br>            %&gt;<br>          }<br>        }<br>      ]<br>    },<br>    {<br>      &quot;predicates&quot;: [{ &quot;equals&quot;: { &quot;path&quot;: &quot;/api/slow&quot; } }],<br>      &quot;responses&quot;: [<br>        {<br>          &quot;is&quot;: { &quot;statusCode&quot;: 200, &quot;body&quot;: &quot;Slow response&quot; },<br>          &quot;behaviors&quot;: [{ &quot;wait&quot;: &lt;%= Math.floor(Math.random() * 2000) + 1000 %&gt; }]<br>        }<br>      ]<br>    },<br>    {<br>      &quot;predicates&quot;: [{ &quot;equals&quot;: { &quot;path&quot;: &quot;/api/error&quot; } }],<br>      &quot;responses&quot;: [<br>        {<br>          &quot;is&quot;: {<br>            &quot;statusCode&quot;: 500,<br>            &quot;body&quot;: &quot;Internal Server Error: &lt;%= new Date().toISOString() %&gt;&quot;<br>          }<br>        }<br>      ]<br>    },<br>    {<br>      &quot;predicates&quot;: [{ &quot;equals&quot;: { &quot;path&quot;: &quot;/api/dynamic&quot; } }],<br>      &quot;responses&quot;: [<br>        {<br>          &quot;inject&quot;: &quot;&lt;% <br>            function dynamicResponse(request) { <br>              return { <br>                body: &#39;Dynamic response at: &#39; + new Date().toISOString() <br>              }; <br>            } <br>          %&gt;&quot;<br>        }<br>      ]<br>    }<br>  ]<br>}</pre><p>In this configuration:<br>- For /api/users, we’re returning a fixed response (stub). The JSON data is dynamically generated.<br>- For /api/slow, we’re adding a random delay (between 1–3 seconds).<br>- For /api/error, we’re simulating an error response with a dynamic timestamp.<br>- For /api/dynamic, we’re defining an inject function that returns a response with the current timestamp each time it’s called.</p><p><strong>3. Inject vs. Behavior: When to Use Which?</strong></p><p>- Use Inject: For responses that require dynamic, state-dependent, or complex logic.<br>- Use Behavior: To define general service behavior, simulate delays, or test error scenarios.</p><h4>Conclusion</h4><p>Mountebank’s inject and behavior features allow you to make your mock services closer to real-world scenarios. While inject allows you to create dynamic and complex responses, behavior helps you shape the overall service conduct. By skillfully using these two features, you can significantly increase the quality and scope of your test scenarios.</p><p>Remember, creating a perfect mock service comes from understanding the behavior of real services well and accurately simulating these behaviors. With these powerful features of Mountebank, you can make your testing processes more efficient and effective.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=25ad696e612c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Streamlining Your Development Workflow: Shell Configuration and Docker Aliases]]></title>
            <link>https://medium.com/@tugkan.boz/streamlining-your-development-workflow-shell-configuration-and-docker-aliases-45edf993f6d2?source=rss-6956c6cfeac0------2</link>
            <guid isPermaLink="false">https://medium.com/p/45edf993f6d2</guid>
            <category><![CDATA[terminal-commands]]></category>
            <category><![CDATA[git]]></category>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[alias]]></category>
            <dc:creator><![CDATA[Tuğkan Boz]]></dc:creator>
            <pubDate>Sun, 01 Sep 2024 21:01:42 GMT</pubDate>
            <atom:updated>2024-09-01T21:01:42.172Z</atom:updated>
            <content:encoded><![CDATA[<p>In the world of software development, efficiency is key. In this article, we’ll explore how to set up your shell environment and create useful aliases, with a focus on Docker commands, git command, etc.</p><h4>Understanding Shell Configuration Files</h4><p>Depending on your operating system and preferred shell, you’ll be working with different configuration files. The two most common scenarios are:</p><p>1. <strong>Bash Shel</strong>l: Uses .bash_profile or .bashrc<br>2. <strong>Zsh (Z Shell)</strong>: Uses .zshrc</p><p><strong>Bash vs. Zsh</strong></p><p>- Bash has been the default shell on many Unix-based systems for years.<br>- Zsh, an extended version of Bash, has gained popularity due to its additional features and is now the default shell on macOS (since Catalina).</p><p>To check which shell you’re using, open a terminal and run:</p><pre><br>echo $SHELL</pre><p><strong>Setting Up Your Shell</strong></p><p>Regardless of which shell you’re using, the process of adding configurations is similar:</p><p>1. Open your shell configuration file in a text editor:<br> — For Bash: <em>nano ~/.bash_profile</em> or <em>nano ~/.bashrc</em><br> — For Zsh: <em>nano ~/.zshrc</em></p><p>2. Add your configurations, aliases, and functions to this file.</p><p>3. Save the file and exit the editor.</p><p>4. Apply the changes by running:<br> — <em>source ~/.bash_profile</em> (or <em>~/.bashrc</em>) for Bash<br> — <em>source ~/.zshrc</em> for Zsh</p><p><strong>The Power of Aliases</strong></p><p>Aliases are shorthand commands that can save you time and keystrokes. They’re particularly useful for long or frequently used commands.</p><p><strong>Docker Aliases</strong></p><p>Let’s look at some helpful Docker aliases:</p><pre><br># Navigation<br>alias ..=&quot;cd ..&quot;<br>alias ...=&quot;cd ../..&quot;<br>alias ....=&quot;cd ../../..&quot;<br>alias ~=&quot;cd ~&quot;<br>alias home=&quot;cd ~&quot;<br><br># List directories<br>alias ll=&quot;ls -la&quot;<br>alias la=&quot;ls -A&quot;<br>alias l=&quot;ls -CF&quot;<br><br># Git shortcuts<br>alias gs=&quot;git status&quot;<br>alias ga=&quot;git add&quot;<br>alias gc=&quot;git commit -m&quot;<br>alias gp=&quot;git push&quot;<br>alias gpl=&quot;git pull&quot;<br>alias gl=&quot;git log --oneline --graph --decorate&quot;<br><br># System<br>alias update=&quot;sudo apt update &amp;&amp; sudo apt upgrade -y&quot;  # For Ubuntu/Debian<br>alias brew-update=&quot;brew update &amp;&amp; brew upgrade&quot;  # For macOS<br>alias c=&quot;clear&quot;<br>alias h=&quot;history&quot;<br><br># Network<br>alias myip=&quot;curl http://ipecho.net/plain; echo&quot;<br>alias ports=&quot;netstat -tulanp&quot;<br><br># File operations<br>alias cp=&quot;cp -i&quot;                          # Confirm before overwriting<br>alias mv=&quot;mv -i&quot;                          # Confirm before overwriting<br>alias mkdir=&quot;mkdir -p&quot;                    # Create parent directories as needed<br><br># Grep with color<br>alias grep=&quot;grep --color=auto&quot;<br><br># Quick edit of config files<br>alias zshconfig=&quot;nano ~/.zshrc&quot;<br>alias bashconfig=&quot;nano ~/.bashrc&quot;<br><br># Python virtual environment<br>alias venv=&quot;python3 -m venv ./venv&quot;<br>alias activate=&quot;source ./venv/bin/activate&quot;<br><br># Docker (additional to those mentioned earlier)<br>alias dps=&quot;docker ps&quot;<br>alias dimg=&quot;docker images&quot;<br>alias drmi=&quot;docker rmi&quot;<br>alias dexec=&quot;docker exec -it&quot;</pre><p>These aliases cover a wide range of common tasks:</p><ol><li><strong>Navigation</strong>: Quickly move up directory levels or to the home directory.</li><li><strong>Directory Listing</strong>: Enhanced ls commands for different levels of detail.</li><li><strong>Git Operations</strong>: Streamlined commands for common Git actions.</li><li><strong>System Management</strong>: Easy updates and system information retrieval.</li><li><strong>Network</strong>: Check your public IP or list open ports.</li><li><strong>File Operations</strong>: Add safeguards to prevent accidental overwrites.</li><li><strong>Configuration</strong>: Quickly edit your shell configuration files.</li><li><strong>Development</strong>: Easily create and activate Python virtual environments.</li><li><strong>Docker</strong>: Additional Docker commands for container and image management.</li></ol><p>To use these aliases, add them to your shell configuration file and reload it.</p><h4>Conclusion</h4><p>Properly configuring your shell and utilizing aliases can significantly enhance your productivity, especially when working with complex tools like Docker. By implementing the Docker aliases we’ve discussed and following best practices for shell configuration, you’ll streamline your development workflow and save valuable time in your day-to-day tasks.</p><p>Remember, the key to an efficient development environment is continuous refinement. Don’t hesitate to modify these aliases or create new ones as your needs evolve. Happy coding!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=45edf993f6d2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[SQL API nedir?]]></title>
            <link>https://medium.com/cstech/sql-api-nedir-2e94b5a2cb24?source=rss-6956c6cfeac0------2</link>
            <guid isPermaLink="false">https://medium.com/p/2e94b5a2cb24</guid>
            <category><![CDATA[https]]></category>
            <category><![CDATA[query]]></category>
            <category><![CDATA[api]]></category>
            <category><![CDATA[integration-test]]></category>
            <category><![CDATA[sql]]></category>
            <dc:creator><![CDATA[Tuğkan Boz]]></dc:creator>
            <pubDate>Tue, 15 Feb 2022 16:48:01 GMT</pubDate>
            <atom:updated>2022-06-05T09:45:32.507Z</atom:updated>
            <content:encoded><![CDATA[<p>Bu yazı ÇiçekSepeti teknoloji ekibinin geliştirdiği SQL API’nin ne olduğunu ve nasıl kullanıldığını anlatmaktadır.</p><p>You can access the English version via <a href="https://medium.com/cstech/what-is-sql-api-ac789b624332">this link</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9DlfyrwvtExPnmFE82Ga3A.jpeg" /></figure><p>SQL API nedir?</p><ul><li>Database’e sorgu atmamızı sağlayan HTTP isteğidir. Projenin kaynak koduna buradan ulaşabilirsiniz: <a href="https://github.com/ciceksepetitech/sqlapi">SQL API</a>.</li></ul><p>SQL API hangi sorunu çözmektedir?</p><ul><li>Başarılı HTTP isteklerini gönderdikten sonra veritabanında bulunan kayıtları kontrol eder.<br>Örneğin: POST isteklerinde database’e atılan dataların kaydedildiğini, DELETE isteklerinde database’den dataların silindiğini kontrol eder.</li></ul><p>SQL API hangi database’leri destekler?</p><ul><li>MySQL</li><li>MsSQL</li><li>MongoDB</li></ul><p>SQL API nasıl kullanılır?</p><ul><li>Database’i oluşturduktan sonra test edilecek tool üzerinden(Postman, RestAssured, Insomnia) SQL API isteği oluşturulur. HTTP isteği local test koşumları için <a href="http://localhost:8033/sql">http://localhost:8033/sql</a> url’ine çıkarak yapılabilir. Bu isteğin body’sinde database ve query bilgilerini içermelidir.</li></ul><p>Farklı database’lerde SQL API request body kullanımları:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/20bcf973b90eb412ff3cb2e8a9ff8935/href">https://medium.com/media/20bcf973b90eb412ff3cb2e8a9ff8935/href</a></iframe><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/4bc41d80f4c7989ba72957db5d6d61ce/href">https://medium.com/media/4bc41d80f4c7989ba72957db5d6d61ce/href</a></iframe><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/fb96872b9a51a28ee460d6bd076eaf63/href">https://medium.com/media/fb96872b9a51a28ee460d6bd076eaf63/href</a></iframe><p>Postman’de oluşturulmuş SQL API örneği:</p><p>Bu örnekte Pre-request’te POST isteğiyle kullanıcı oluşturulmaktadır. Fakat isteğin response’unda kullanıcı bilgileri gelmemektedir. Aynı test senaryosunda SQL API’ye istek atarak database’deki kayıdı oluşturulan kullanıcı dataları kontrol edilmektedir.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g4vJnObVGZFC7bcX4hVcTw.png" /><figcaption>Pre-request’te başarılı bir customer oluşturulur.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*z5h8ctBKB5X-C7AhAvm1PQ.png" /><figcaption>Body’de SQL API için database configleri ve query hazırlanır.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iyT_Z6j9u1ovJfAPduG-gw.png" /><figcaption>Test adımında databasedeki querynin kontrolü yapılır.</figcaption></figure><p>Faydalı linkler:</p><p><a href="https://hub.docker.com/r/techciceksepeti/sqlapi">https://hub.docker.com/r/techciceksepeti/sqlapi</a><br><a href="https://github.com/ciceksepetitech/sqlapi">https://github.com/ciceksepetitech/sqlapi</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2e94b5a2cb24" width="1" height="1" alt=""><hr><p><a href="https://medium.com/cstech/sql-api-nedir-2e94b5a2cb24">SQL API nedir?</a> was originally published in <a href="https://medium.com/cstech">ÇSTech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What is SQL API?]]></title>
            <link>https://medium.com/cstech/what-is-sql-api-ac789b624332?source=rss-6956c6cfeac0------2</link>
            <guid isPermaLink="false">https://medium.com/p/ac789b624332</guid>
            <category><![CDATA[integration-testing]]></category>
            <category><![CDATA[http-request]]></category>
            <category><![CDATA[sql]]></category>
            <category><![CDATA[query]]></category>
            <category><![CDATA[api]]></category>
            <dc:creator><![CDATA[Tuğkan Boz]]></dc:creator>
            <pubDate>Tue, 15 Feb 2022 16:44:49 GMT</pubDate>
            <atom:updated>2022-08-03T13:01:20.165Z</atom:updated>
            <content:encoded><![CDATA[<p>In this article, you can find what SQL API developed by ÇiçekSepeti technology team is, which databases it supports, how it is used, and the example created in Postman.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9DlfyrwvtExPnmFE82Ga3A.jpeg" /></figure><p>What is SQL API?</p><ul><li>SQL API is HTTP request that allows us to send a query to the database. You can access the source code of the project here and get more information, <a href="https://github.com/ciceksepetitech/sqlapi">SQL API</a>.</li><li>Warning! Do not use it in production. SQL API is suitable for test environments. In particular for integration tests.</li></ul><p>Which problem is solved by SQL API?</p><ul><li>After sending successful HTTP requests, it checks the records contained in the database.<br>For example, It checks that the data sent to the database is saved in POST requests, and data is deleted from the database in DELETE requests.</li></ul><p>Which databases does SQL API support?</p><ul><li>MySQL</li><li>MsSQL</li><li>MongoDB</li></ul><p>How to use SQL API?</p><ul><li>After creating the database, SQL API request is created through the tool to be tested (Postman, RestAssured, Insomnia). HTTP request can be made by url <a href="http://localhost:8033/sql">http://localhost:8033/sql</a> for local test runs. The body of this request should contain database and query information.</li></ul><p>SQL API request body usage in different databases:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/20bcf973b90eb412ff3cb2e8a9ff8935/href">https://medium.com/media/20bcf973b90eb412ff3cb2e8a9ff8935/href</a></iframe><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/fb96872b9a51a28ee460d6bd076eaf63/href">https://medium.com/media/fb96872b9a51a28ee460d6bd076eaf63/href</a></iframe><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/4bc41d80f4c7989ba72957db5d6d61ce/href">https://medium.com/media/4bc41d80f4c7989ba72957db5d6d61ce/href</a></iframe><p>Example of SQL API created in Postman:</p><ul><li>In this example, the user is created with a POST request in Pre-request. However, the user information is not received in the request’s response. In the same test scenario, the user data created in the database is checked by sending a request to SQL API.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g4vJnObVGZFC7bcX4hVcTw.png" /><figcaption>Successful customer is created in the pre-request.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*z5h8ctBKB5X-C7AhAvm1PQ.png" /><figcaption>Database configs and query are prepared for SQL API in body.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iyT_Z6j9u1ovJfAPduG-gw.png" /><figcaption>In the test step, the query in the database is checked.</figcaption></figure><p>Useful links:</p><p><a href="https://hub.docker.com/r/techciceksepeti/sqlapi">https://hub.docker.com/r/techciceksepeti/sqlapi</a><br><a href="https://github.com/ciceksepetitech/sqlapi">https://github.com/ciceksepetitech/sqlapi</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ac789b624332" width="1" height="1" alt=""><hr><p><a href="https://medium.com/cstech/what-is-sql-api-ac789b624332">What is SQL API?</a> was originally published in <a href="https://medium.com/cstech">ÇSTech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ÇiçekSepeti Mikroservis Projelerinde Otomasyon Testi Süreçleri — Part 2/3]]></title>
            <link>https://medium.com/cstech/%C3%A7i%C3%A7eksepeti-mikroservis-projelerinde-otomasyon-testi-s%C3%BCre%C3%A7leri-part-2-3-7a719178112?source=rss-6956c6cfeac0------2</link>
            <guid isPermaLink="false">https://medium.com/p/7a719178112</guid>
            <dc:creator><![CDATA[Tuğkan Boz]]></dc:creator>
            <pubDate>Mon, 10 Jan 2022 10:28:05 GMT</pubDate>
            <atom:updated>2022-06-05T09:49:40.450Z</atom:updated>
            <content:encoded><![CDATA[<h3>ÇiçekSepeti Mikroservis Projelerinde Otomasyon Testi Süreçleri — Part 2/3</h3><p>Bu bölümde ÇiçekSepeti’nde API otomasyonunu ve bu otomasyonun CI/CD süreçlerine nasıl aktarıldığını anlatacağız. API otomasyonunda entegrasyon testleri, CDC testleri ve performans testleri yapmaktayız.</p><p>API otomasyonu yazarken kullandığımız araçlar, konfigürasyonlar, test mantığı ve dikkat edilmesi gereken durumlar gibi konuları ele alacağız.</p><p>API otomasyonundaki en büyük amacımız: test coverage’nı en yüksek seviyede tutmaktır. Projeyi, CI/CD pipeline adımlarında docker container’ları ayağa kaldırıp test ortamlarından bağımsız bir şekilde testlerin koşulmasını amaçlamaktayız.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vaCCHIBuXIbiDVGibzbzhg.jpeg" /><figcaption><a href="https://www.freepik.com/">Designed by vectorjuice / Freepik</a></figcaption></figure><h4>Entegrasyon Testi</h4><p>Bu yöntem ile API’lar için validation, business flow, extreme ve happy path senaryoları; Postman Collection üzerinde yazılan testler ile kontrol edilmektedir.<br>CI/CD pipeline’ına eklenen entegrasyon testleri, her commit ile docker containerlerı ayağa kaldırılarak sıfırdan koşmaktadır.</p><p>ÇiçekSepeti olarak API testlerinde test ortamlarındaki değişikliklerden etkilenmemeyi amaçlamaktayız. İzole bir ortam için: kendi veritabanımızı oluşturuyoruz ve haberleştiğimiz diğer servisleri mockluyoruz.</p><h4>1- Veritabanı</h4><p>Test ortamındaki veritabanını kullanmak yerine kendi veritabanımızı oluşturmamızın amacı, verileri testlerimize uygun oluşturabilmek ve test ortamındaki verilerin değişikliğinden etkilenmemektir.</p><p>Örneğin bu serviste MySQL veritabanı kullanıyoruz, bundan dolayı projede <em>./ci-test/mysql/schema.sql</em> dosyasını oluşturup içerisine tablolarımızın ve verilerimizin oluşmasını sağlayan sql komutlarını ekliyoruz.</p><p>Schema.sql dosyasını oluştururken şunlara dikkat etmeliyiz:<br>- Tabloları oluştururken sadece ihtiyacımız olan alanları eklemekteyiz.<br>- Farklı business akışları için uygun veri oluşturmaktayız.<br>- Her bir test senaryoda kullanılan verinin ayrı olmasını sağlamaktayız.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/f4514a5f9826d29f3e9963b61c902b39/href">https://medium.com/media/f4514a5f9826d29f3e9963b61c902b39/href</a></iframe><p>2- Mock Servisler</p><p>Test ortamındaki servisler yerine mock servis oluşturmamızın amacı, ilgili servisin ayakta olmaması veya geç cevap vermesi gibi olumsuz durumlardan etkilenmemektir.</p><p>Projede mock servis kullanılacak ise <em>./ci-test/imposters/imposters.ejs</em> içinde gerekli olan servislerin .ejs dosyaları tanımlanmalıdır.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/66dc6898870cbc59ffdb3eb70488445e/href">https://medium.com/media/66dc6898870cbc59ffdb3eb70488445e/href</a></iframe><p>Ardından, <em>./ci-test/imposters </em>dizininde, kullanılacak her bir mock servis için .ejs dosyası oluşturulmalıdır. Bu dosya içerisinde request ve response’lar eklenmelidir.</p><p>Örneğin, 5025 portunda çalışan “<em>/todos/user/1</em>” url’e GET isteği attığımızda bize cevap olarak toDos array’inde <em>id, name, isCompleted, expireDate</em> alanlarını dönen bir mock servis yazılmıştır.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/b2a272f4c96ad260dd63073aad283203/href">https://medium.com/media/b2a272f4c96ad260dd63073aad283203/href</a></iframe><p>Mountebank ile servisleri mockladığımızda istekleri kaydedip bize görsel bir arayüz üzerinden sunabiliyor, bu konuyla alakalı makaleye linkten ulaşabilirsiniz: <a href="https://medium.com/@nursah.bayat/mountebank-ile-requestleri-kaydetme-g%C3%B6r%C3%BCnt%C3%BCleme-2a6352f0f459">Link.</a></p><h4>Containerları Ayağa Kaldırma</h4><p>docker-compose.yml dosyası, projede ayağa kaldırılacak container’ların konfigüre edildiği yerdir. <br>Bu serviste test için ihtiyacımız olan container’lar:<br>-MySQL<br>-Sqlapi<br>-Mountebank</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/dada51e2b30d04d0778b41129bcec7ce/href">https://medium.com/media/dada51e2b30d04d0778b41129bcec7ce/href</a></iframe><p>Terminalde proje dizinine gidip aşağıdaki komutla container’ları oluşturuyoruz.</p><blockquote>docker compose build</blockquote><p>Container’lar oluştuktan sonra aşağıdaki komutla projeyi ayağa kaldırıyoruz.</p><blockquote>docker compose up</blockquote><p>Mock servisimizi ve test datalarımızı oluşturup projeyi ayağa kaldırdıktan sonra testlerimizi yazmaya başlayabiliriz. Test senaryolarımızın yazıldığı makalemizin diğer partına bu linkten ulaşabilirsiniz. <a href="https://medium.com/@nursah.bayat/%C3%A7i%C3%A7eksepeti-mikroservis-projelerinde-otomasyon-testi-s%C3%BCre%C3%A7leri-part-3-3-bab770745689">Link.</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7a719178112" width="1" height="1" alt=""><hr><p><a href="https://medium.com/cstech/%C3%A7i%C3%A7eksepeti-mikroservis-projelerinde-otomasyon-testi-s%C3%BCre%C3%A7leri-part-2-3-7a719178112">ÇiçekSepeti Mikroservis Projelerinde Otomasyon Testi Süreçleri — Part 2/3</a> was originally published in <a href="https://medium.com/cstech">ÇSTech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>