$ loading_
用于对已部署的 Power Pages 网站进行运行时浏览、爬取与接口验证测试。
复制安装指令，让 AI 自动完成配置 · 推荐新手
请帮我安装 askskill 上的 "test-site" 技能： 1. 下载 https://raw.githubusercontent.com/microsoft/power-platform-skills/main/plugins/power-pages/skills/test-site/SKILL.md 2. 保存为 ~/.claude/skills/test-site/SKILL.md 3. 装好后重载技能，告诉我可以用了
请对这个已部署的 Power Pages 网站做一次冒烟测试：https://example.powerpages.com。使用浏览器访问首页、登录页、联系我们页，检查页面是否能正常加载、主要按钮是否可点击，并验证关键 API 请求是否返回 200 或预期结果。最后输出测试摘要和失败项。
一份网站冒烟测试报告，包含页面访问结果、交互检查结果、API 验证结果及失败原因。
请爬取这个已激活的 Power Pages 网站并检查常见问题：https://example.powerpages.com。遍历可访问页面，记录死链、404 页面、加载异常页面，以及明显缺失的资源文件，并按页面列出问题清单。
一份按页面整理的巡检结果，标出死链、错误页面和资源加载问题。
请测试这个 Power Pages 网站中的提交表单流程：https://example.powerpages.com/register。使用浏览器填写并提交表单，检查前端提示是否正确、提交后页面跳转是否正常，并验证相关 API 请求的状态码、响应内容和错误处理是否符合预期。
一份表单联调测试结果，说明提交流程是否正常，并列出接口响应与异常处理情况。
Plugin check: Run
node "${CLAUDE_PLUGIN_ROOT}/scripts/check-version.js"— if it outputs a message, show it to the user before proceeding.
Test a deployed, activated Power Pages site at runtime. Navigate the site in a browser, crawl all discoverable links, verify pages load correctly, capture network traffic to test API requests, and generate a comprehensive test report.
Prerequisite: This skill expects a deployed and activated Power Pages site. Run
/deploy-siteand/activate-sitefirst if the site is not yet live.
/_api/ (Web API / OData) requests return successful responses./_api/serverlogics/ endpoints the test run must also capture and report the actual response body shape so frontend integrations can be written against the real response, not a guessed one. If frontend parsing or field access does not match the observed shape, report the mismatch and describe the parsing or field-access changes needed — this skill does not modify any code.Every run produces a categorized test report (docs/alm/last-test-site.json — see Phase 6.7a). Stable category IDs and the source phase that produces each:
Category id | Display Name | Source phase | What it covers |
|---|---|---|---|
site-load | Site Load | Phase 2 | Homepage HTTP status, redirect handling, initial render. One card for the homepage; failures are critical. |
authentication | Authentication | Phase 3 | Anonymous-to-Entra redirect, private-site gate detection, login flow integrity. Critical for private sites. |
page-crawl | Page Crawl | Phase 4 | One card per page tested (up to 25). Each card carries the page URL, HTTP status, and any console errors. Severity scales with HTTP class (5xx → critical, 4xx on public → high). |
web-api | Web API | Phase 5 | One card per /_api/ endpoint observed during the run. Captures status code, response shape, and remediation hints (table-permissions / site-settings / inner-error settings). |
auth-pages | Authenticated Pages | Phase 5.6 | Pages that only became reachable after login. Skipped when the user opts out of authenticated testing. |
auth-api | Authenticated API | Phase 5.6 | API endpoints that only became callable after login. Skipped when authenticated testing is skipped. |
console | Console Health | Aggregated | Rolled-up count of console errors observed across all phases. Severity is medium by default. |
plan-alm's Validation tab consumes this shape directly — each category becomes a collapsible group in the per-stage sub-tab, and the rolled-up runOutcome (passed / passed-with-warnings / failed) drives the green / yellow / red Outcome badge in both the Validation tab and the Execution checklist substep.
Initial request: $ARGUMENTS
Goal: Determine the live URL of the Power Pages site to test.
Create the full task list with all 6 phases before starting any work (see Progress Tracking table).
If the user provided a URL in $ARGUMENTS:
https://.SITE_URL and skip to Phase 2.If no URL was provided, attempt auto-detection:
powerpages.config.json:…
为 Power Apps 代码应用接入 Azure DevOps 连接器，便于查询工单、提报缺陷与管理流水线。
对 Power Pages 站点执行端到端安全审查，并汇总生成完整 HTML 报告。