<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>quality assurance on Kuldeep Pisda</title><link>https://kdpisda.in/tag/quality-assurance/</link><description>Recent content in quality assurance on Kuldeep Pisda</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 02 Dec 2025 12:50:48 +0530</lastBuildDate><atom:link href="https://kdpisda.in/tag/quality-assurance/index.xml" rel="self" type="application/rss+xml"/><item><title>Test Automation Best Practices That Won't Make You Want to Flip Your Desk</title><link>https://kdpisda.in/test-automation-best-practices-that-wont-make-you-want-to-flip-your-desk/</link><pubDate>Tue, 02 Dec 2025 12:50:48 +0530</pubDate><guid>https://kdpisda.in/test-automation-best-practices-that-wont-make-you-want-to-flip-your-desk/</guid><description>&lt;p&gt;We have all been there. You push a feature, the CI pipeline lights up green, and you move on, only to find a frantic message hours later about a regression in production. That momentary confidence shatters, replaced by a sinking feeling. It&amp;rsquo;s a common story in fast moving startups and scale ups, where the pressure to ship often turns test suites into a fragile, high maintenance burden. The problem is not a lack of tests, but a lack of strategy. Flaky tests and unexpected breaks are often symptoms of deeper issues, where the cost of maintaining the test suite starts to outweigh its benefits.&lt;/p&gt;</description></item><item><title>Your Guide to Testing Software Requirements Before You Write a Single Line of Code</title><link>https://kdpisda.in/your-guide-to-testing-software-requirements-before-you-write-a-single-line-of-code/</link><pubDate>Fri, 03 Oct 2025 11:01:25 +0530</pubDate><guid>https://kdpisda.in/your-guide-to-testing-software-requirements-before-you-write-a-single-line-of-code/</guid><description>&lt;p&gt;Ever poured weeks into a feature that matched the spec sheet perfectly, only to watch it land with a thud? I have. It&amp;rsquo;s a gut wrenching feeling. You followed the map, but the map led you off a cliff.&lt;/p&gt;
&lt;p&gt;This is the silent killer of so many projects: we focus so intensely on &lt;em&gt;building the thing right&lt;/em&gt; that we forget to ask if we&amp;rsquo;re even &lt;em&gt;building the right thing&lt;/em&gt;. &amp;ldquo;Testing software requirements&amp;rdquo; is the formal name for this gut check. It&amp;rsquo;s the process of interrogating your plan before the first line of code is ever written, saving you from the nightmare of building beautiful software that nobody actually wants.&lt;/p&gt;</description></item></channel></rss>