skills.rest
autopus-ai
autopus-aiOFFICIAL
Explore all skills by this author →
GitHub

auto-test

Executes E2E test scenarios defined in scenarios.md and reports pass, warn, or fail results.

111|73|Updated Mar 20, 2026
Search Tags:#test automation#validation#qa#verification#scenarios#e2e testing#test execution
One-click install
npx skills add https://github.com/autopus-ai/autopus-adk --skill auto-test-autopus-ai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: auto-test
Source: https://github.com/autopus-ai/autopus-adk/tree/main/.omp/skills/auto-test
Command: npx skills add https://github.com/autopus-ai/autopus-adk --skill auto-test-autopus-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Verifying that a feature works end-to-end after implementation is often skipped or done inconsistently. This Skill runs the E2E scenarios declared in scenarios.md and produces structured PASS, WARN, or FAIL results with evidence, so validation is repeatable and auditable. ## Core Features & Use Cases - Scenario-Driven Execution: Loads scenarios.md and runs each declared E2E scenario against the target directory. - Structured Verdicts: Reports PASS, WARN, or FAIL per scenario along with supporting evidence. - Context-Aware Testing: Uses a test context profile (core and test contexts required, canary excluded) to focus validation. - Use Case: After implementing a feature with the auto pipeline, invoke the test step to confirm every acceptance scenario in scenarios.md passes before shipping. ## Quick Start Run the auto-test skill against the current project to execute all E2E scenarios from scenarios.md and show me the pass, warn, and fail results with evidence.

Frequently Asked Questions about auto-test

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

FAQPage Schema
How do I run E2E test scenarios from a scenarios.md file?▼

Invoke the auto-test entrypoint with the target directory, and it loads scenarios.md, executes each declared E2E scenario, and reports results. Each scenario receives a PASS, WARN, or FAIL verdict with supporting evidence.

What is the auto-test skill used for in the Autopus pipeline?▼

It is the validation phase of the Autopus-ADK workflow, verifying implemented features against E2E scenarios defined in scenarios.md. It runs after implementation to confirm behavior before shipping.

What inputs does the E2E scenario runner require?▼

It requires a target directory and a scenarios.md file containing the declared E2E scenarios. It also uses a test context profile requiring core and test contexts while excluding canary contexts.

What do PASS, WARN, and FAIL results mean in scenario testing?▼

PASS means the scenario completed as specified, WARN indicates partial or questionable behavior worth reviewing, and FAIL means the scenario did not meet its declared expectations. Each verdict is accompanied by evidence for traceability.

What are the limitations of scenarios.md-based E2E validation?▼

Validation coverage is limited to the scenarios explicitly declared in scenarios.md, so undeclared edge cases are not tested. The quality of results depends on how completely the scenarios were written beforehand.

Related Skills

Explore More Software Engineering Skills→
arbiterForgearbiterForge
139

brainstorming

Refine rough feature ideas into approved, testable specifications with acceptance criteria.

Official
Advanced
clogacloga
3

daily-ops

Automate MCP-backed system patrols and maintenance decisions across eight inspection areas.

Community
Advanced
sheawinklersheawinkler
78

requesting-code-review

Automate pre-commit verification with static scans, tests, linting, and reviewer gates.

Community
Advanced
fgarofalo56fgarofalo56
6

testing

Run unit, integration, and E2E tests with pytest, Jest, Cypress, and Playwright.

Community
Advanced