<?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:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:jellypod="https://jellypod.ai/namespace/1.0" xmlns:podcast="https://podcastindex.org/namespace/1.0" xmlns:psc="http://podlove.org/simple-chapters"><channel><title><![CDATA[QA Run1 Show]]></title><description><![CDATA[A short QA test podcast about testing apps.]]></description><link>https://qa-run1-show-2dzgzw.jellypod.com</link><generator>Powered by Jellypod (https://www.jellypod.com)</generator><lastBuildDate>Thu, 12 Nov 2026 19:15:51 GMT</lastBuildDate><atom:link href="https://qa-run1-show-2dzgzw.jellypod.com/rss" rel="self" type="application/rss+xml"/><pubDate>Mon, 19 Oct 2026 02:51:58 GMT</pubDate><copyright><![CDATA[Copyright 2026 QA Run1 Show]]></copyright><language><![CDATA[en]]></language><podcast:locked owner="feed+15db38ba@podcasts.jellypod.com">yes</podcast:locked><podcast:guid>5d37914b-4661-4033-ba75-96894f6221dd</podcast:guid><itunes:author>QA Test</itunes:author><itunes:subtitle>A short QA test podcast about testing apps.</itunes:subtitle><itunes:summary>A short QA test podcast about testing apps.</itunes:summary><itunes:type>episodic</itunes:type><itunes:owner><itunes:name>QA Test</itunes:name><itunes:email>feed+15db38ba@podcasts.jellypod.com</itunes:email></itunes:owner><itunes:explicit>false</itunes:explicit><itunes:category text="Technology"/><itunes:image href="https://media.jellypod.com/storage/v1/object/public/CoverImages/org_01M381Q5MJ1S7KSTG34GTW60CA/podcast-covers/5d37914b-4661-4033-ba75-96894f6221dd-41c2cbcd-02c3-447f-8375-783ed5e2f289.jpeg"/><item><title><![CDATA[Write Bug Reports Developers Actually Read]]></title><description><![CDATA[Learn how to write bug reports developers can quickly understand and act on: use specific titles, clear reproduction steps, expected versus actual results, and searchable evidence. We also cover why neutral language, one defect per report, and honest severity ratings help build trust and speed up triage.

Show Notes

How to Write a Bug Report Developers Actually Act On - Pearly Quality: https://pearlyquality.hu/articles/bug-reports-developers-act-on/]]></description><link>https://qa-run1-show-2dzgzw.jellypod.com/episodes/473f83f5-0259-49d0-ac2e-a43394cb8c21</link><guid isPermaLink="false">473f83f5-0259-49d0-ac2e-a43394cb8c21</guid><pubDate>Thu, 22 Oct 2026 21:16:53 GMT</pubDate><enclosure url="https://op3.dev/e,pg=5d37914b-4661-4033-ba75-96894f6221dd/media.jellypod.com/storage/v1/object/public/Podcasts/org_01M381Q5MJ1S7KSTG34GTW60CA/473f83f5-0259-49d0-ac2e-a43394cb8c21/published/cd688fbd-b94d-48e6-b3af-6bfa012efcc8.mp3?v=cd688fbd-b94d-48e6-b3af-6bfa012efcc8" length="0" type="audio/mpeg"/><podcast:generator uri="https://www.jellypod.com"></podcast:generator><podcast:episode>1</podcast:episode><itunes:episode>1</itunes:episode><content:encoded><![CDATA[<p>Learn how to write bug reports developers can quickly understand and act on: use specific titles, clear reproduction steps, expected versus actual results, and searchable evidence. We also cover why neutral language, one defect per report, and honest severity ratings help build trust and speed up triage.</p><p><strong>Show Notes</strong></p><ul><li>How to Write a Bug Report Developers Actually Act On - Pearly Quality: <a href="https://pearlyquality.hu/articles/bug-reports-developers-act-on/">https://pearlyquality.hu/articles/bug-reports-developers-act-on/</a></li></ul>]]></content:encoded><podcast:transcript language="en" rel="captions" type="application/x-subrip" url="https://media.jellypod.com/storage/v1/object/public/Podcasts/org_01M381Q5MJ1S7KSTG34GTW60CA/473f83f5-0259-49d0-ac2e-a43394cb8c21/cd688fbd-b94d-48e6-b3af-6bfa012efcc8.srt"></podcast:transcript><itunes:author>QA Test</itunes:author><itunes:subtitle>Learn how to write bug reports developers can quickly understand and act on: use specific titles, clear reproduction steps, expected versus actual results, and searchable evidence. We also cover why neutral language, one defect per report, and honest seve</itunes:subtitle><itunes:summary>Learn how to write bug reports developers can quickly understand and act on: use specific titles, clear reproduction steps, expected versus actual results, and searchable evidence. We also cover why neutral language, one defect per report, and honest severity ratings help build trust and speed up triage.

Show Notes

How to Write a Bug Report Developers Actually Act On - Pearly Quality: https://pearlyquality.hu/articles/bug-reports-developers-act-on/</itunes:summary><itunes:explicit>false</itunes:explicit><itunes:duration>00:03:26</itunes:duration><itunes:image href="https://media.jellypod.com/storage/v1/object/public/CoverImages/org_01M381Q5MJ1S7KSTG34GTW60CA/podcast-covers/5d37914b-4661-4033-ba75-96894f6221dd-41c2cbcd-02c3-447f-8375-783ed5e2f289.jpeg"/><itunes:episodeType>full</itunes:episodeType></item></channel></rss>