e2e-test

Automate end-to-end browser tests across STS, BFF, and Client stacks.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/geobarteam/github-copilot-configs --skill e2e-test-geobarteam
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: e2e-test
Source: https://github.com/geobarteam/github-copilot-configs/tree/main/skills/e2e-test
Command: npx skills add https://github.com/geobarteam/github-copilot-configs --skill e2e-test-geobarteam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates end-to-end browser testing against the full {{SolutionName}} stack (STS + BFF + Client + Azurite) to verify UI flows, authentication, and overall health before release.

Core Features & Use Cases

  • Launch and orchestrate the exact test sequence for STS, BFF, and Client, including port mapping, health checks, and teardown.
  • Navigate pages, wait for content, perform actions, and capture screenshots and console logs to validate user interactions and error states.
  • Use for smoke-testing a feature, validating login flows, and ensuring the client UI renders correctly after implementation.

Quick Start

Run the e2e-test skill to execute the end-to-end browser test sequence against the running {{SolutionName}} stack.

Frequently Asked Questions about e2e-test

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

FAQPage Schema
How do I automate end-to-end browser tests for a full-stack web application?

Automate end-to-end browser tests using Playwright MCP to validate full-stack UI flows across STS, BFF, and Client components by orchestrating page navigation, capturing screenshots, and verifying health endpoints.

What does end-to-end testing validate in an ASP.NET Blazor application?

End-to-end testing validates UI rendering, authentication flows, and feature smoke tests against the full ASP.NET Blazor stack, ensuring the client UI renders correctly and login processes function without regression.

Do I need a running application stack to execute Playwright MCP browser tests?

Yes, executing Playwright MCP browser tests requires a running solution stack with active STS, BFF, and Client components, along with the ability to read port mappings and health endpoints during test orchestration.

How do I orchestrate test sequences for authentication and page rendering checks?

Orchestrate test sequences by launching the STS, BFF, and Client components, performing port mapping and health checks, navigating pages, waiting for content, and capturing console logs before final teardown.

Can I capture screenshots and console logs during automated UI regression testing?

Yes, you can capture screenshots and console logs during automated UI regression testing to validate user interactions and identify error states across the full application stack.

What are the limitations of using Playwright MCP for full-stack end-to-end testing?

Playwright MCP end-to-end testing is limited by its dependency on a fully running solution stack and accessible Azurite, requiring active port mappings and health endpoints to successfully orchestrate and tear down tests.