Multica Test T3 UI Automation
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.
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/en_US/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
# UI Automation (T3 · UI)
T3 only after **G2.5 PASS**; an AC can only be verified by UI → run this skill alone; if it also has an API channel → run both, orchestration merges one report.
> Integrated from `ui-automation-squad`. **Material assembly + BLOCKED see `multica-test-orchestration`.**
## Required Items (stop + interruption list if missing; summary from comments)
| Required | How it counts as complete |
| --- | --- |
| G2.5 PASS | Leader/DevOps explicit G2.5 PASS (or deploy_url + Leader written authorization) |
| deploy_url | Reachable environment URL |
| page_url | Page URL; if omitted must equal deploy_url (state in comments) |
| e2e script | **Path in MULTICA.md §2**; in deploy branch at G2.5 SHA, **1:1** with cases |
| ui_auth | `auth_mode=none` or "account via Secret variable name"; **never plaintext password from comments** |
**Never** use `xmind-ui-automation` / `playwright.git` / `req-figma-ui-automation` as prerequisites.
## Flow
```bash
pytest <MULTICA.md §2 e2e path> --base-url <page_url> --alluredir ./reports/ui
```
Cases source: T1 Confluence t1-cases + T2 supplement. Missing script path → interruption list.
## Output and merge
```markdown
# T3 UI Automation — {JIRA_KEY}
- G2.5: PASS @ {sha} deploy: {url} page: {page_url}
- e2e: {MULTICA.md §2 path}
- total / pass / fail / error
- per case: id / title / status / screenshot / log path
- conclusion: PASS | FAIL | BLOCKED
```Details
- Skill name
multica-test-t3-ui-automation- Repository
- it235/multica-best-practices
- Path
templates/en_US/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 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.
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 Test T3 UI Automation
279it235/multica-best-practices
T3 UI 自动化:pytest+Playwright,1 功能用例 = 1 个 e2e 测试;路径读 MULTICA.md §2;在 deploy URL 执行。
Multica Test T2 Coverage
279it235/multica-best-practices
T2 覆盖率评估:G2 PASS 后对照 diff、契约与 T1 Confluence;增量正文 + Apifox 补场景 + tests/e2e Playwright 入库。不生成 XMind。
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.
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.