e2e

Execute end-to-end tests across UI, API, and database layers.

2.3k|237|Updated Feb 28, 2026
One-click install
npx skills add https://github.com/AgentsMesh/AgentsMesh --skill e2e-agentsmesh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: e2e
Source: https://github.com/AgentsMesh/AgentsMesh/tree/main/.claude/skills/e2e
Command: npx skills add https://github.com/AgentsMesh/AgentsMesh --skill e2e-agentsmesh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the execution of end-to-end (E2E) tests, ensuring comprehensive validation of application functionality across UI, API, and database layers.

Core Features & Use Cases

  • Comprehensive Testing: Executes UI, API, and database verification steps as defined in test cases.
  • Environment Awareness: Dynamically configures and uses the correct development environment ports and Docker containers based on the current worktree.
  • Tool Orchestration: Leverages specific tools like MCP Chrome DevTools for UI tests, curl for API tests, and docker exec psql for database tests.
  • Use Case: Run a full suite of E2E tests for a new feature, ensuring that the user interface behaves as expected, the backend APIs respond correctly, and the database state is accurate after user interactions.

Quick Start

Execute the end-to-end tests for the current feature by running the e2e skill.

Frequently Asked Questions about e2e

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

FAQPage Schema
How do I run end-to-end tests across UI, API, and database layers?

End-to-end testing across UI, API, and database layers is executed by orchestrating verification steps that use MCP Chrome DevTools for UI, curl for API interactions, and docker exec psql for database state validation.

What is the best way to automate E2E tests in Docker development environments?

Automating E2E tests in Docker development environments involves dynamically determining and utilizing the correct ports and Docker containers specific to the active worktree to ensure robust application testing.

Does this E2E testing approach use Chrome DevTools for UI validation?

Yes, E2E testing uses MCP Chrome DevTools specifically for UI validation, while employing curl for API interactions and docker exec psql for database queries to ensure comprehensive test coverage.

Can I verify database state with psql during end-to-end test execution?

You can verify database state during end-to-end test execution by running docker exec psql commands, which query the database container specific to your active worktree to validate data accuracy after user interactions.

Why do my end-to-end tests fail to connect to the correct development environment ports?

End-to-end tests fail to connect when they lack environment awareness; this testing process dynamically configures and uses the correct development environment ports based on the current worktree to prevent connection errors.