Playwright 瀏覽器自動化
Playwright 瀏覽器自動化
用 Playwright 規劃穩定的端對端瀏覽器工作流程。
magnus919 · 社群來源 · 測試與除錯
來源狀態
可用來源
原始名稱: playwright
原始作者: magnus919
這是第三方 Community Skill;2lus 收錄不代表已完整安全審計或保證安全。
資源類型
Skill
與類似 Skill 有什麼不同?
- Playwright 網站測試
官方 Playwright 卡介紹工具基礎;此卡聚焦穩定 E2E 工作流程、mock 與 CI。
來源描述的能力
這些是來源描述的可能操作,不代表 2lus 已授予權限或已測試。
尚未列出能力,請審查原始來源。
這個 Skill 是什麼?
以可讀定位器、隔離網路依賴及 CI 分析驗證使用者旅程。
可以做什麼?何時適合使用?
- 設計登入至結帳 E2E
- 攔截 API 建立可重複情境
- 分析平行執行與失敗 trace
如何使用
- 定義真實使用者流程與可觀察結果
- 優先使用 role/label 定位器並控制網路回應
- 規劃隔離、平行、CI、accessibility snapshot 與 trace 分析
使用前你需要準備
- 頁面流程與測試環境
- Playwright 版本及 API 契約
你可以替換:
請提供版本、來源資料、目標與限制。
環境與相依需求
- 頁面流程與測試環境
- Playwright 版本及 API 契約
使用範例與 Prompt
以下是 2lus 撰寫的示範需求;請替換為你有權處理的檔案與專案,不代表已執行或保證結果。
入門
為搜尋表單設計 role locator 和成功狀態斷言。
實務
為付款錯誤情境規劃 network mock 與重試後畫面驗證。
進階
設計可平行執行的 CI E2E、aria snapshot 與失敗 trace 分析流程。
實用提醒
- 避免固定 sleep;等待使用者可觀察狀態。
限制與注意事項
- 測試碼與 snapshot 仍需人工判斷,亦不能證明完整無障礙合規。
安全注意事項
- 測試帳號與 token 不寫入記錄;headless 擷取須尊重資料權限。
使用與設定
此條目不提供已確認的通用安裝指令;請依官方文件與 Agent 版本操作。
支援平台
未確認特定 Agent 相容性
來源與授權
來源查核日期(非安全認證): 2026-10-01
MIT
原始來源 ↗ 官方文件 ↗相關 Skills
使用第三方 Skill 前,請先檢查來源、權限與執行內容。安裝指令只供查看與複製,不會由 2lus 執行。
2lus AI Skills Library 提供 Skill 的整理與使用導覽。第三方 Skill 的內容、授權與可用性以原始來源為準。使用或安裝前,請自行確認其權限與執行內容。
Playwright Browser Automation
Plan stable end-to-end browser workflows with Playwright.
magnus919 · Community source · Testing & Debugging
Source status
Active source
Original name: playwright
Original author: magnus919
This is a third-party community skill. Inclusion by 2lus is not a complete security audit or safety guarantee.
Resource type
Skill
How is this different from similar skills?
- Playwright
The official Playwright card covers foundations; this card focuses on applied E2E workflows, mocks, and CI.
Documented capabilities
These are operations described upstream, not permissions granted or tested by 2lus.
Capabilities not declared here; review the original source.
What is this skill?
Verify user journeys with readable locators, isolated network dependencies, and CI evidence.
Use cases and when to use it
- Design login-to-checkout E2E
- Intercept APIs for repeatable scenarios
- Analyze parallel runs and failure traces
How to use it
- Define user journeys and observable outcomes
- Prefer role/label locators and controlled responses
- Plan isolation, parallelism, CI, accessibility snapshots, and trace review
What you need
- Page workflow and test environment
- Playwright version and API contract
You can replace:
Provide versions, source material, goals, and constraints.
Environment and dependencies
- Page workflow and test environment
- Playwright version and API contract
Usage and prompt examples
These example requests were written by 2lus. Substitute files and projects you may use; examples are not executed results or guarantees.
Beginner
Design role locators and observable assertions for a search form.
Practical
Plan network mocks and retry-state checks for a payment error flow.
Advanced
Design parallel CI E2E, aria snapshots, and failure trace analysis.
Tips
- Avoid fixed sleeps; wait for user-observable states.
Limitations
- Tests and snapshots need human interpretation and do not establish full accessibility conformance.
Security notes
- Keep test accounts and tokens out of logs; respect data permissions during headless extraction.
Usage and setup
No verified universal installation command is provided for this entry. Follow the official documentation for your agent version.
Supported agents
Specific agent compatibility unknown
Sources and license
Source check date (not a safety certification): 2026-10-01
MIT
Original source ↗ Documentation ↗Related skills
Before using a third-party skill, review its source, permissions and executable content. Commands are for viewing and copying only; 2lus does not execute them.
2lus AI Skills Library provides curated educational guides. Third-party content, licenses and availability are governed by their original sources. Review permissions and executable content before use or installation.