$ loading_
Test deployed Power Pages sites with browsing, crawling, and API verification.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "test-site" skill from askskill: 1. Download https://raw.githubusercontent.com/microsoft/power-platform-skills/main/plugins/power-pages/skills/test-site/SKILL.md 2. Save it as ~/.claude/skills/test-site/SKILL.md 3. Reload skills and tell me it's ready
Run a smoke test on this deployed Power Pages site: https://example.powerpages.com. Use a browser to visit the home page, login page, and contact page, check whether pages load correctly, whether primary buttons are clickable, and verify that key API requests return 200 or expected results. Then output a test summary and failures.
A site smoke test report with page visit results, interaction checks, API verification results, and failure reasons.
Crawl this activated Power Pages site and check for common issues: https://example.powerpages.com. Traverse accessible pages, record broken links, 404 pages, pages with load failures, and obviously missing resource files, then list issues by page.
A page-by-page inspection report highlighting broken links, error pages, and resource loading issues.
Test the form submission flow on this Power Pages site: https://example.powerpages.com/register. Use a browser to fill out and submit the form, check whether frontend messages are correct, whether post-submit navigation works properly, and verify that related API requests have expected status codes, response content, and error handling.
A form integration test result showing whether submission works and detailing API responses and error handling.
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:…
Review and fix Power Pages security headers, CSP, CORS, cookies, and embedding settings.
Run an end-to-end Power Pages security review with a consolidated HTML report.
Add a data source or connector to a Power Apps code app.
Add Azure DevOps to Power Apps for work items, bugs, pipelines, and API calls.
Add the Excel Online connector to read and write workbook data.
Set up Power Platform Pipelines for automated Power Pages deployments.
Activate and provision a Power Pages site in a Power Platform environment.
Build and deploy an existing Power Pages code site to a target environment.
Create and launch a new Power Pages code site from concept to deployment.
Interact with and test local web apps using Playwright for debugging and verification.
Add essential SEO settings to Power Pages sites for better visibility and sharing.
Analyzes needs and recommends the best backend integration path for Power Pages.