<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Test Planning &#8211; BleepingBugs</title>
	<atom:link href="https://bleepingbugs.com/tag/test-planning/feed/" rel="self" type="application/rss+xml" />
	<link>https://bleepingbugs.com</link>
	<description>Candid Takes On QA</description>
	<lastBuildDate>Tue, 02 Jun 2026 06:03:28 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.0</generator>

<image>
	<url>https://bleepingbugs.com/wp-content/uploads/2026/05/cropped-bb_IconOnly_transparent_bg-1-32x32.webp</url>
	<title>Test Planning &#8211; BleepingBugs</title>
	<link>https://bleepingbugs.com</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>How to Build the &#8220;Imperfect&#8221; QA Process</title>
		<link>https://bleepingbugs.com/how-to-build-the-imperfect-qa-process/</link>
		
		<dc:creator><![CDATA[Bleeping Bugs]]></dc:creator>
		<pubDate>Sun, 24 May 2026 17:51:35 +0000</pubDate>
				<category><![CDATA[Testing Tutorials]]></category>
		<category><![CDATA[Bug Reporting]]></category>
		<category><![CDATA[Career]]></category>
		<category><![CDATA[QA Process]]></category>
		<category><![CDATA[Test Planning]]></category>
		<guid isPermaLink="false">https://bleepingbugs.com/?p=809</guid>

					<description><![CDATA[When I got my first QA Engineer job out of college at a small financial company, I did what any new grad would do. I googled &#8220;QA process.&#8221; Then I googled &#8220;what should a QA process look like.&#8221; Then I googled &#8220;how to build a QA process from scratch.&#8221; I read a lot of articles.&#46;&#46;&#46;]]></description>
										<content:encoded><![CDATA[<p>When I got my first QA Engineer job out of college at a small financial company, I did what any new grad would do. I googled “QA process.” Then I googled “what should a QA process look like.” Then I googled “how to build a QA process from scratch.” I read a lot of articles. I got a lot of frameworks with a lot of boxes and arrows. None of it told me what to actually do on Monday morning.</p>
<p><a href="https://bleepingbugs.com/how-to-build-the-imperfect-qa-process/" rel="nofollow">Source</a></p>]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>The Test Plan Nobody Reads</title>
		<link>https://bleepingbugs.com/the-test-plan-nobody-reads/</link>
		
		<dc:creator><![CDATA[Bleeping Bugs]]></dc:creator>
		<pubDate>Sat, 23 May 2026 21:01:24 +0000</pubDate>
				<category><![CDATA[Shower Thoughts]]></category>
		<category><![CDATA[Test Planning]]></category>
		<guid isPermaLink="false">https://bleepingbugs.com/?p=807</guid>

					<description><![CDATA[For over a year I sent a test plan at the start of every sprint. Same format, same sections, shared in the same Slack channel every time. In all that time, maybe one or two of them got a comment from anyone outside the QA team. Not from product. Not from engineering. I kept sending&#46;&#46;&#46;]]></description>
										<content:encoded><![CDATA[<p>For over a year I sent a test plan at the start of every sprint. Same format, same sections, shared in the same Slack channel every time. In all that time, maybe one or two of them got a comment from anyone outside the QA team. Not from product. Not from engineering. I kept sending them anyway, convinced that if I just got the format right, or shared it at the right time…</p>
<p><a href="https://bleepingbugs.com/the-test-plan-nobody-reads/" rel="nofollow">Source</a></p>]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>How To Write a Sprint Test Plan</title>
		<link>https://bleepingbugs.com/how-to-write-a-sprint-test-plan/</link>
		
		<dc:creator><![CDATA[Bleeping Bugs]]></dc:creator>
		<pubDate>Sun, 17 May 2026 19:51:51 +0000</pubDate>
				<category><![CDATA[Testing Tutorials]]></category>
		<category><![CDATA[Test Planning]]></category>
		<guid isPermaLink="false">https://bleepingbugs.com/?p=818</guid>

					<description><![CDATA[Most test plans I&#8217;ve seen start with scope before talking about risks. Here&#8217;s what we&#8217;ll test, here&#8217;s what we won&#8217;t. Which is fine, except it skips the question that actually drives all of it: what are the risks we&#8217;re trying to protect against? I write sprint-level test plans one per sprint, covering everything QA is&#46;&#46;&#46;]]></description>
										<content:encoded><![CDATA[<p>Most test plans I’ve seen start with scope before talking about risks. Here’s what we’ll test, here’s what we won’t. Which is fine, except it skips the question that actually drives all of it: what are the risks we’re trying to protect against? I write sprint-level test plans one per sprint, covering everything QA is responsible for in that three week window. I’ll cover project and feature…</p>
<p><a href="https://bleepingbugs.com/how-to-write-a-sprint-test-plan/" rel="nofollow">Source</a></p>]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
