Multica Test T3 UI Automation
T3 UI 自动化:pytest+Playwright,1 功能用例 = 1 个 e2e 测试;路径读 MULTICA.md §2;在 deploy URL 执行。
Install
npx skills add it235/multica-best-practices --skill multica-test-t3-ui-automationgit clone --depth 1 https://github.com/it235/multica-best-practices.git /tmp/multica-best-practices
mkdir -p ~/.claude/skills
cp -r /tmp/multica-best-practices/templates/zh_CN/skills/tester/multica-test-t3-ui-automation ~/.claude/skills/multica-test-t3-ui-automationPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Test UI Automation(功能用例 → UI 1:1) 把 **T1 Confluence / T2 入库** 的 Playwright 用例在 **部署环境** 执行。 > T2 应在 **MULTICA.md §2 UI E2E 路径** 编写/积累脚本(见 `docs/test-automation-in-repo.md`)。T3 门禁见 `multica-test-orchestration`。 ## Platform 协作 | Platform skill | 本 skill 用途 | | --- | --- | | — | 无直接 platform 调用;`page_url` / 用例集来自 Issue 评论与 T1 产物 | UI 在部署环境执行;环境 URL 由 DevOps / Leader 写入 JIRA 评论(见 `multica-artifact-cicd-sync`)。 ## 原则 - **入仓路径**:Read 目标 repo **MULTICA.md §2**(分仓按 Issue 矩阵各读一份);缺文件 → BLOCKED - **无 e2e 目录时**:在 MULTICA 指定路径按 `framework-template.md` 初始化(禁止 `/tmp/ui-auto-*`) - **禁止前置**:`xmind-ui-automation`、`req-figma-ui-automation`、公司 **`playwright.git` 外挂仓库**(与本仓 MULTICA §2 路径不矛盾) - **1:1**:每条自动化 CASE → 恰好一个 `test_*.py` - **步骤对齐**:`steps[i]` → 第 i 个操作;`expected_results[i]` → 该步断言(等长) - **不编造**:locator 来自 **打开 page_url 后**的真实页面;找不到 → **BLOCKED** ## 输入(缺则中断) ```text repo_root: # Issue 仓库矩阵;Read MULTICA.md e2e_dir: # MULTICA.md §2 UI E2E 路径(默认 tests/e2e/) cases_source: # T1 Confluence 或 e2e_dir 内 test_*.py page_url / deploy_url: # Issue 评论 jira_key: auth_mode: # none | form_login | sso | cookie auth_user_env / auth_pass_env: ``` ### 账号密码(强制) - `page_url` **不等于**已登录;需登录系统必须给 `auth_mode` + env 变量名 - **禁止**把账号/密码写进:用例 JSON、脚本、XMind、JIRA 评论、Allure 正文 - 用例前置只写权限语义;真实凭据只放 Agent Secret / gitignore `.env` - 执行前检查 `auth_user_env`/`auth_pass_env` 非空;为空 → 中断,提示配置 Secret **勿回贴 Issue** - `auth_mode=none`:仅无需登录页面
Details
- Skill name
multica-test-t3-ui-automation- Repository
- it235/multica-best-practices
- Path
templates/zh_CN/skills/tester/multica-test-t3-ui-automation/SKILL.md- License
- MIT
- Repo updated
- 4 November 2026
FAQ
What does the Multica Test T3 UI Automation skill do?
T3 UI 自动化:pytest+Playwright,1 功能用例 = 1 个 e2e 测试;路径读 MULTICA.md §2;在 deploy URL 执行。
How do I install the Multica Test T3 UI Automation skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add it235/multica-best-practices --skill multica-test-t3-ui-automation. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Multica Test T3 UI Automation popular?
It lives in it235/multica-best-practices, which has 279 GitHub stars and 33 forks.
Related skills
Multica Artifact Architect
279it235/multica-best-practices
Land technical design artifacts to the code repo or knowledge platform (default Git repo / Confluence). Used by @Architect to upload technical design for downstream implementation and test consumption. Swappable platform.
Multica Artifact Architect
279it235/multica-best-practices
架构师产物薄编排:校验设计草稿规范,落地时只调 multica-platform-confluence + multica-platform-jira。用于 @Architect 发布设计文档。
Multica Artifact Backend
279it235/multica-best-practices
Land API contract artifacts to the API collaboration platform (default Apifox). Used by @BackendDev to upload API contract for downstream frontend / test consumption. Swappable platform.
Multica Verification
279it235/multica-best-practices
Gatekeeping function: objectively check whether an artifact satisfies the acceptance criteria. Triggered by the Leader to rerun at gate points (G1/G2/G3); members can also use it for self-check. Used for design review / implementation acceptance / test-report review.
Multica Test T3 UI Automation
279it235/multica-best-practices
T3 UI automation—only after G2.5 PASS; run pytest+Playwright 1:1 by MULTICA §2 e2e path and T1 cases; join overall verdict with API side. No local mock.
TDD Methodoly Expert
194thedaviddias/skill-check
Use when implementing features or fixing bugs with strict Test-Driven Development (TDD). Activate for coding tasks that require new functionality, refactoring, or comprehensive test coverage, especially when the user mentions TDD or Test Driven Development.
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.