Borrowing it
Nothing to install: this file belongs to MisonL/Ling. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/MisonL/Ling/main/.agents/skills/webapp-testing/SKILL.mdgit clone --depth 1 https://github.com/MisonL/LingWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/misonl/ling/webapp-testing)<a href="https://agentmods.dev/skills/misonl/ling/webapp-testing"><img src="https://agentmods.dev/badge/skills/misonl/ling/webapp-testing.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00028 | $0.01499 |
| Opus 5 | $0.00014 | $0.00749 |
| Sonnet 5 | $0.00006 | $0.00300 |
| Haiku 4.5 | $0.00003 | $0.00150 |
Grade A, and why
webapp-testing scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Web 应用测试
发现并测试一切，不放过任何路由。Web 应用测试（Web App Testing）以完整覆盖为目标。
运行时脚本（Runtime Scripts）
使用以下脚本执行自动化浏览器测试：
| 脚本（Script） | 用途（Purpose） | 用法（Usage） |
|---|---|---|
scripts/playwright_runner.py |
基础浏览器测试 | python scripts/playwright_runner.py <网址> |
| 带截图输出 | python scripts/playwright_runner.py <网址> --screenshot |
|
| 可访问性检查 | python scripts/playwright_runner.py <网址> --a11y |
依赖要求： pip install playwright && playwright install chromium
1. 深度审计方法（Deep Audit Approach）
先做发现（Discovery First）
| 目标（Target） | 如何发现（How to Find） |
|---|---|
| 路由（Routes） | 扫描 app/、pages/、router 文件 |
| API 端点（API Endpoints） | 用 Grep 检索 HTTP 方法 |
| 组件（Components） | 查找组件目录 |
| 功能点（Features） | 阅读相关文档 |
系统化测试（Systematic Testing）
- Map（建图） - 列出全部路由/API
- Scan（扫描） - 验证是否可响应
- Test（测试） - 覆盖关键路径
2. Web 测试金字塔（Testing Pyramid for Web）
/\ 端到端（E2E，少量）
/ \ 关键用户流程
/----\
/ \ 集成测试（Integration，中量）
/--------\ API、数据流
/ \
/------------\ 组件测试（Component，大量）
单个 UI 单元
3. 端到端（E2E）测试原则
测什么（What to Test）
| 优先级（Priority） | 测试内容（Tests） |
|---|---|
| 1 | Happy Path（主流程） |
| 2 | 鉴权流程（Authentication flows） |
| 3 | 关键业务动作 |
| 4 | 错误处理 |
端到端（E2E）最佳实践
| 实践（Practice） | 原因（Why） |
|---|---|
使用 data-testid |
选择器稳定 |
| 等待元素就绪 | 避免不稳定测试（flaky tests） |
| 保持干净状态 | 用例彼此独立 |
| 避免依赖实现细节 | 面向用户行为测试 |
4. Playwright 原则（Playwright Principles）
核心概念（Core Concepts）
| 概念（Concept） | 用途（Use） |
|---|---|
| Page Object Model（页面对象模型） | 封装页面逻辑 |
| Fixtures（测试夹具） | 复用测试准备过程 |
| Assertions（断言） | 内置自动等待能力 |
| Trace Viewer（追踪查看器） | 调试失败用例 |
配置建议（Configuration）
| 设置项（Setting） | 建议（Recommendation） |
|---|---|
| 重试次数（Retries） | CI 中设为 2 |
| Trace（追踪） | on-first-retry |
| Screenshots（截图） | on-failure |
| Video（视频） | retain-on-failure |
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 3d ago First seen · 188 lines · 28 tokens per session scan A f21addc775ff
webapp-testing is a skill published in the GitHub repository MisonL/Ling (8 stars, last pushed 5mo ago), licensed MIT. It adds 28 tokens to every session and 1,499 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
browse
Drive a real browser through Aside: open a page, read it, click through a flow, take screenshots, check console errors. (gstack).
playwright-cli
A command-line tool for controlling Chromium, Firefox, and WebKit browsers, including navigation, page interaction, screenshots, PDFs, and recorded actions.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
browser-qa
A browser-based quality check for deployed web pages and user flows. It uses browser automation to test rendering, navigation, forms, interactions, responsive behaviour, and accessibility-related issues.
test-electron-app
Drive the real running PostHog Electron app (live tRPC, workspace-server, real data) over CDP with agent-browser. Connect to the running app on port 9222, test desktop changes against a local Django stack, snapshot the accessibility tree, inspect network requests, and screenshot only when explicitly asked. Use when…
smoke-test
Run smoke tests against a deployed or local app based on your git diff. Each test uses Skyvern browser tools (navigate, act, validate, screenshot) with Chrome DevTools MCP as fallback. Posts screenshot evidence as PR comments.