runtime-validation Skill
Runtime validation for migrated applications — covers testing strategy (planning phase) and test execution (validation phase): startup verification, integration testing, and end-to-end flow validation. Use when: (1) designing test strategy during planning phase (teamlead reads Part 1) (2) verifying a migrated app start Published by microsoft in github-copilot-modernization.
What is runtime-validation Skill?
Runtime validation for migrated applications — covers testing strategy (planning phase) and test execution (validation phase): startup verification, integration testing, and end-to-end flow validation. Use when: (1) designing test strategy during planning phase (teamlead reads Part 1) (2) verifying a migrated app start Published by microsoft in github-copilot-modernization. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Testing
- Security review
- Design and media
- Writing
- Testing use cases
Technical details
- Install or run with Copy skill directory
When to use runtime-validation Skill
- Use it for testing.
- Use it for security review.
- Use it for design and media.
- Use it for writing.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/github-copilot-modernization
- Skill file: plugins/github-copilot-modernization/skills/runtime-validation/SKILL.md
What it does
Runtime validation for migrated applications — covers testing strategy (planning phase) and test execution (validation phase): startup verification, integration testing, and end-to-end flow validation. Use when: (1) designing test strategy during planning phase (teamlead reads Part 1) (2) verifying a migrated app start
Skill instructions
Runtime Validation This skill serves two phases of the pipeline: - Design phase (Part 1) — planning roles read this to produce a testing strategy before implementation begins - Validation phase (Part 2) — tester reads this to execute startup verification + write and run tests --- Part 1: Testing Strategy Audience: planning roles producing the pre-implementation plan. Tester reads the resulting testing strategy during validation and executes it. Output: a "Testing Strategy" section in the planning artifact, produced before writing test code. 1.1 Test Tiers Not every project needs every tier. Pick the tiers that match the app's architecture: | Tier | Config | DB | Security | Speed | When to use | |------|--------|----|----------|-------|-------------| | Unit | Mocked deps | None | None | 1ms | Always — implementer writes & runs. Test infrastructure is designed here (see §1.4 item 10) | | Slice | Partial app context | In-memory | Mocked | 100ms | Framework-supported isolation (e.g., @WebM
Explore related resources
Frequently asked questions
What is runtime-validation?
runtime-validation is a open-source AI agent skill with Copy skill directory. Runtime validation for migrated applications — covers testing strategy (planning phase) and test execution (validation phase): startup verification, integration testing, and end-to-end flow.
Who is runtime-validation best for?
runtime-validation is best for reusing agent instructions, scripts, and references, testing workflows, security review workflows, design and media workflows.
How do I install runtime-validation?
Install or run runtime-validation using Copy skill directory. Check runtime-validation for the latest setup command.
Is runtime-validation actively maintained?
runtime-validation may need a closer maintenance check before production use.
Auto-fetched from GitHub.
