Playwright 命令行 playwright-cli
io.github.microsoft/playwright/playwright-cli
自动化浏览器交互、测试网页并处理 Playwright 测试。
“Playwright” 共 93 个结果
io.github.microsoft/playwright/playwright-cli
自动化浏览器交互、测试网页并处理 Playwright 测试。
io.github.microsoft/playwright/playwright-release-notes
Write the release notes for a Playwright release - the Node.js notes in docs/src/release-notes-js.md together with the Python, Java and .NET translations, and the GitHub markdown for each language's release. Use when asked to write, translate or publish release notes.
io.github.microsoft/playwright/playwright-dev
讲解如何开发 Playwright——添加 API、MCP 工具、CLI 命令与引入 vendor 依赖。
io.github.microsoft/playwright/playwright-triage
根据 bug 报告中提供的信息复现并分诊 Playwright issue。当被要求分诊、复现或验证 GitHub issue(新的 bug 报告,或已有报告的新评论)时使用。
io.github.microsoft/playwright/playwright-test-results
从聚合的 DuckDB 数据库中查询 Playwright CI 测试结果。可回答关于不稳定(flaky)测试、失败率、慢测试,以及按运行/SHA/PR 维度的结果等问题,无需在 GitHub 制品中翻找。
io.github.microsoft/playwright/playwright-component-testing
使用内置故事画廊(story gallery)搭建 Playwright 组件测试——由内置 mount fixture 驱动 story 脚手架与画廊开发页,无需专用组件测试运行时。当被要求用 Playwright 对 React 或 Vue 组件做隔离测试,或从 @playwright/experimental-ct-react / -vue 迁移时使用。
io.github.langgenius/dify/e2e-cucumber-playwright
在 e2e/ 下编写、修改或审查 Cucumber 与 Playwright 测试时使用,涵盖 feature 文件、step 定义、支撑代码、scenario 标签、定位器和断言。不适用于 Vitest、React Testing Library、后端测试或 E2E 套件之外的通用浏览器自动化。
io.github.Comfy-Org/ComfyUI_frontend/writing-playwright-tests
为 ComfyUI_frontend 编写 Playwright 端到端测试。在创建、修改或调试浏览器测试时使用。触发词:playwright、e2e test、browser test、spec file
io.github.PramodDutta/qaskills/playwright-mobile-web
使用 Playwright 设备模拟进行移动 Web 测试,涵盖响应式测试、触摸交互、视口管理、网络限速、地理位置测试与移动端专属 UI 模式。
io.github.open-metadata/OpenMetadata/writing-playwright-tests
在编写新的 Playwright E2E 测试或新增测试用例时使用。提供源自 Playwright Developer Handbook 的测试理念、模式与最佳实践。
io.github.microsoft/playwright/api-review
Produce the "Playwright 1.xx API Review" artifact for a range of commits - the public API additions and the breaking or behavior changes that affect existing users since the last API review or since the last release, ordered by impact, each with links, before/after snippets and a documentation check. Covers microsoft/playwright (Node.js) and the Python, Java and .NET ports. Use when asked for an API review, to review API changes, or to check what changed in the public API since a release or since the last review.
io.github.stablyai/orca/orchestration
协调受监督的 Orca worker:线程消息、阻塞式问答、任务派发、worker_done/escalation 等待、任务 DAG、决策关卡以及 agent 间的工作分解。完全所有权移交("hand off"、"handoff"、"give this to another agent"、"another worktree")用 orca-cli,除非需要监督、监控或协调 DAG;终端控制、轻量终端提示、shell 命令、Orca 工作树管理、读取/等待终端也用 orca-cli。仅当需要 OS/窗口级控制(焦点、菜单、对话框、坐标、截图)时,才用 Computer Use 操作外部浏览器窗口、webview、Orca 应用 UI 或 Orca 内置浏览器之外的桌面 UI。Orca 内置页面用 orca-cli,外部页面用 Playwright/CDP 等页面自动化工具。
io.github.grafana/grafana/frontend-testing-strategy
按本仓库约定为 Grafana 前端代码(React/TypeScript,任意包或功能域)编写单元与 E2E 测试。新增、补齐或审查前端测试时使用;测试仅断言“渲染成功/已定义”、AI 生成测试质量存疑、或前端测试不稳定时同样适用。涉及可视化面板与 grafana-ui 可视化组件时,另需加载 panel-testing-strategy skill。
io.github.anomalyco/opencode/component-tests
Use when writing, changing, debugging, or reviewing the Playwright component tests that mount stories. That covers specs in packages/app/component-tests or packages/session-ui/component-tests, `*.fixture.tsx` files there or beside source (such as packages/gui-plugins/src/browser/panel.fixture.tsx), the stories they mount, and the shared harness in packages/stories (playwright/config.ts, playwright/story.ts, vite.config.ts, src/frame.tsx, src/index-plugin.ts, mocks). Also use when a component test is flaky, passed on retry, or fails with "Execution context was destroyed", "Failed to fetch dynamically imported module", or `#story-root` hidden. Covers mount args, source modules imported by URL, Vite dependency pre-bundling and reloads, a cold vs warm story server, mobile drawers, geometry, and checks before pushing.
io.github.browser-use/browser-use/browser-use
通过 CDP 直接控制浏览器完成 web 交互:自动化、抓取、测试、截图以及站点/应用操作。
io.github.browser-use/browser-use/cloud
Browser Use Cloud(托管版浏览器自动化 API)文档参考。凡涉及 Cloud REST API(v2、v3 或 v4)、browser-use-sdk(Python 或 TypeScript)、X-Browser-Use-API-Key 鉴权、cloud sessions、浏览器 profile、profile 同步、CDP WebSocket 连接、隐身浏览器、住宅代理、验证码处理、webhook、workspace、skill 市场、liveUrl 流、定价,以及集成模式(聊天界面、subagent、把浏览器工具接入已有 agent)时使用。n8n/Make/Zapier 集成、云上 Playwright/Puppeteer/Selenium、1Password 密钥库相关问题也适用。不适用于开源 Python 库(Agent、Browser、Tools 配置)——那些请用 open-source skill。
io.github.OpenHands/OpenHands/e2e-testing
This skill should be used when the user asks to "add an E2E test", "run live E2E", "run mock-LLM tests", "debug Playwright CI", "test the Docker image", or changes tests/e2e, Playwright configs, E2E workflows, artifacts, or test reporting.
io.github.deepseek-ai/deepseek-harness/record-browser-gif
使用可用的浏览器控制工作流,可选 Playwright Videos 提升采集帧率,并以确定性编码把浏览器或 Web UI 交互演示录制为优化后的 GIF,再用 gh --attach 将 GIF 附到 PR 上;无法附加时回退到专用 assets 分支。在被要求制作、录制或生成演示浏览器工作流的 GIF 时使用;凡改动面向产品用户的 GUI 行为的 PR,都必须附带从该 PR 真实服务端与模型流程录制的 GIF。
io.github.Stirling-Tools/Stirling-PDF/ui-walkthrough
对当前分支功能做完整的 UI 调查。枚举每个视图与状态(空态、有数据、加载、错误、每个对话框/菜单/面板、响应式断点、浅色+暗色+RTL),用内置 Playwright 工装捕获,汇总为带全局明暗切换滑杆的单图 HTML 走查,随后跑两轮审查:视觉/一致性(对齐、间距、专业感、明暗一致、对比度、截断)与 UX/易用性(流程、可发现性、可供性、空态/错误态、预期)。当被要求做 UI 走查、截图审查、设计或 QA 巡检、「找出可以更易用/更好的地方」或前端工作合并前使用。加 --fix 自动应用安全的前端修复并重新捕获;--theme 限定主题;--no-rtl 跳过 RTL。
io.github.outline/outline/verify-outline
Launch an isolated Outline instance (web UI + API, production build, own Postgres/Redis containers) from the current checkout and drive it in a headless browser to prove a user-facing change works, with screenshots, Playwright traces and database checks as evidence. Use when asked to verify, demo, reproduce or screenshot Outline behavior in the real app, rather than only in unit tests.
io.github.alirezarezvani/claude-skills/engineering-skills
工程团队技能包的索引,支持 Claude Code、Codex、Gemini CLI、Cursor、OpenClaw 及另外 6 种工具。涵盖架构、前端、后端、QA、DevOps、安全、AI/ML、数据工程、Playwright、Stripe、AWS、MS365(仅 stdlib Python 工具)。用于浏览或选择工程团队角色技能——只加载所需的单个专家 SKILL.md,切勿批量加载整个技能包。
io.github.anomalyco/opencode/app-e2e-tests
Use when writing, changing, reviewing, or debugging Playwright e2e tests in packages/app/e2e (regression keepers and user stories). Covers the mocked opencode server harness and the Bun static server, per-test isolation, page-load and route cost, the suite-wide service-worker block, races with first mount, hover, measurement, clock, dialogs and shortcuts, projects, shards and worker scheduling, rehearsing Windows timing locally, and diagnosing a CI flake from its artifacts. Not for Storybook component tests or e2e/performance benchmarks.
io.github.affaan-m/ECC/e2e-testing
Playwright E2E testing patterns, Page Object Model, configuration, CI/CD integration, artifact management, and flaky test strategies. Use when writing Playwright tests, structuring page objects, or fixing flaky E2E runs in CI.
io.github.affaan-m/ECC/react-testing
React component testing with React Testing Library, Vitest/Jest, MSW for network mocking, accessibility assertions with axe, and the decision boundary between component tests and Playwright/Cypress end-to-end runs. Use when writing or fixing tests for React components, hooks, or pages.