<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Mark Sameh</title>
    <description>The latest articles on DEV Community by Mark Sameh (@mark_sameh_1fa98d61f13db0).</description>
    <link>https://dev.to/mark_sameh_1fa98d61f13db0</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3873524%2F509a8614-eb2c-4458-8d56-d9a799a5b85c.jpg</url>
      <title>DEV Community: Mark Sameh</title>
      <link>https://dev.to/mark_sameh_1fa98d61f13db0</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/mark_sameh_1fa98d61f13db0"/>
    <language>en</language>
    <item>
      <title>I built a Chrome extension to stop writing the same bug report over and over</title>
      <dc:creator>Mark Sameh</dc:creator>
      <pubDate>Thu, 07 May 2026 18:35:44 +0000</pubDate>
      <link>https://dev.to/mark_sameh_1fa98d61f13db0/i-built-a-chrome-extension-to-stop-writing-the-same-bug-report-over-and-over-1kmg</link>
      <guid>https://dev.to/mark_sameh_1fa98d61f13db0/i-built-a-chrome-extension-to-stop-writing-the-same-bug-report-over-and-over-1kmg</guid>
      <description>&lt;h2&gt;
  
  
  The problem
&lt;/h2&gt;

&lt;p&gt;As a QA engineer, I was spending 20-30 minutes on every single bug report.&lt;/p&gt;

&lt;p&gt;Write the steps. Attach the screenshot. Record the video. Explain the environment. &lt;br&gt;
Jump on a call because the developer "can't reproduce it."&lt;/p&gt;

&lt;p&gt;Sound familiar?&lt;/p&gt;

&lt;h2&gt;
  
  
  What I built
&lt;/h2&gt;

&lt;p&gt;I built &lt;strong&gt;Bug Reproduction Recorder&lt;/strong&gt; — a Chrome extension that automates the &lt;br&gt;
whole thing.&lt;/p&gt;

&lt;p&gt;Here's the flow:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Click &lt;strong&gt;Record&lt;/strong&gt;
&lt;/li&gt;
&lt;li&gt;Reproduce the bug&lt;/li&gt;
&lt;li&gt;Click &lt;strong&gt;Stop&lt;/strong&gt;
&lt;/li&gt;
&lt;li&gt;Get a fully structured bug report — automatically&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The report includes:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Video recording of the session&lt;/li&gt;
&lt;li&gt;Screenshots captured at key moments&lt;/li&gt;
&lt;li&gt;Browser info, OS, page URL&lt;/li&gt;
&lt;li&gt;Reproduction steps&lt;/li&gt;
&lt;li&gt;Shareable public link&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Why I built it myself
&lt;/h2&gt;

&lt;p&gt;I looked at existing tools — Jam, BrowserStack Bug Capture, Loom — but they were &lt;br&gt;
either too expensive for solo QA engineers, too heavy, or required the whole team &lt;br&gt;
to sign up.&lt;/p&gt;

&lt;p&gt;I wanted something lightweight, free to start, and focused purely on bug &lt;br&gt;
reproduction.&lt;/p&gt;

&lt;h2&gt;
  
  
  Tech stack
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Chrome Extension (Manifest V3)&lt;/li&gt;
&lt;li&gt;Supabase (auth + storage)&lt;/li&gt;
&lt;li&gt;Google OAuth&lt;/li&gt;
&lt;li&gt;Vanilla JS&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Try it
&lt;/h2&gt;

&lt;p&gt;🔗 Chrome Web Store: &lt;a href="https://chromewebstore.google.com/detail/bug-reproduction-recorder/bjljppfeefaemnnilkbigfmegaaebkmd" rel="noopener noreferrer"&gt;https://chromewebstore.google.com/detail/bug-reproduction-recorder/bjljppfeefaemnnilkbigfmegaaebkmd&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;🌐 Landing page: &lt;a href="https://bugrecorder-landing.vercel.app" rel="noopener noreferrer"&gt;https://bugrecorder-landing.vercel.app&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;It's free to start (20 reports/month). Would love your feedback — especially &lt;br&gt;
from fellow QA engineers. What would make this 10x more useful for you?&lt;/p&gt;

</description>
      <category>qa</category>
      <category>devtools</category>
      <category>testing</category>
      <category>chrom</category>
    </item>
    <item>
      <title>I built a free Playwright &amp; Cypress snippet library — because I was tired of Googling the same patterns</title>
      <dc:creator>Mark Sameh</dc:creator>
      <pubDate>Sat, 11 Apr 2026 12:52:15 +0000</pubDate>
      <link>https://dev.to/mark_sameh_1fa98d61f13db0/i-built-a-free-playwright-cypress-snippet-library-because-i-was-tired-of-googling-the-same-2b2j</link>
      <guid>https://dev.to/mark_sameh_1fa98d61f13db0/i-built-a-free-playwright-cypress-snippet-library-because-i-was-tired-of-googling-the-same-2b2j</guid>
      <description>&lt;p&gt;Every week, without fail, I'd find myself searching for the same things.&lt;br&gt;
"Playwright intercept POST request." "Cypress wait for API response." "How to skip login UI in Playwright."&lt;br&gt;
I've been a senior QA automation engineer for years. I know these patterns. But I'd still end up on the same Stack Overflow threads, the same outdated blog posts, the same GitHub Gists that may or may not still work with the current version.&lt;br&gt;
And when I couldn't find what I needed fast enough, I'd ask AI to generate it for me. That worked — but it felt like there should be a better way.&lt;br&gt;
So I built one.&lt;/p&gt;

&lt;p&gt;What is SnipQA?&lt;br&gt;
SnipQA is a free, searchable snippet library built specifically for QA automation engineers working with Playwright and Cypress.&lt;br&gt;
It has two main features:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;A curated snippet library
137+ real-world code snippets covering everything from authentication and network interception to file uploads, visual testing, fixtures, selectors, and more. Every snippet is commented to explain why, not just what.&lt;/li&gt;
&lt;li&gt;An AI generator
You describe what you need in plain English — "intercept a failed API response and show an error message" — and get a working, commented snippet instantly. No prompt engineering needed, just describe your scenario.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;What it covers&lt;br&gt;
Both Playwright (TypeScript) and Cypress (JavaScript) — across these categories:&lt;/p&gt;

&lt;p&gt;Auth (login via UI, via API, storageState, cy.session)&lt;br&gt;
Network (intercept, mock, abort, modify headers)&lt;br&gt;
Assertions (visible, text, URL, title, count, soft assertions)&lt;br&gt;
Selectors (getByRole, getByLabel, getByTestId, getByText, XPath)&lt;br&gt;
Forms (dropdowns, checkboxes, radio buttons, file upload, date inputs)&lt;br&gt;
Fixtures (beforeEach, afterEach, test.describe, data-driven)&lt;br&gt;
Visual (screenshot, element screenshot, baseline comparison)&lt;br&gt;
Wait (network idle, element disappear, URL change)&lt;br&gt;
Navigation (multi-tab, back/forward, redirect)&lt;br&gt;
And more&lt;/p&gt;

&lt;p&gt;Why I built it the way I did&lt;br&gt;
I deliberately kept it simple. No login required. No account. No paywall. You land on the page, you search, you copy, you go back to work.&lt;br&gt;
The AI generation is powered by Claude with a QA-specific system prompt — so the output follows actual best practices for each framework version, not just generic code.&lt;br&gt;
The like/dislike system on each snippet is there so the most useful patterns surface over time as more engineers use it.&lt;/p&gt;

&lt;p&gt;What's next&lt;br&gt;
I'm planning to add:&lt;/p&gt;

&lt;p&gt;Page Object Model snippets&lt;br&gt;
CI/CD config snippets (GitHub Actions)&lt;br&gt;
Accessibility testing patterns&lt;br&gt;
A "show equivalent in Cypress/Playwright" toggle&lt;/p&gt;

&lt;p&gt;But honestly the most valuable input right now would come from you. What patterns do you search for most? What's missing? What would make this actually save you time?&lt;/p&gt;

&lt;p&gt;👉 &lt;a href="https://snipqa.vercel.app/" rel="noopener noreferrer"&gt;https://snipqa.vercel.app/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;It's free, no account needed. Try the AI generator and tell me what you think.&lt;/p&gt;

</description>
      <category>testing</category>
      <category>playwright</category>
      <category>cypress</category>
      <category>qa</category>
    </item>
  </channel>
</rss>
