appbuilder-e2e-testing

Generate Playwright E2E tests for App Builder SPAs and AEM extensions.

1|Updated Oct 7, 2024
One-click install
npx skills add https://github.com/valithedge/etisalatedge --skill appbuilder-e2e-testing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: appbuilder-e2e-testing
Source: https://github.com/valithedge/etisalatedge/tree/main/.agents/skills/appbuilder-e2e-testing
Command: npx skills add https://github.com/valithedge/etisalatedge --skill appbuilder-e2e-testing

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) and references (resource) components.

What problem does it solve?

Automating browser-based end-to-end testing for Adobe App Builder SPAs and AEM extensions, reducing manual QA time and catching integration issues early.

Core Features & Use Cases

  • Generate Playwright configs, test files, and CI workflows for browser-level validation of ExC Shell SPAs and AEM extensions.
  • Validate end-to-end flows across full-stack scenarios, including iframe-driven UIs and nested content.
  • Use in both local development and CI pipelines to ensure consistent UI behavior and regression coverage.

Quick Start

Install dependencies, configure Playwright, and run the E2E tests for App Builder apps.

Frequently Asked Questions about appbuilder-e2e-testing

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

FAQPage Schema
How do I automate Playwright E2E tests for Adobe App Builder SPAs?

Automate Playwright E2E tests for App Builder SPAs by generating test files and base configuration templates that validate browser interactions across local development and CI pipelines. This reduces manual QA time and catches integration issues early.

Can I test nested iframes in AEM extension UIs with Playwright?

Yes, you can test nested iframes in AEM extension UIs with Playwright. The generated E2E tests validate full-stack browser flows across ExC Shell SPAs and iframe-driven content to ensure consistent UI behavior and regression coverage.

Do I need Node.js 18+ to run E2E testing for App Builder?

Yes, Node.js 18+ and Playwright are required dependencies to run E2E testing for App Builder. You also need base configuration templates and optional CI workflow assets to generate test files, configuration, and pipelines.

What's the best way to validate ExC Shell SPA browser interactions in CI?

The best way to validate ExC Shell SPA browser interactions in CI is generating Playwright configs and CI workflows. This approach ensures consistent UI behavior and regression coverage across full-stack scenarios during local development and automated pipelines.

Does E2E testing for AEM extensions work in local development environments?

Yes, E2E testing for AEM extensions works in local development environments. You can use generated Playwright configurations and test files locally before integrating them into CI pipelines to verify browser interactions and full-stack flows.