<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Testing on Vibe Coding</title><link>https://vibecoding.rest/tags/testing/</link><description>Recent content in Testing on Vibe Coding</description><generator>Hugo</generator><language>en</language><atom:link href="https://vibecoding.rest/tags/testing/index.xml" rel="self" type="application/rss+xml"/><item><title>Puppeteer</title><link>https://vibecoding.rest/mcp-servers/puppeteer/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/mcp-servers/puppeteer/</guid><description>&lt;p&gt;The Puppeteer server gives an agent control of a real (or headless) Chrome browser — navigating to URLs, clicking elements, filling in forms, and capturing screenshots as it goes.&lt;/p&gt;&#10;&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;&#10;&lt;p&gt;Some tasks can only be verified by actually looking at rendered output — a UI change, a broken layout, a JavaScript-heavy page that a plain HTTP fetch can&amp;rsquo;t render. Browser automation closes that verification gap.&lt;/p&gt;</description></item><item><title>Webapp Testing</title><link>https://vibecoding.rest/skills/webapp-testing/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/webapp-testing/</guid><description>&lt;p&gt;The Webapp Testing skill packages a verification workflow: launching a dev server, driving a browser through the golden path and edge cases, and checking console and network output for errors — rather than declaring a UI change complete after just reading the code.&lt;/p&gt;</description></item><item><title>Playwright</title><link>https://vibecoding.rest/mcp-servers/playwright/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/mcp-servers/playwright/</guid><description>&lt;p&gt;Playwright MCP gives an agent structured control over a real browser — Chromium, Firefox, or WebKit — using Playwright&amp;rsquo;s accessibility tree instead of pixel-based screenshots. It exposes tools for navigation, clicking, form filling, and page inspection so an agent can complete multi-step web tasks deterministically.&lt;/p&gt;</description></item><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>Qodo</title><link>https://vibecoding.rest/tools/qodo/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/tools/qodo/</guid><description>&lt;p&gt;Qodo focuses on what happens before and around a merge rather than writing the code itself: a multi-agent review system analyzes pull requests for bugs and standards violations, paired with Qodo Cover for generating unit tests against existing code.&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>