Playwright E2E Tests
onyx-dot-app/onyx
Write and maintain Playwright end-to-end tests for the Onyx application.
Provides Playwright MCP testing workflow for the web application.
Install Testing With Playwright
$ npx skills add microsoft-foundry/foundry-agent-webapp --skill testing-with-playwright -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install microsoft-foundry/foundry-agent-webapp testing-with-playwright --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/microsoft-foundry/foundry-agent-webapp.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/testing-with-playwright .claude/skills/testing-with-playwright && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "testing-with-playwright" agent skill from https://github.com/microsoft-foundry/foundry-agent-webapp/tree/main/.github/skills/testing-with-playwright into .claude/skills/testing-with-playwright/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testing-with-playwright", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/microsoft-foundry/foundry-agent-webapp/tree/main/.github/skills/testing-with-playwrightType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add microsoft-foundry/foundry-agent-webapp --skill testing-with-playwright -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install microsoft-foundry/foundry-agent-webapp testing-with-playwright --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/microsoft-foundry/foundry-agent-webapp.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.github/skills/testing-with-playwright .agents/skills/testing-with-playwright && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "testing-with-playwright" agent skill from https://github.com/microsoft-foundry/foundry-agent-webapp/tree/main/.github/skills/testing-with-playwright into .agents/skills/testing-with-playwright/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testing-with-playwright", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add microsoft-foundry/foundry-agent-webapp --skill testing-with-playwright -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install microsoft-foundry/foundry-agent-webapp testing-with-playwright --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/microsoft-foundry/foundry-agent-webapp.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.github/skills/testing-with-playwright .cursor/skills/testing-with-playwright && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "testing-with-playwright" agent skill from https://github.com/microsoft-foundry/foundry-agent-webapp/tree/main/.github/skills/testing-with-playwright into .cursor/skills/testing-with-playwright/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testing-with-playwright", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/microsoft-foundry/foundry-agent-webapp.git --path .github/skills/testing-with-playwright--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add microsoft-foundry/foundry-agent-webapp --skill testing-with-playwright -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install microsoft-foundry/foundry-agent-webapp testing-with-playwright --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/microsoft-foundry/foundry-agent-webapp.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.github/skills/testing-with-playwright .gemini/skills/testing-with-playwright && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "testing-with-playwright" agent skill from https://github.com/microsoft-foundry/foundry-agent-webapp/tree/main/.github/skills/testing-with-playwright into .gemini/skills/testing-with-playwright/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testing-with-playwright", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install microsoft-foundry/foundry-agent-webapp testing-with-playwrightInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add microsoft-foundry/foundry-agent-webapp --skill testing-with-playwright -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/microsoft-foundry/foundry-agent-webapp.git skills-src && mkdir -p .github/skills && cp -r skills-src/.github/skills/testing-with-playwright .github/skills/testing-with-playwright && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "testing-with-playwright" agent skill from https://github.com/microsoft-foundry/foundry-agent-webapp/tree/main/.github/skills/testing-with-playwright into .github/skills/testing-with-playwright/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testing-with-playwright", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add microsoft-foundry/foundry-agent-webapp --skill testing-with-playwright -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install microsoft-foundry/foundry-agent-webapp testing-with-playwright --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/microsoft-foundry/foundry-agent-webapp.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.github/skills/testing-with-playwright .opencode/skills/testing-with-playwright && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "testing-with-playwright" agent skill from https://github.com/microsoft-foundry/foundry-agent-webapp/tree/main/.github/skills/testing-with-playwright into .opencode/skills/testing-with-playwright/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testing-with-playwright", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
testing-with-playwright- GitHub stars
- 127
- Token cost
- ~1.2k tokens
- SKILL.md length
- 402 words
- Files
- 1
- Skills in repo
- 19
- Repo updated
- First seen
- Licence
- MIT
At a glance
Provides Playwright MCP testing workflow for the web application.
- Works in 5 steps: Browser console logs - Check console… → VS Code terminal logs - Check terminal… → Network requests - Inspect API calls and… → …
- Testing UI changes
- SKILL.md covers Subagent Delegation for Testing, Testing Priority (Token…, Workflow and When to Test, plus 6 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Testing With Playwright is an agent skill from microsoft-foundry/foundry-agent-webapp. Provides Playwright MCP testing workflow for the web application. Use when testing UI changes, verifying chat functionality, debugging frontend issues, or validating state transitions in the browser.
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Testing & QA, covering Browser testing. It works with Playwright, Model Context Protocol and Visual Studio Code. The repository describes itself as: GitHub Copilot enabled repo for building and deploying a web application with Entra ID authentication and integrated with Azure AI Foundry Agents. The licence is MIT.
When your agent uses it
- Testing UI changes
- Verifying chat functionality
- Debugging frontend issues
- Validating state transitions in the browser
Example prompts
- “Use the testing-with-playwright skill to provide Playwright MCP testing workflow for the web application”
- “/testing-with-playwright”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Browser console logs - Check console messages for state transitions and errors
- VS Code terminal logs - Check terminal output for backend/frontend server logs
- Network requests - Inspect API calls and status codes
- Accessibility snapshot - Get DOM structure for element verification
- Screenshots - Visual verification (use sparingly, high token cost)
What it can do on your machine
Read from SKILL.md and the folder at commit f6cb362. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are powershell).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Testing With Playwright loads about 1.2k tokens when it runs. Until then it costs about 56 tokens; SKILL.md has 402 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from microsoft-foundry/foundry-agent-webapp at commit f6cb362, republished under its MIT licence (© microsoft-foundry). 402 words, ~1,242 tokens.
Download SKILL.mdSave it as
.claude/skills/testing-with-playwright/SKILL.md (or your agent's skills folder).- name
- testing-with-playwright
- description
- Provides Playwright MCP testing workflow for the web application. Use when testing UI changes, verifying chat functionality, debugging frontend issues, or validating state transitions in the browser.
Testing with Playwright MCP
CRITICAL: Always test changes before completion.
Subagent Delegation for Testing
Screenshot operations blow up context fast (~2000-5000 tokens each). Delegate to subagent for:
- Multi-step UI test scenarios
- Visual regression verification
- Accessibility audits
- Screenshot-heavy debugging
Delegation Pattern
runSubagent(
prompt: "TESTING task with Playwright MCP.
**Servers**: Frontend at localhost:5173, Backend at localhost:8080
**Test Scenario**: [describe what to verify]
**Steps**:
1. Navigate to http://localhost:5173
2. [specific actions to perform]
**Check in priority order** (stop when answer found):
1. Browser console logs - look for errors, state transitions (🔄)
2. Network requests - verify API calls and status codes
3. Accessibility snapshot - check element presence
4. Screenshot - ONLY if visual verification essential
**Return**:
- Pass/Fail result
- Specific evidence (error messages, status codes, element presence)
- Console action log if relevant (🔄 ACTION_TYPE entries)
Do NOT include raw screenshots or full accessibility dumps.",
description: "Test: [what being verified]"
)When to Delegate vs Inline
| Delegate to Subagent | Keep Inline |
|---|---|
| Multi-page flows | Single console check |
| Visual verification needed | Network status check |
| Accessibility audit | Element presence (single) |
| Error reproduction | Quick state verification |
| Screenshot required | Reading console logs |
Testing Priority (Token efficiency)
- Browser console logs - Check console messages for state transitions and errors
- VS Code terminal logs - Check terminal output for backend/frontend server logs
- Network requests - Inspect API calls and status codes
- Accessibility snapshot - Get DOM structure for element verification
- Screenshots - Visual verification (use sparingly, high token cost)
Key insight: Browser console shows React state changes (🔄 ACTION_TYPE), errors, and warnings. VS Code terminals show server logs and compilation output.
Workflow
Start servers in VS Code terminals (preferred - logs visible to AI agent):
# Run these VS Code tasks:
# - "Backend: ASP.NET Core API" (dotnet watch, port 8080)
# - "Frontend: React Vite" (npm run dev, port 5173)
# Or use compound task: "Start Dev (VS Code Terminals)"Then test with Playwright MCP:
- Navigate to http://localhost:5173
- Check browser console for state transitions and errors
- Verify network requests for API calls
- Take accessibility snapshot for DOM validation
Check server logs:
- Check VS Code terminal output for backend compilation and request logs
- Backend terminal shows: request handling, errors, recompilation status
- Frontend terminal shows: HMR updates, build warnings, Vite output
When to Test
- After UI component or API endpoint changes
- Before committing multi-step implementations
- When user reports issues
Show full SKILL.md (156 more words)Show less
Validation Checklist
- Console shows expected actions (🔄 [timestamp] ACTION_TYPE)
- No console errors/warnings
- Network tab shows correct status codes (200/400/401/500)
- DOM elements present in accessibility snapshot
State Logging (Dev Mode)
Each state change prints:
🔄 [HH:MM:SS] ACTION_TYPE
Action: { … }
Changes: { field: before → after }Project-Specific: Key Test Scenarios
| Scenario | What to Verify |
|---|---|
| Initial load | Auth redirect, agent metadata loads |
| Send message | User message appears, streaming starts |
| Streaming | Text chunks append, no flicker |
| Annotations | Citations render with links |
| Cancel stream | Input re-enabled, status → idle |
| Error recovery | Retry button works, error clears |
Project-Specific: Network Verification
| Endpoint | Success | Failure |
|---|---|---|
POST /api/chat/stream | 200 + SSE events | 401 (auth), 400 (validation) |
GET /api/agent/info | 200 + JSON metadata | 500 (agent not found) |
Playwright MCP
| Capability | Token Cost |
|---|---|
| Navigate | Low |
| Console logs | Low |
| Click / Type | Low |
| Accessibility snapshot | Medium |
| Screenshot | High |
Use console logs for state verification. Use snapshots for element presence. Avoid screenshots unless visual check required.
Related Skills
- validating-ui-features - Detailed test procedures for specific features
- writing-typescript-code - Frontend patterns and state management
- implementing-chat-streaming - SSE flow verification
© microsoft-foundry, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .github/skills/testing-with-playwright of microsoft-foundry/foundry-agent-webapp.
Open the folder on GitHubat commit f6cb362
Compare with similar skills
Testing With Playwright next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Testing With Playwright this skillmicrosoft-foundry/foundry-agent-webapp | 127 | — | ~1.2k | Automated safety check: Pass | MIT | |
| Playwright E2E Testsonyx-dot-app/onyx | 32k | 1 repos | ~2.8k | Automated safety check: Notes | Custom licence | |
| Shogun Screenshotyohey-w/multi-agent-shogun | 1.4k | — | ~901 | Automated safety check: Notes | MIT | |
| Playwright Debugvoicetreelab/voicetree | 922 | — | ~1.2k | Automated safety check: Pass | Custom licence | |
| Hands On Testktnyt/cclsp | 675 | — | ~1.7k | Automated safety check: Pass | MIT | |
| E2E VerificationChorus-AIDLC/Chorus | 1.2k | — | ~1.5k | Automated safety check: Notes | AGPL-3.0 |
Similar skills
Shogun Screenshot
yohey-w/multi-agent-shogun
スクリーンショットの取得・加工を行う。ローカルスクショから最新画像を取得、 PlaywrightでWebページをキャプチャ、画像のトリミング・リサイズ、機微情報を黒塗りマスキング。
Playwright Debug
voicetreelab/voicetree
This skill should be used when the user asks to "debug the electron app", "connect playwright to VoiceTree", "take screenshots of the running app", "interact with the live UI", "inspect the running…
Hands On Test
ktnyt/cclsp
Performs manual hands-on testing of a web application using playwright-cli.
E2E Verification
Chorus-AIDLC/Chorus
A skill your agent uses when manually verifying a Chorus frontend change in a real browser — finding local login credentials, driving the running dev server with the Playwright MCP, logging in…
UI Regression Recorder
xuxh21/ui-regression-recorder-skill
A skill your agent uses when the user says to initialize the current project for UI regression, record an operation, convert Playwright codegen recordings into stable tests, extract shared helpers…
More from microsoft-foundry/foundry-agent-webapp
All 19 skills in this repoCommitting Code
microsoft-foundry/foundry-agent-webapp
Provides commit message format and workflow for this repository.
Implementing Chat Streaming
microsoft-foundry/foundry-agent-webapp
Provides SSE streaming patterns for the chat API and frontend.
Planning Features
microsoft-foundry/foundry-agent-webapp
Provides structured plan template for feature implementation.
Researching Azure AI SDK
microsoft-foundry/foundry-agent-webapp
Provides research patterns for Foundry Agent Service SDK. An agent skill from microsoft-foundry/foundry-agent-webapp.
Deploying To Azure
microsoft-foundry/foundry-agent-webapp
Provides deployment commands and troubleshooting for Azure Container Apps.
Syncing MCP Servers
microsoft-foundry/foundry-agent-webapp
Synchronize MCP server configuration between VS Code (.vscode/mcp.json) and Copilot CLI (~/.copilot/mcp-config.json).
Related
Categories
Questions about Testing With Playwright
What does Testing With Playwright do?
Provides Playwright MCP testing workflow for the web application. Testing With Playwright is an agent skill from microsoft-foundry/foundry-agent-webapp. Provides Playwright MCP testing workflow for the web application.
When should I use Testing With Playwright?
Testing With Playwright fits situations like: testing UI changes; verifying chat functionality; debugging frontend issues; validating state transitions in the browser.
How do I install Testing With Playwright in Claude Code?
Run `npx skills add microsoft-foundry/foundry-agent-webapp --skill testing-with-playwright -a claude-code`. Or copy the skill folder (.github/skills/testing-with-playwright in microsoft-foundry/foundry-agent-webapp) into .claude/skills/testing-with-playwright in your project. Claude Code loads it when a task matches its description.
How do I install Testing With Playwright in Codex?
Run `npx skills add microsoft-foundry/foundry-agent-webapp --skill testing-with-playwright -a codex`. Or copy the skill folder (.github/skills/testing-with-playwright in microsoft-foundry/foundry-agent-webapp) into .agents/skills/testing-with-playwright in your project. Codex loads it when a task matches its description.
Can I use Testing With Playwright in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add microsoft-foundry/foundry-agent-webapp --skill testing-with-playwright -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/testing-with-playwright, .gemini/skills/testing-with-playwright, .github/skills/testing-with-playwright and .opencode/skills/testing-with-playwright in your project.
What does Testing With Playwright need to run?
SKILL.md names no scripts, command-line tools or credentials: Testing With Playwright is instructions for the agent only.
Does Testing With Playwright access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Testing With Playwright safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Testing With Playwright use?
Testing With Playwright is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Testing With Playwright use?
About 1.2k tokens (SKILL.md is roughly 5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Testing With Playwright?
Skills that share tags, products or a category with Testing With Playwright: Playwright E2E Tests (onyx-dot-app/onyx, 32k stars), Shogun Screenshot (yohey-w/multi-agent-shogun, 1.4k stars), Playwright Debug (voicetreelab/voicetree, 922 stars) and Hands On Test (ktnyt/cclsp, 675 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Testing With Playwright?
microsoft-foundry (a GitHub organization) maintains it in microsoft-foundry/foundry-agent-webapp, which has 127 GitHub stars. The repository holds 19 skills in this directory. The repository was last updated on April 21, 2026.
Source: microsoft-foundry/foundry-agent-webapp on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.