pr-testing

Install the PR-specific Aspire CLI build and run change-driven test scenarios.

6.2k|952|Updated Sep 25, 2023
One-click install
npx skills add https://github.com/microsoft/aspire --skill pr-testing-microsoft
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-testing
Source: https://github.com/microsoft/aspire/tree/main/.agents/skills/pr-testing
Command: npx skills add https://github.com/microsoft/aspire --skill pr-testing-microsoft

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of quickly validating that an Aspire pull request actually works end-to-end, by downloading the exact CLI build produced for the PR and executing targeted test scenarios derived from the PR changes.

Core Features & Use Cases

  • PR CLI dogfood install: Downloads the Aspire CLI from the PR’s “Dogfood this PR” artifact instructions and installs it in an isolated temp location or repo-local container workspace.
  • Version/commit verification: Confirms the installed CLI version matches the PR head commit (so tests run against the correct build).
  • Change-driven scenario selection: Categorizes PR changes (CLI, hosting, dashboard, templates, client/components, tests) and generates happy-path plus targeted unhappy-path checks accordingly.
  • Evidence capture + report generation: Records scenario status, screenshots, logs, and produces a comprehensive markdown report suitable for PR review.
  • Execution modes: Runs locally in a temp directory or in an isolated repo-local container runner for Linux/container-reproducible behavior.

Quick Start

Ask the agent to test your pull request by saying: Test PR 12345.

Frequently Asked Questions about pr-testing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify an Aspire pull request using the CLI build?▼

To verify an Aspire pull request, install the PR-specific Aspire CLI build in an isolated temp location or repo-local container runner, confirm the version matches the PR head commit, and execute change-driven test scenarios to validate the changes.

What types of Aspire PR changes require running pull request testing?▼

Pull request testing applies to Aspire PRs that modify CLI commands or options, hosting integrations, dashboard UI, templates, client or components, and tests, requiring appropriate happy-path and targeted unhappy-path coverage to ensure functionality.

Can I run Aspire integration tests in an isolated container runner?▼

Yes, you can run Aspire integration tests in an isolated repo-local container runner for Linux or container-reproducible behavior, or alternatively execute them locally in a temp directory to ensure deterministic install and testing isolation.

How does change-driven scenario selection work for Aspire regression verification?▼

Change-driven scenario selection categorizes Aspire PR changes into areas like CLI, hosting, dashboard, templates, or client components, and automatically generates corresponding happy-path and targeted unhappy-path test scenarios to execute appropriate regression verification.

What evidence is captured during Aspire PR testing for review?▼

During Aspire PR testing, the system records scenario status, screenshots, and logs, then produces a comprehensive markdown report suitable for PR review to provide evidence-backed validation of the Aspire CLI build.

Do I need the PR Dogfood instructions to test an Aspire pull request?▼

Yes, testing an Aspire pull request requires using the PR's Dogfood this PR instructions to achieve a deterministic install of the Aspire CLI build, ensuring the tests run against the exact build produced for that specific PR.