e2e-adhoc-diagnostics

Run and debug Playwright end-to-end tests for Electron applications.

Updated Feb 15, 2026
One-click install
npx skills add https://github.com/softwareByAndi/workflow --skill e2e-adhoc-diagnostics
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: e2e-adhoc-diagnostics
Source: https://github.com/softwareByAndi/workflow/tree/main/.claude/skills/e2e-adhoc-diagnostics
Command: npx skills add https://github.com/softwareByAndi/workflow --skill e2e-adhoc-diagnostics

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides a streamlined process for running, debugging, and writing end-to-end tests against the Electron application, ensuring robust software quality.

Core Features & Use Cases

  • Ad-hoc Test Execution: Run individual spec files with enhanced debugging features like video recording and traces.
  • Diagnostic Scripting: Create temporary scripts to investigate application behavior and pinpoint issues.
  • Use Case: When a specific E2E test fails intermittently, use this Skill to run that test in isolation with detailed logging and video to quickly identify the root cause.

Quick Start

Run the ad-hoc test file e2e/diagnostics/docker-startup-smoke.spec.ts.

Frequently Asked Questions about e2e-adhoc-diagnostics

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

FAQPage Schema
How do I debug a failing Playwright E2E test for an Electron app?

You can debug a failing Playwright E2E test for an Electron app by running individual spec files in isolation with enhanced diagnostics like video recording and traces to quickly identify the root cause.

Can I run an ad-hoc Playwright test without executing the entire E2E test suite?

Yes, you can execute an ad-hoc Playwright test independently by running individual spec files, such as the diagnostics smoke test, to troubleshoot intermittent failures and pinpoint application issues efficiently.

How do I write a diagnostic script to investigate Electron application behavior?

You can write a diagnostic script to investigate Electron application behavior by creating temporary scripts within your E2E testing environment, allowing you to interact with application components and log detailed behavior for troubleshooting.

What's the best way to capture video and traces when troubleshooting E2E tests?

The best way to capture video and traces when troubleshooting E2E tests is to use ad-hoc test execution features that support enhanced debugging outputs, allowing you to record test runs and inspect detailed application interactions.

Why does my E2E test fail intermittently and how can I isolate the issue?

Your E2E test may fail intermittently due to race conditions or timing issues; you can isolate the issue by running the specific failing test in isolation with detailed logging and video recording to analyze the exact failure point.