skills.rest
ABLER-Digital-Services
ABLER-Digital-ServicesOFFICIAL
Explore all skills by this author →
GitHub

it-app-e2e-reporter

Summarize Playwright E2E test results into structured HTML reports with pass/fail counts and evidence.

Updated May 18, 2026
Search Tags:#e2e#failure analysis#trace#evidence#playwright#test reporting#ci artifacts
One-click install
npx skills add https://github.com/ABLER-Digital-Services/ai-guild --skill it-app-e2e-reporter
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: it-app-e2e-reporter
Source: https://github.com/ABLER-Digital-Services/ai-guild/tree/main/skills/it-app-e2e-reporter
Command: npx skills add https://github.com/ABLER-Digital-Services/ai-guild --skill it-app-e2e-reporter

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

E2Eテストの実行結果を、成功/失敗の一覧と証跡（スクリーンショット・トレース）を含む形で整理して、関係者に報告できる状態にします。

Core Features & Use Cases

  • Playwright HTMLレポートの整理: テスト実行後にプレイブライトのHTMLレポートを生成し、ステップやエラー詳細を確認しやすくします。
  • サマリーレポート作成: 実行日時・対象・環境・結果件数・失敗詳細（原因分類）・証跡一覧を表形式でまとめます。
  • 原因分類と対応方針の提示: UI変更 / データ不整合 / タイムアウト / バグに分類し、次のアクションまで記録します。

Quick Start

テスト実行後のログと artifact（playwright-report/evidence/test-results）を提示して「E2Eテスト実行結果のサマリーレポートを原因分類と対応方針込みで作成して」と依頼してください。

Frequently Asked Questions about it-app-e2e-reporter

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

FAQPage Schema
How do I generate a structured E2E test report with failure analysis from Playwright?▼

To generate a structured E2E test report, provide Playwright execution logs and CI artifacts like screenshots and trace files. The Skill classifies failures into UI changes, data inconsistencies, timeouts, or bugs, and outputs a summary with evidence references.

Can I classify Playwright E2E test failures by root cause automatically?▼

Yes, E2E test failure root cause classification is applied by categorizing failures into UI changes, data inconsistencies, timeouts, or bugs. This organizes Playwright results into a structured report with corresponding evidence and next-step action policies.

What is the best way to summarize Playwright test results for stakeholder review?▼

The best way to summarize Playwright test results is to compile execution metadata, pass/fail/skip counts, and evidence into a structured report. This includes listing failure details with cause classifications and trace file references for clear communication.

Does E2E test reporting work with CI artifacts and local Playwright runs?▼

Yes, E2E test reporting works with both local and CI environments. You need to collect execution metadata and CI artifacts such as the playwright-report and test-results directories to generate the HTML reports and evidence summaries.

What evidence is included in an E2E test summary report?▼

An E2E test summary report includes screenshots and trace files as evidence. These artifacts are compiled alongside execution dates, target environments, result counts, and classified failure details to provide clear traceability for review.

Related Skills

Explore More Software Engineering Skills→
mvillmowmvillmow
18

analyze-ci-failure-logs

Analyze CI failure logs to identify root causes and error patterns.

Community
Intermediate
robwestzrobwestz

status-report-generator

Generate project status reports from Git history and issue trackers.

Community
Intermediate
zenbuappszenbuapps

browser-tester

Analyze git diffs and run Playwright CLI tests with video and screenshot reports.

Official
Advanced
jmaglyjmagly
175

flaky-detect

Analyze CI history and test execution patterns to identify flaky tests.

Community
Advanced