Verified:GitHub

factory-e2e

Execute end-to-end tests against acceptance criteria and classify failures.

Updated Mar 1, 2026

Search Tags:#quality assurance #test automation #acceptance criteria #regression testing #e2e testing #software verification

Ready to run

npx skills add https://github.com/JongHyunLee84/factory --skill factory-e2e

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: factory-e2e
Source: https://github.com/JongHyunLee84/factory/tree/main/skills/factory-e2e
Command: npx skills add https://github.com/JongHyunLee84/factory --skill factory-e2e

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the verification of software implementation against defined acceptance criteria through comprehensive end-to-end testing, ensuring the product meets user and business requirements.

Core Features & Use Cases

Automated Test Execution: Runs predefined automated, script-based, or manual E2E test scenarios.
Acceptance Criteria Validation: Directly maps test outcomes to specific acceptance criteria defined in architectural documents.
Failure Triage: Classifies test failures into Implementation Bugs, Design Gaps, or Test Errors for appropriate routing.
Regression Testing: Ensures that new changes do not negatively impact existing functionality.
Use Case: After a new feature is developed, this Skill will execute all E2E tests to confirm it functions as expected and doesn't break anything else in the system.

Quick Start

Execute end-to-end tests for the project using the factory-e2e skill.

Frequently Asked Questions about factory-e2e

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

FAQPage Schema

How do I automate end-to-end testing against acceptance criteria?▼

Automated end-to-end testing executes predefined script-based or manual test scenarios to verify software implementation against acceptance criteria defined in architectural documents. It outputs test results and decisions to the factory/e2e directory for tracking.

How does failure triage work in e2e test automation?▼

Failure triage in e2e test automation classifies test failures into Implementation Bugs, Design Gaps, or Test Errors. This triage routing ensures appropriate teams address defects, design shortfalls, or test script issues efficiently after regression runs.

Can I use regression testing to prevent new features from breaking existing functionality?▼

Regression testing verifies that new feature changes do not negatively impact existing system functionality. It runs comprehensive end-to-end tests after development to confirm software meets user and business requirements without introducing regressions.

Do I need architectural documents to run e2e tests?▼

Yes, e2e tests require factory/architect/architect.md for acceptance criteria. The test execution directly maps test outcomes to specific acceptance criteria defined within these architectural documents to validate implementation.

What is the best way to verify software implementation meets business requirements?▼

The best way to verify software implementation meets business requirements is through comprehensive end-to-end testing. This approach automates test execution and validates outcomes against defined acceptance criteria to ensure product compliance.

Why are my e2e tests returning design gap failures?▼

E2e tests return design gap failures when test execution reveals missing features or unhandled user flows in the architectural design. The failure triage classifies these specifically as Design Gaps for appropriate routing and resolution.