e2e-chrome-devtools

Automate visual smoke testing of live web apps via Chrome DevTools MCP.

1|2|Updated Apr 6, 2026

Search Tags:#automation #e2e #lighthouse #chrome-devtools #visual-testing #web-app #smoke-test

Ready to run

npx skills add https://github.com/parisgroup-ai/imersao-ia-setup --skill e2e-chrome-devtools

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: e2e-chrome-devtools
Source: https://github.com/parisgroup-ai/imersao-ia-setup/tree/main/skills/e2e-chrome-devtools
Command: npx skills add https://github.com/parisgroup-ai/imersao-ia-setup --skill e2e-chrome-devtools

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Visual smoke testing the live web app by exercising critical paths in a real Chrome browser via Chrome DevTools MCP, surfacing rendering issues, console errors, network failures, and performance anomalies before release.

Core Features & Use Cases

Visual smoke testing against a running web app using the real Chrome browser via the Chrome DevTools MCP.
Capture screenshots, inspect console and network activity, run Lighthouse audits, and test mobile/dark-mode emulation.
Use cases include quick health checks of dashboards, landing pages, and API-driven pages in local or production environments.

Quick Start

Install and configure the Chrome DevTools MCP, connect to a running app, and run the skill to perform visual smoke testing.

Frequently Asked Questions about e2e-chrome-devtools

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

FAQPage Schema

How do I run visual smoke tests on a live web app using real Chrome?▼

Visual smoke testing of a live web app is automated using Chrome DevTools MCP to exercise critical paths in a real Chrome browser, surfacing rendering, console, network, and performance anomalies before release.

Can I capture Lighthouse scores and network behavior during automated web app testing?▼

Yes, automated web app testing via Chrome DevTools MCP captures Lighthouse scores, network activity, and console errors, verifying API-driven interfaces, authenticated dashboards, and public landing pages across local or production environments.

Does visual smoke testing require a running Chrome instance with DevTools Protocol enabled?▼

Yes, visual smoke testing requires a running Chrome browser with DevTools Protocol enabled and proper MCP server configuration to inspect rendering, run audits, and test mobile or dark-mode emulation.

What is the best way to verify rendering and performance across different devices and themes?▼

The best way to verify rendering and performance across different devices and themes is using Chrome DevTools MCP to automate visual smoke tests, capturing screenshots and running Lighthouse audits on critical web app paths.

When should I use Chrome DevTools MCP for e2e testing instead of other automation approaches?▼

Use Chrome DevTools MCP for e2e testing when you need to surface real browser rendering issues, console errors, and network failures in local or production environments, complementing standard automation with deep performance and visual verification.

Why are my visual smoke tests missing network failures on API-driven dashboards?▼

Visual smoke tests might miss network failures on API-driven dashboards if the Chrome instance lacks DevTools Protocol enabled or MCP server configuration is incorrect, preventing proper network activity inspection during testing.