wsbaser:generate-test-report

Convert multi-scenario browser test results into an HTML report with embedded screenshots.

1|Updated Feb 21, 2026

Search Tags:#automation #screenshots #e2e-testing #html-report #report-generation #test-results #multi-scenario

Ready to run

npx skills add https://github.com/wsbaser/claude-plugins --skill wsbaser-generate-test-report

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: wsbaser:generate-test-report
Source: https://github.com/wsbaser/claude-plugins/tree/main/plugins/wsbaser/skills/generate-test-report
Command: npx skills add https://github.com/wsbaser/claude-plugins --skill wsbaser-generate-test-report

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Produces a complete, human-readable HTML test report from multi-scenario browser tests, consolidating results, steps, issues, and screenshots into a single artifact.

Core Features & Use Cases

Allure-style HTML report with a sidebar for navigating scenarios and a detailed per-scenario view.
Embeds screenshots as data URIs and includes per-step statuses, issues, and guidance for fixes.
Supports post-test workflows by generating artifacts after browser testing and by triggering via /wsbaser:generate-test-report.

Quick Start

Invoke after tests by calling /wsbaser:generate-test-report to produce the HTML report.

Frequently Asked Questions about wsbaser:generate-test-report

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

FAQPage Schema

How do I generate a multi-scenario HTML test report from browser automation results?▼

To generate an HTML test report, invoke the report generation command after your browser automation test suite executes. It converts multi-scenario test results into a polished HTML artifact with a collapsible sidebar, per-scenario details, and embedded screenshots.

What is the best way to include screenshots in an e2e-testing HTML report?▼

Including screenshots in an e2e-testing HTML report is handled by encoding all available image assets as data URIs. This embeds screenshots directly into the single HTML test report artifact, ensuring it is self-contained and portable without external file dependencies.

Does the report generation process apply status-based styling for UI regression runs?▼

Yes, the report generation process applies status-based styling for UI regression runs. It renders test metadata into a consistent frontend structure, styling per-step statuses and issues with distinct visual cues to highlight failures and provide fix guidance.

Can I use this HTML report generation with my existing browser automation test suite?▼

You can use this HTML report generation with any browser automation test suite that produces multi-scenario test results. It requires no external dependencies and consolidates results, steps, issues, and screenshots into a single comprehensive artifact for web apps.

Why does my multi-scenario test report need embedded screenshots as data URIs?▼

Your multi-scenario test report needs embedded screenshots as data URIs to ensure the HTML artifact remains self-contained. Encoding images as data URIs prevents broken image links when sharing the report across different environments or post-test workflows.