e2e-template-testing

Run local squad sessions to validate template changes and capture evidence.

619|188|Updated Jul 4, 2024
One-click install
npx skills add https://github.com/CommunityToolkit/Aspire --skill e2e-template-testing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: e2e-template-testing
Source: https://github.com/CommunityToolkit/Aspire/tree/main/examples/squad/CommunityToolkit.Aspire.Hosting.Squad.AppHost/dev-squad/.squad/templates/skills/e2e-template-testing
Command: npx skills add https://github.com/CommunityToolkit/Aspire --skill e2e-template-testing

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill automates end-to-end validation of template changes for squad sessions, ensuring prompt-level regressions are caught early in the development process.

Core Features & Use Cases

  • End-to-End Validation: Runs real squad sessions against a locally-built CLI to test modified templates.
  • Automated Session Creation: Initializes and manages test squad sessions.
  • Outcome Verification: Provides evidence files and verdicts on template changes.

Quick Start

To test your changes to the .squad-templates directory, use the 'e2e-template-testing' skill by providing a tracking PR number and repository URL.

Frequently Asked Questions about e2e-template-testing

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

FAQPage Schema
How do I automate end-to-end validation for squad session template changes?

Automate end-to-end validation for squad sessions by running real test sessions against a locally-built CLI, capturing output, and generating evidence files to review template modifications.

What do I need to run automated E2E tests on local CLI squad templates?

Running automated E2E tests for squad templates requires Node.js, npm, Git, the GitHub Copilot CLI, and a local clone of your squad repository to execute the test sessions.

How do I verify prompt-level regressions when modifying squad templates?

Verify prompt-level regressions by initializing automated test squad sessions against your local CLI, which captures session output and provides verdicts on the template changes.

Can I use a tracking PR number to test squad template changes automatically?

Yes, you can test squad template changes by providing a tracking PR number and repository URL to the E2E testing skill to initiate and manage the automated validation sessions.

What kind of evidence files are generated when testing squad session templates?

Testing squad session templates generates evidence files and verdicts that document the CLI session output, allowing you to review the impact of template modifications during development.

Why do I need a local squad repository clone for end-to-end template testing?

A local squad repository clone is required for end-to-end template testing so the testing scripts can execute real squad sessions directly against your locally-built CLI environment.