Endor
Official@endorhq
Run your favorite server software inside your browser
Agent Skills by Endor
Showing 11 vetted skills indexed across 1 GitHub repositories.
fp-update
Updates existing E2E tests to align with E2E_TESTS.md specifications.
fp-add-spec
Generate E2E_TESTS.md specifications by analyzing package source code and public APIs.
fp-fix
Diagnose and fix failing E2E tests according to E2E_TESTS.md specifications.
fp-add
Add features or suites to E2E test specifications and generate test code.
fp-generate
Generate End-to-End test files from E2E_TESTS.md specifications.
fp-review-spec
Validate E2E_TESTS.md structure, metadata, and quality without modifying files.
fp-update-spec
Update E2E_TESTS.md specifications from git history and source code changes.
flightplanner
Generate and update E2E tests from E2E_TESTS.md specifications.
fp-audit
Analyze gaps between E2E test specifications and implemented test cases.
fp-init
Generate E2E_TESTS.md specification files from project source code and release history.
fp-smoke-test
Execute comprehensive smoke tests on CLI, library, web API, and web UI applications.
Frequently Asked Questions About Endor
FAQPage SchemaWhat specific testing tasks does Endor enable?▼
Endor enables the generation, validation, and maintenance of E2E test suites based on E2E_TESTS.md specifications. It supports initializing new test documentation from source code, updating existing tests to match specification changes, diagnosing failures, and auditing coverage gaps between defined requirements and actual test implementations.
Which personas benefit most from using Endor?▼
Endor is designed for Quality Assurance engineers, Software Development Engineers in Test (SDETs), and full-stack developers. It is particularly useful for teams managing large-scale web applications or complex library architectures who require strict alignment between technical documentation and functional test coverage.
What are the primary prerequisites for using Endor?▼
Endor requires a project with existing source code or release history to initialize specifications. Users must maintain an E2E_TESTS.md file, which serves as the source of truth for test generation and validation. The system relies on git history and source code analysis to maintain synchronization between specifications and test files.