<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Testing &amp; QA on Vibe Coding</title><link>https://vibecoding.rest/category/testing--qa/</link><description>Recent content in Testing &amp; QA on Vibe Coding</description><generator>Hugo</generator><language>en</language><atom:link href="https://vibecoding.rest/category/testing--qa/index.xml" rel="self" type="application/rss+xml"/><item><title>Playwright Browser Automation</title><link>https://vibecoding.rest/skills/playwright-claude/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/playwright-claude/</guid><description>&lt;p&gt;This skill gives Claude Code direct, model-invoked control of Playwright — driving a real browser through a web app&amp;rsquo;s flows to click, fill forms, and validate behavior end-to-end.&lt;/p&gt;&#10;&lt;h2 id="why-a-skill-for-this"&gt;Why a skill for this&lt;/h2&gt;&#10;&lt;p&gt;Reading component code doesn&amp;rsquo;t confirm a flow actually works in a browser. A dedicated Playwright skill turns that verification into a repeatable, invokable step instead of an ad hoc script written from scratch each time.&lt;/p&gt;</description></item><item><title>iOS Simulator</title><link>https://vibecoding.rest/skills/ios-simulator/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/ios-simulator/</guid><description>&lt;p&gt;The iOS Simulator skill lets Claude drive Apple&amp;rsquo;s Simulator directly — building the app, navigating its screens, and exercising flows the way a developer would during manual QA.&lt;/p&gt;&#10;&lt;h2 id="why-a-skill-for-this"&gt;Why a skill for this&lt;/h2&gt;&#10;&lt;p&gt;iOS development often has no equivalent to a browser&amp;rsquo;s headless test runner conveniently available mid-conversation. This skill closes that gap by giving Claude a controllable simulator instead of relying on the developer to manually verify every change.&lt;/p&gt;</description></item><item><title>FFUF Web Fuzzing</title><link>https://vibecoding.rest/skills/ffuf-web-fuzzing/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/ffuf-web-fuzzing/</guid><description>&lt;p&gt;This skill integrates the ffuf web fuzzer, letting Claude run authenticated fuzzing scans, auto-calibrate for noisy responses, and analyze results for real vulnerabilities during a penetration test.&lt;/p&gt;&#10;&lt;h2 id="why-a-skill-for-this"&gt;Why a skill for this&lt;/h2&gt;&#10;&lt;p&gt;Fuzzing tools have enough flags and calibration nuance that getting authenticated, low-noise scans right by hand takes real fuzzer expertise. Packaging that expertise as a skill makes competent fuzzing runs repeatable for anyone using it.&lt;/p&gt;</description></item><item><title>Threat Hunting with Sigma Rules</title><link>https://vibecoding.rest/skills/threat-hunting-sigma/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/threat-hunting-sigma/</guid><description>&lt;p&gt;This skill uses Sigma detection rules — a vendor-neutral format for describing log-based threat signatures — to hunt for suspicious activity and analyze security events.&lt;/p&gt;&#10;&lt;h2 id="why-a-skill-for-this"&gt;Why a skill for this&lt;/h2&gt;&#10;&lt;p&gt;Sigma&amp;rsquo;s rule format is expressive but verbose to write and match by hand across large event logs. A skill that already knows the format turns threat hunting into a repeatable query task instead of a manual log-reading exercise.&lt;/p&gt;</description></item><item><title>Trail of Bits Security Skills</title><link>https://vibecoding.rest/skills/trail-of-bits-security/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/trail-of-bits-security/</guid><description>&lt;p&gt;Trail of Bits&amp;rsquo; security skills bring their own audit tooling — static analysis with CodeQL and Semgrep, variant analysis, and vulnerability pattern detection — into Claude Code.&lt;/p&gt;&#10;&lt;h2 id="why-a-skill-for-this"&gt;Why a skill for this&lt;/h2&gt;&#10;&lt;p&gt;Security auditing firms encode years of hard-won pattern knowledge into their tooling configs. Packaging that as a skill means Claude Code inherits Trail of Bits&amp;rsquo; actual audit methodology instead of a generic security pass.&lt;/p&gt;</description></item><item><title>Chrome Relay</title><link>https://vibecoding.rest/skills/chrome-relay/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/chrome-relay/</guid><description>&lt;p&gt;Chrome Relay drives the user&amp;rsquo;s already-signed-in Chrome session — cookies, SSO, localhost included — through a local CLI bridge, as a real-browser counterpart to headless Playwright automation.&lt;/p&gt;&#10;&lt;h2 id="why-a-skill-for-this"&gt;Why a skill for this&lt;/h2&gt;&#10;&lt;p&gt;Some flows only work correctly inside an authenticated, already-logged-in browser session — SSO-gated internal tools, for instance. Relaying through the real Chrome session sidesteps re-authenticating a separate automated browser.&lt;/p&gt;</description></item><item><title>Full-Page Screenshot</title><link>https://vibecoding.rest/skills/full-page-screenshot/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/full-page-screenshot/</guid><description>&lt;p&gt;This skill captures full-page screenshots of web pages via the Chrome DevTools Protocol, with zero external dependencies.&lt;/p&gt;&#10;&lt;h2 id="why-a-skill-for-this"&gt;Why a skill for this&lt;/h2&gt;&#10;&lt;p&gt;Full-page capture (beyond the visible viewport) usually needs either a heavier automation framework or manual scrolling-and-stitching. Talking to the DevTools Protocol directly gets a clean full-page image without either.&lt;/p&gt;</description></item><item><title>PICT Test Case Design</title><link>https://vibecoding.rest/skills/pict-test-case-design/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/pict-test-case-design/</guid><description>&lt;p&gt;This skill designs comprehensive pairwise-combinatorial test suites from requirements or code, using Microsoft&amp;rsquo;s PICT methodology to keep the case count manageable.&lt;/p&gt;&#10;&lt;h2 id="why-a-skill-for-this"&gt;Why a skill for this&lt;/h2&gt;&#10;&lt;p&gt;Testing every combination of inputs is usually infeasible, but pairwise coverage catches most real-world combinatorial bugs with far fewer cases. PICT&amp;rsquo;s methodology is the standard way to generate that reduced set correctly.&lt;/p&gt;</description></item><item><title>Playwright Testing Skill</title><link>https://vibecoding.rest/skills/playwright-codex/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/playwright-codex/</guid><description>&lt;p&gt;OpenAI&amp;rsquo;s curated Playwright skill gives Codex the same browser-automation and interactive test-authoring capability as its Claude Code counterpart, packaged for Codex&amp;rsquo;s skill system.&lt;/p&gt;&#10;&lt;h2 id="why-a-skill-for-this"&gt;Why a skill for this&lt;/h2&gt;&#10;&lt;p&gt;Verifying a web app in a real browser matters regardless of which coding agent is driving the session — this is the Codex-native equivalent of that same verification step.&lt;/p&gt;</description></item></channel></rss>