webapp-testing
Use this skill to build features or debug anything that uses a webapp frontend.
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 4.9k
- Forks
- 590
01 前言 Front Matter
- name
- webapp-testing
- description
- Use this skill to build features or debug anything that uses a webapp frontend.
02 资源文件 1
- 资产文件assets/fan-out-pool.md1.3 KB
03 SKILL.md 正文
<required> CRITICAL Add the following steps to your Todo list using TodoWrite:
<system-reminder>From this point on, ignore any existing tests until you have a working example validated through a new playwright file.</system-reminder>
- Install playwright. Use the SDK that best matches the codebase. Default to python.
- Write a playwright config file. Make sure you use reporter: 'list' mode.
- If using python, you must use a virtual env.
- Check to see if you require authentication. If you do, ask me for credentials. <system-reminder>Do NOT use mock mode or test harnesses. You should be testing the real thing.</system-reminder>
- Write and run a playwright script that lets you interact with the webapp frontend.
- Follow these steps in a loop until the bug is fixed:
- Add many logs to the server and to the UI. You MUST do this on every loop.
- Start the server and the UI.
- Run the playwright script and identify what is happening. Take screenshots, read logs, do whatever you need to.
- Update the playwright script. <system-reminder>If you get stuck: did you add logs?</system-reminder>
- Run a final demonstration of the playwright browser NOT in headless mode. This is to show me directly what you accomplished.
- Clean up all background jobs and close any browsers.
- Make sure other tests pass. </required>
Web Application Testing
To test local web applications, write native Python Playwright scripts. Your testing should be as close to 'real' as possible.
Example
Identify the server
Single server:
npm run dev" --port 5173
Multiple servers (e.g., backend + frontend):
cd backend && python server.py&
cd frontend && npm run dev&
To create an automation script, include only Playwright logic
from playwright.sync_api import sync_playwright
with sync_playwright() as p:
browser = p.chromium.launch(headless=True) # Always launch chromium in headless mode
page = browser.new_page()
page.goto('http://localhost:5173') # Server already running and ready
page.wait_for_load_state('networkidle') # CRITICAL: Wait for JS to execute
# ... your automation logic
browser.close()
<system-reminder>If Playwright is not available, install it in a virtual env.</system-reminder>
Do NOT get in a loop where you just keep running tests. In this mode, you should ignore tests entirely until it works.
04 同仓库更多 Skills
trigger-pipelines-for-copilot-pr
Trigger ADO pipelines for a Copilot-created PR by posting /azp run comments. Use when the user asks to trigger CI pipelines for a specific PR.
review
Review changes relative to a prior state, such as a diff, pull request, branch, commit, or working-tree changes. Use for change-focused code review and regression analysis. Do not use to assess an existing file, API, design, implementation, or other artifact without a comparison; if the request is ambiguous, ask whether the user wants a change review and what prior state to compare against.
review-pr-local
The authority on pulling a pull request — Azure DevOps or GitHub — into an isolated local worktree so a human can review it in their editor, and on posting human-controlled review comments back to the PR (ADO via the ado PR-thread MCP tools or the Azure DevOps REST API, GitHub via the gh CLI). Auto-detects the platform and all identifiers from the PR URL; not tied to any specific repository. The AI assists an interactive human review and only ever posts comments the human explicitly requests. If you find yourself checking out a PR branch over the user's own working tree, or posting AI-authored review prose the human did not ask for, invoke this skill instead.
policy-check
This skill should be used when the user asks to "run policy check", "check policy", "policy-check", or needs to validate package compliance. Provides guidance on running policy checks for specific packages or the entire repository.
pipeline-test-triage
Triage test failures in an Azure DevOps pipeline run for Fluid Framework. Use when the user shares an ADO build/pipeline URL or build ID and wants failures analyzed, when they ask "why did this pipeline fail", "summarize the test failures", "is this test flaky or a real bug", "compare these runs", or wants bugs filed for genuine failures. Covers the Real Service End to End Tests pipeline as the worked example but applies to any FF test pipeline.
fluid-release
Fluid Framework client release group — minor releases, patch releases, and post-release type test updates. Covers release prep, branching, version bumps, changelogs, release notes, and type test baselines. In autonomous mode, auto-detects state from the repo, attempts to execute, and falls back to a GitHub issue on failure. Triggers on "release", "do the release", "release status", version bump, release notes, changelog, release branch, or release engineering.