auto-test

Execute end-to-end test scenarios from scenarios.md via Autopus workflow routing.

Updated Apr 24, 2026
One-click install
npx skills add https://github.com/shin0720/autopus --skill auto-test-shin0720
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: auto-test
Source: https://github.com/shin0720/autopus/tree/main/.autopus/plugins/auto/skills/auto-test
Command: npx skills add https://github.com/shin0720/autopus --skill auto-test-shin0720

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the manual effort of running end-to-end test scenarios for software projects, ensuring consistent validation of full-stack functionality without repetitive manual work.

Core Features & Use Cases

  • E2E Scenario Execution: Runs predefined end-to-end test scenarios defined in a project's scenarios.md file to validate full application workflows.
  • Flag Preservation: Maintains all user-specified test flags (like --auto, --loop, --team) exactly as provided when routing to the canonical Autopus test workflow.
  • Use Case: When developing a new authentication feature, use this Skill to automatically run all related E2E test scenarios to confirm login, registration, and permission flows work as expected across the entire stack.

Quick Start

Use the auto-test skill to run all end-to-end test scenarios defined in your project's scenarios.md file.

Frequently Asked Questions about auto-test

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

FAQPage Schema
How do I run end-to-end test scenarios automatically?

To run end-to-end test scenarios automatically, define your test cases in a project scenarios.md file and invoke the auto-test skill to execute full-stack workflow validation without manual effort.

What is E2E scenario validation for full-stack functionality?

E2E scenario validation for full-stack functionality executes predefined test cases against the entire application stack to confirm workflows like authentication and permissions behave as expected across all layers.

How do I validate user-specified test flags during workflow routing?

To validate user-specified test flags during workflow routing, the system preserves all flags like --auto, --loop, and --team exactly as provided when routing to the canonical Autopus test workflow.

Can I use Autopus workflow routing with predefined test case definitions?

Yes, Autopus workflow routing integrates directly with predefined test case definitions by loading detailed test execution logic and preserving user-specified test flags during the automated E2E test run.

Do I need a scenarios.md file to automate E2E test execution?

Yes, a scenarios.md file is required to define the end-to-end test scenarios. The automated test execution reads this file to validate full application workflows against your predefined test cases.

Best way to automate repetitive manual E2E testing for new features?

The best way to automate repetitive manual E2E testing is defining scenarios in a scenarios.md file and routing them through the Autopus workflow, ensuring consistent validation without manual execution.