skills.rest
amijadoamijado
amijadoamijadoCOMMUNITY
Explore all skills by this author →
GitHub

gas-e2e

Automate GAS Web App end-to-end testing across four Chrome modes.

Updated Feb 11, 2026
Search Tags:#automation#testing#playwright#e2e-testing#chrome-devtools#iframe#gas
One-click install
npx skills add https://github.com/amijadoamijado/sd003 --skill gas-e2e
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gas-e2e
Source: https://github.com/amijadoamijado/sd003/tree/main/.claude/skills/gas-e2e
Command: npx skills add https://github.com/amijadoamijado/sd003 --skill gas-e2e

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires playwright, and includes scripts (resource) components.

What problem does it solve?

This Skill automates end-to-end testing for GAS Web Apps across multiple modes, helping teams quickly validate UI flows, authentication, and deployments without manual steps.

Core Features & Use Cases

  • Four operation modes: claude-in-chrome, chrome-devtools-mcp, connect_over_cdp, and persistent_context, enabling flexible testing in local, CI, and headless environments.
  • Handles GAS iframe constraints and provides a guided flow for navigating, interacting with the iframe, capturing snapshots, and generating evidence.
  • Use Case: Validate a GAS Web App after deployment by launching the app, performing typical user actions, and collecting traces and screenshots for QA.

Quick Start

Run a test using Mode 2 to connect to an existing Chrome, navigate to the GAS URL, interact with the iframe, and capture a screenshot and snapshot evidence.

Frequently Asked Questions about gas-e2e

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

FAQPage Schema
How do I automate E2E testing for a GAS Web App with iframe interactions?▼

E2E testing for a GAS Web App requires handling specific iframe constraints by connecting to the app, navigating internal frames, and capturing snapshots. This Skill automates that flow to validate UI and authentication.

What is the best way to run Playwright tests on an existing Chrome session?▼

Running Playwright tests on an existing Chrome session uses the connect_over_cdp or persistent_context modes. These approaches securely connect to your active browser to execute testing scripts without launching a new instance.

Can I use this for CI-friendly deployment verification of GAS Web Apps?▼

Yes, you can use this for CI-friendly deployment verification of GAS Web Apps. It supports headless environments and multiple operation modes to validate deployments automatically while collecting traces and screenshots.

Does Playwright E2E testing support multiple browser connection modes?▼

Playwright E2E testing here supports four connection modes: claude-in-chrome, chrome-devtools-mcp, connect_over_cdp, and persistent_context. These provide flexible orchestration across local, CI, and headless environments.

Why does GAS iframe testing fail with standard Playwright scripts?▼

GAS iframe testing often fails due to specific iframe constraints within the Web App. This Skill provides a guided flow and robust error handling with clear fallbacks to properly navigate, interact, and capture evidence within these frames.

Related Skills

Explore More Software Engineering Skills→
TW-NLPTW-NLP
91

webapp-testing

Execute Playwright scripts to automate web application testing and debugging.

Community
Advanced
iamcxaiamcxa
3

e2e-walkthrough

Orchestrate human-guided browser walkthroughs with step screenshots and trace capture.

Community
Advanced
GoBeromsuGoBeromsu
2

browser-testing-with-devtools

Inspect DOM, console, network, and performance in real browsers via Chrome DevTools MCP.

Community
Intermediate
carerecarere
124

playwright-bowser

Automate headless browser tasks with Playwright CLI and persistent sessions.

Community
Intermediate