<?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[Case to Cases - Medium]]></title>
        <description><![CDATA[CaseToCases is a monthly digest curating the latest in QA trends, tools, and automation. From manual testing to automation, we share insights and real-world stories to keep you updated. Subscribe for valuable lessons and stay ahead in the world of software quality. - Medium]]></description>
        <link>https://medium.com/case-to-cases?source=rss----0b12bd111f79---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Case to Cases - Medium</title>
            <link>https://medium.com/case-to-cases?source=rss----0b12bd111f79---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 15:18:10 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/case-to-cases" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[CaseToCases Digest #7:-The Evolution of Prompting in Software Testing]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/case-to-cases/casetocases-digest-7-the-evolution-of-prompting-in-software-testing-50a5030feadf?source=rss----0b12bd111f79---4"><img src="https://cdn-images-1.medium.com/max/2240/1*0joaChf9woFFqrjwVPhPRQ.png" width="2240"></a></p><p class="medium-feed-snippet">Hello, Test Enthusiasts &#x1F44B;</p><p class="medium-feed-link"><a href="https://medium.com/case-to-cases/casetocases-digest-7-the-evolution-of-prompting-in-software-testing-50a5030feadf?source=rss----0b12bd111f79---4">Continue reading on Case to Cases »</a></p></div>]]></description>
            <link>https://medium.com/case-to-cases/casetocases-digest-7-the-evolution-of-prompting-in-software-testing-50a5030feadf?source=rss----0b12bd111f79---4</link>
            <guid isPermaLink="false">https://medium.com/p/50a5030feadf</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[software-testing]]></category>
            <category><![CDATA[prompt]]></category>
            <category><![CDATA[llm]]></category>
            <category><![CDATA[writing-prompts]]></category>
            <dc:creator><![CDATA[Niar]]></dc:creator>
            <pubDate>Mon, 01 Sep 2025 02:49:01 GMT</pubDate>
            <atom:updated>2025-09-01T02:49:01.072Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[CaseToCases Digest #6: — ChatGPT Agent vs MCP Server , Two AI Approaches That Are Changing the…]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/case-to-cases/casetocases-digest-6-chatgpt-agent-vs-mcp-server-two-ai-approaches-that-are-changing-the-049e31610033?source=rss----0b12bd111f79---4"><img src="https://cdn-images-1.medium.com/max/2240/1*0joaChf9woFFqrjwVPhPRQ.png" width="2240"></a></p><p class="medium-feed-snippet">Hello, Test Enthusiasts &#x1F44B;</p><p class="medium-feed-link"><a href="https://medium.com/case-to-cases/casetocases-digest-6-chatgpt-agent-vs-mcp-server-two-ai-approaches-that-are-changing-the-049e31610033?source=rss----0b12bd111f79---4">Continue reading on Case to Cases »</a></p></div>]]></description>
            <link>https://medium.com/case-to-cases/casetocases-digest-6-chatgpt-agent-vs-mcp-server-two-ai-approaches-that-are-changing-the-049e31610033?source=rss----0b12bd111f79---4</link>
            <guid isPermaLink="false">https://medium.com/p/049e31610033</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[llm]]></category>
            <dc:creator><![CDATA[Niar]]></dc:creator>
            <pubDate>Tue, 05 Aug 2025 08:54:13 GMT</pubDate>
            <atom:updated>2025-08-05T08:54:13.543Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[CaseToCases Digest #5: - Scriptless, AI, and TestOps: 3 New Forces in the QA Environment]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/case-to-cases/casetocases-digest-5-scriptless-ai-and-testops-3-new-forces-in-the-qa-environment-bfee11caf30f?source=rss----0b12bd111f79---4"><img src="https://cdn-images-1.medium.com/max/2240/1*0joaChf9woFFqrjwVPhPRQ.png" width="2240"></a></p><p class="medium-feed-snippet">Hello, Test Enthusiasts &#x1F44B;</p><p class="medium-feed-link"><a href="https://medium.com/case-to-cases/casetocases-digest-5-scriptless-ai-and-testops-3-new-forces-in-the-qa-environment-bfee11caf30f?source=rss----0b12bd111f79---4">Continue reading on Case to Cases »</a></p></div>]]></description>
            <link>https://medium.com/case-to-cases/casetocases-digest-5-scriptless-ai-and-testops-3-new-forces-in-the-qa-environment-bfee11caf30f?source=rss----0b12bd111f79---4</link>
            <guid isPermaLink="false">https://medium.com/p/bfee11caf30f</guid>
            <category><![CDATA[software-testing]]></category>
            <category><![CDATA[automation-testing]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[technology-trends]]></category>
            <dc:creator><![CDATA[Niar]]></dc:creator>
            <pubDate>Tue, 15 Jul 2025 15:55:18 GMT</pubDate>
            <atom:updated>2025-07-28T06:36:52.506Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[CaseToCases Digest #4 — The Limits of AI in Software Testing: Why QA Engineers Still Matter]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/case-to-cases/casetocases-digest-4-the-limits-of-ai-in-software-testing-why-qa-engineers-still-matter-9d532756a968?source=rss----0b12bd111f79---4"><img src="https://cdn-images-1.medium.com/max/2240/1*gdxA2q7umMnzsWL37EY3tg.png" width="2240"></a></p><p class="medium-feed-snippet">Hello, Test Enthusiasts &#x1F44B;</p><p class="medium-feed-link"><a href="https://medium.com/case-to-cases/casetocases-digest-4-the-limits-of-ai-in-software-testing-why-qa-engineers-still-matter-9d532756a968?source=rss----0b12bd111f79---4">Continue reading on Case to Cases »</a></p></div>]]></description>
            <link>https://medium.com/case-to-cases/casetocases-digest-4-the-limits-of-ai-in-software-testing-why-qa-engineers-still-matter-9d532756a968?source=rss----0b12bd111f79---4</link>
            <guid isPermaLink="false">https://medium.com/p/9d532756a968</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[software-testing]]></category>
            <category><![CDATA[ai-assistant]]></category>
            <dc:creator><![CDATA[Niar]]></dc:creator>
            <pubDate>Mon, 23 Jun 2025 13:17:38 GMT</pubDate>
            <atom:updated>2025-06-23T13:17:57.463Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[CaseToCases Digest #3 — Beyond Manual: How AI & n8n Redefine QA Workflows]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/case-to-cases/casetocases-digest-3-beyond-manual-how-ai-n8n-redefine-qa-workflows-788d534a9db8?source=rss----0b12bd111f79---4"><img src="https://cdn-images-1.medium.com/max/2240/1*gdxA2q7umMnzsWL37EY3tg.png" width="2240"></a></p><p class="medium-feed-snippet">Hello, Test Enthusiasts &#x1F44B;</p><p class="medium-feed-link"><a href="https://medium.com/case-to-cases/casetocases-digest-3-beyond-manual-how-ai-n8n-redefine-qa-workflows-788d534a9db8?source=rss----0b12bd111f79---4">Continue reading on Case to Cases »</a></p></div>]]></description>
            <link>https://medium.com/case-to-cases/casetocases-digest-3-beyond-manual-how-ai-n8n-redefine-qa-workflows-788d534a9db8?source=rss----0b12bd111f79---4</link>
            <guid isPermaLink="false">https://medium.com/p/788d534a9db8</guid>
            <category><![CDATA[software-testing]]></category>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[agentic-workflow]]></category>
            <category><![CDATA[agentic-ai]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Niar]]></dc:creator>
            <pubDate>Tue, 10 Jun 2025 17:23:44 GMT</pubDate>
            <atom:updated>2025-06-10T17:31:51.074Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[CaseToCases Digest #2]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/case-to-cases/casetocases-digest-2-b2e558143b3b?source=rss----0b12bd111f79---4"><img src="https://cdn-images-1.medium.com/max/2240/1*AYb20it-9WHCPAQMf6cEkg.png" width="2240"></a></p><p class="medium-feed-link"><a href="https://medium.com/case-to-cases/casetocases-digest-2-b2e558143b3b?source=rss----0b12bd111f79---4">Continue reading on Case to Cases »</a></p></div>]]></description>
            <link>https://medium.com/case-to-cases/casetocases-digest-2-b2e558143b3b?source=rss----0b12bd111f79---4</link>
            <guid isPermaLink="false">https://medium.com/p/b2e558143b3b</guid>
            <category><![CDATA[automation-testing]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[software-testing]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Niar]]></dc:creator>
            <pubDate>Fri, 02 May 2025 09:56:22 GMT</pubDate>
            <atom:updated>2025-07-21T15:05:30.231Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[CaseToCases Digest #1 — “Quality is a habit, not a phase]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/case-to-cases/casetocases-digest-1-quality-is-a-habit-not-a-phase-bbd16c18560a?source=rss----0b12bd111f79---4"><img src="https://cdn-images-1.medium.com/max/2240/1*AYb20it-9WHCPAQMf6cEkg.png" width="2240"></a></p><p class="medium-feed-snippet">Hello, Test Enthusiasts &#x1F44B;</p><p class="medium-feed-link"><a href="https://medium.com/case-to-cases/casetocases-digest-1-quality-is-a-habit-not-a-phase-bbd16c18560a?source=rss----0b12bd111f79---4">Continue reading on Case to Cases »</a></p></div>]]></description>
            <link>https://medium.com/case-to-cases/casetocases-digest-1-quality-is-a-habit-not-a-phase-bbd16c18560a?source=rss----0b12bd111f79---4</link>
            <guid isPermaLink="false">https://medium.com/p/bbd16c18560a</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[software-testing]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[quality-assurance]]></category>
            <category><![CDATA[automation]]></category>
            <dc:creator><![CDATA[Niar]]></dc:creator>
            <pubDate>Wed, 23 Apr 2025 05:25:27 GMT</pubDate>
            <atom:updated>2025-04-23T05:25:27.658Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Modularization in Playwright Testing: A Complete Example]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/case-to-cases/modularization-in-playwright-testing-a-complete-example-9ebad66645b0?source=rss----0b12bd111f79---4"><img src="https://cdn-images-1.medium.com/max/2600/1*2pD2HT0kmVd9z6JlJ7FBjA.png" width="2800"></a></p><p class="medium-feed-snippet">What is Modularization?</p><p class="medium-feed-link"><a href="https://medium.com/case-to-cases/modularization-in-playwright-testing-a-complete-example-9ebad66645b0?source=rss----0b12bd111f79---4">Continue reading on Case to Cases »</a></p></div>]]></description>
            <link>https://medium.com/case-to-cases/modularization-in-playwright-testing-a-complete-example-9ebad66645b0?source=rss----0b12bd111f79---4</link>
            <guid isPermaLink="false">https://medium.com/p/9ebad66645b0</guid>
            <category><![CDATA[code-reuse]]></category>
            <category><![CDATA[playwrights]]></category>
            <category><![CDATA[test-automation]]></category>
            <category><![CDATA[modularization]]></category>
            <dc:creator><![CDATA[Niar]]></dc:creator>
            <pubDate>Wed, 23 Apr 2025 02:44:59 GMT</pubDate>
            <atom:updated>2024-03-24T11:08:46.701Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[New Cypress.stop() command: Improve Testing Efficiency with Effective Control]]></title>
            <link>https://medium.com/case-to-cases/new-cypress-stop-command-improve-testing-efficiency-with-effective-control-4c11d7bbc51e?source=rss----0b12bd111f79---4</link>
            <guid isPermaLink="false">https://medium.com/p/4c11d7bbc51e</guid>
            <category><![CDATA[automation-testing]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[software-testing]]></category>
            <category><![CDATA[cypress]]></category>
            <dc:creator><![CDATA[Niar]]></dc:creator>
            <pubDate>Wed, 23 Apr 2025 02:44:45 GMT</pubDate>
            <atom:updated>2025-04-23T02:55:26.888Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Jn9qYValATnmI2CreYOjPw.png" /></figure><h3><strong>Introduction</strong></h3><p>Cypress has launched a powerful new command, Cypress.stop(), designed to programmatically stop test execution. This addition gives testers greater control over their automation or test scripts, optimizing efficiency by preventing unnecessary executions and reducing time wasted on failed or irrelevant scenarios.</p><p>In this article, we’ll discuss the importance of <a href="https://www.cypress.io/blog/introducing-cypress-stop-a-simple-way-to-halt-test-runs">Cypress.stop()</a>, its practical applications, and potential pitfalls if implemented incorrectly.</p><h3>What is the purpose of Cypress Introducing Cypress.stop()</h3><p>Automated tests often run across multiple steps and depend on numerous factors such as API availability, environment settings, and test data. If an issue arises early in a test suite, it is inefficient to continue execution. <em>“</em><strong><em>Cypress.stop()</em></strong><em>”</em> addresses this by allowing early termination, saving resources and improving test reliability</p><h3>Key Use Cases for Cypress.stop()</h3><h3>1. Stopping Tests Upon Failure</h3><p>Instead of running subsequent tests when a critical failure occurs, we can halt execution to focus on debugging</p><h4>Example:</h4><pre>afterEach(function () {<br>  if (this.currentTest.state === &#39;failed&#39;) {<br>    Cypress.stop();<br>  }<br>});</pre><p><strong>Benefit</strong>: Saves time by avoiding unnecessary test runs after an initial failure.</p><h3>2. Environment-Specific Testing</h3><p>Certain tests should only run in specific environments. Running them in an unintended environment could lead to misleading results</p><h4>Example:</h4><pre>beforeEach(() =&gt; {<br>  if (Cypress.env(&#39;TEST_ENV&#39;) !== &#39;staging&#39;) {<br>    cy.log(&#39;Wrong environment, stopping test execution&#39;);<br>    Cypress.stop();<br>  }<br>});</pre><p><strong>Benefit</strong>: Prevents unintended execution in production or misconfigured environments</p><h3>3. Stopping Tests If Required Data Is Missing</h3><p>If a test relies on certain data, it should not proceed when that data is unavailable</p><h4>Example:</h4><pre>cy.request(&#39;/api/user/123&#39;).then((response) =&gt; {<br>  if (response.status === 404) {<br>    cy.log(&#39;User not found, stopping test execution&#39;);<br>    Cypress.stop();<br>  }<br>});</pre><p><strong>Benefit</strong>: Ensures meaningful test execution by verifying prerequisite conditions</p><h3>4. Handling API or Service Outages</h3><p>When a test suite depends on an external API, it should stop execution if the API is down to avoid false negatives</p><h4>Example:</h4><pre>cy.request({<br>  url: &#39;/api/status&#39;,<br>  failOnStatusCode: false<br>}).then((response) =&gt; {<br>  if (response.status !== 200) {<br>    cy.log(&#39;API is down, stopping tests&#39;);<br>    Cypress.stop();<br>  }<br>});</pre><p><strong>Benefit</strong>: Prevents failures caused by external dependencies</p><h3>5. Debugging &amp; Investigating Specific Test Steps</h3><p>When troubleshooting a test, you may want to stop execution at a specific step to inspect the current state of the application</p><h4>Example:</h4><pre>cy.get(&#39;#cart&#39;).should(&#39;be.visible&#39;).then(() =&gt; {<br>  Cypress.stop(); // Pause execution for investigation<br>});</pre><p><strong>Benefit</strong>: Enables precise debugging without running the entire test suite.</p><h3>Potential or Pitfalls When Misapplying Cypress.stop()</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UzKN8BgH-pNA5ro6LJxjaA.png" /></figure><p>While “<strong><em>Cypress.stop()</em></strong>” is powerful, improper usage can lead to unintended consequences:</p><ul><li><strong>Incomplete test execution</strong>: Overuse can prevent tests from running fully, leading to missed defects</li><li><strong>False-positive results</strong>: Tests may incorrectly pass if execution is stopped prematurely</li><li><strong>Inconsistent automation workflows</strong>: If not used strategically, it may disrupt CI/CD pipelines</li></ul><h3>Conclusion</h3><p>The introduction of “<strong><em>Cypress.stop()</em></strong>” gives QA engineers more control over test execution. By implementing it strategically, we can increase efficiency, prevent unnecessary failures, and improve test reliability. However, we need and must ensure that it does not lead to incomplete or misleading test results</p><p>Start leveraging “<strong><em>Cypress.stop()</em></strong>” in your test automation workflow and experience the benefits of proper test control!</p><p>And, If you need a freelance QA team or bug hunters to help refine your testing process, my team and I are here to assist you. Reach out to us at <a href="https://lynk.id/depfaris">https://lynk.id/depfaris</a></p><p>This story is published in <a href="https://medium.com/case-to-cases">Casetocases</a>. Connect with the Author on LinkedIn and follow <a href="https://www.linkedin.com/in/faris-niar/">Faris Kurnia</a> to stay up to date with the latest QA news.</p><p>Subscribe to our <a href="https://medium.com/@niarsdet/subscribe">newsletter</a> to stay updated with the latest QA news and trends. Let’s shape the future of QA together!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4c11d7bbc51e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/case-to-cases/new-cypress-stop-command-improve-testing-efficiency-with-effective-control-4c11d7bbc51e">New Cypress.stop() command: Improve Testing Efficiency with Effective Control</a> was originally published in <a href="https://medium.com/case-to-cases">Case to Cases</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Name Field Validation in Form: The Art of Testing]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/case-to-cases/name-field-validation-in-form-the-art-of-testing-281b8ca7f31d?source=rss----0b12bd111f79---4"><img src="https://cdn-images-1.medium.com/max/1920/1*LogdGHQUVTcSsUL8QIJgyw.png" width="1920"></a></p><p class="medium-feed-link"><a href="https://medium.com/case-to-cases/name-field-validation-in-form-the-art-of-testing-281b8ca7f31d?source=rss----0b12bd111f79---4">Continue reading on Case to Cases »</a></p></div>]]></description>
            <link>https://medium.com/case-to-cases/name-field-validation-in-form-the-art-of-testing-281b8ca7f31d?source=rss----0b12bd111f79---4</link>
            <guid isPermaLink="false">https://medium.com/p/281b8ca7f31d</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[quality-assurance]]></category>
            <category><![CDATA[bug-bounty-hunter]]></category>
            <category><![CDATA[software-testing]]></category>
            <dc:creator><![CDATA[Niar]]></dc:creator>
            <pubDate>Wed, 23 Apr 2025 02:43:39 GMT</pubDate>
            <atom:updated>2025-05-17T14:06:48.873Z</atom:updated>
        </item>
    </channel>
</rss>