<?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>Bug Reporting &#8211; BleepingBugs</title>
	<atom:link href="https://bleepingbugs.com/tag/bug-reporting/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>Bug Reporting &#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>How to Write a Good Functional Bug Report</title>
		<link>https://bleepingbugs.com/how-to-write-a-good-functional-bug-report/</link>
		
		<dc:creator><![CDATA[Bleeping Bugs]]></dc:creator>
		<pubDate>Tue, 12 May 2026 04:43:48 +0000</pubDate>
				<category><![CDATA[Testing Tutorials]]></category>
		<category><![CDATA[Bug Reporting]]></category>
		<guid isPermaLink="false">https://bleepingbugs.com/?p=669</guid>

					<description><![CDATA[When I started in QA, I thought I had bug reports figured out. Steps to reproduce. Expected result. Actual result. Screenshot. Every tutorial said the same thing, so I did the same thing. Felt solid. Then I joined a company that used freelance testers. Video attachments were mandatory — not recommended, mandatory. The reasoning was&#46;&#46;&#46;]]></description>
										<content:encoded><![CDATA[<p>When I started in QA, I thought I had bug reports figured out. Steps to reproduce. Expected result. Actual result. Screenshot. Every tutorial said the same thing, so I did the same thing. Felt solid. Then I joined a company that used freelance testers. Video attachments were mandatory — not recommended, mandatory. The reasoning was blunt: you can’t fake a video. A screenshot proves nothing…</p>
<p><a href="https://bleepingbugs.com/how-to-write-a-good-functional-bug-report/" rel="nofollow">Source</a></p>]]></content:encoded>
					
		
		<enclosure url="https://bleepingbugs.com/wp-content/uploads/2026/05/blazedemo_bug_report.mp4" length="372234" type="video/mp4" />

			</item>
		<item>
		<title>A Bug Report Is How You Communicate Risk</title>
		<link>https://bleepingbugs.com/a-bug-report-is-how-you-communicate-risk/</link>
		
		<dc:creator><![CDATA[Bleeping Bugs]]></dc:creator>
		<pubDate>Fri, 28 Apr 2023 02:33:30 +0000</pubDate>
				<category><![CDATA[Shower Thoughts]]></category>
		<category><![CDATA[Bug Reporting]]></category>
		<guid isPermaLink="false">https://bleepingbugs.com/?p=35</guid>

					<description><![CDATA[Most QAs think reporting a bug means opening Jira. And sure, Jira works. But that framing limits your options. A bug is just information about a risk — here&#8217;s something wrong, here&#8217;s how bad it could be, here&#8217;s what we should do about it. And information doesn&#8217;t care how it travels. As long as the&#46;&#46;&#46;]]></description>
										<content:encoded><![CDATA[<p>Most QAs think reporting a bug means opening Jira. And sure, Jira works. But that framing limits your options. A bug is just information about a risk — here’s something wrong, here’s how bad it could be, here’s what we should do about it. And information doesn’t care how it travels. As long as the right person receives it clearly and can act on it, you’ve done your job.</p>
<p><a href="https://bleepingbugs.com/a-bug-report-is-how-you-communicate-risk/" rel="nofollow">Source</a></p>]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
