skills.rest
sbluemin
sblueminCOMMUNITY
Explore all skills by this author →
GitHub

console-e2e

Run real-browser end-to-end tests for the Fleet Console web UI.

16|2|Updated Mar 17, 2026
Search Tags:#UI testing#diagnostics#web automation#browser testing#end-to-end testing
One-click install
npx skills add https://github.com/sbluemin/fleet-harness --skill console-e2e
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: console-e2e
Source: https://github.com/sbluemin/fleet-harness/tree/main/.agents/skills/console-e2e
Command: npx skills add https://github.com/sbluemin/fleet-harness --skill console-e2e

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires agent-browser, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the challenge of testing and diagnosing the Fleet Console's user interface in a thorough and automated manner, providing a reliable way to catch issues before they reach production.

Core Features & Use Cases

  • Real-Browser End-to-End Testing: Ensures that the Fleet Console's web UI functions correctly across different browsers and scenarios.
  • Diagnostic Power: Helps identify problems such as blank screens, terminal rendering issues, Theater or Operation interactions, and more.
  • Use Case: If a user notices a strange behavior in the Fleet Console's web UI, they can use this Skill to pinpoint the issue and diagnose the root cause.

Quick Start

Use the 'console-e2e' skill to initiate an end-to-end test for the Fleet Console's web UI.

Frequently Asked Questions about console-e2e

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

FAQPage Schema
How do I run end-to-end tests on a web UI to diagnose blank screens and rendering issues?▼

End-to-end testing diagnoses web UI rendering issues by running real-browser scenarios against the Fleet Console to identify blank screens, terminal rendering problems, and interaction failures. It pinpoints root causes for strange interface behaviors before production deployment.

What is the best way to automate browser testing for the Fleet Console UI?▼

Automating browser testing for the Fleet Console requires real-browser scenarios that validate UI interactions and system response times. This approach ensures functionality across different browsers and provides thorough diagnostic power for pinpointing interface problems.

Do I need agent-browser to set up end-to-end testing for web UI interactions?▼

Yes, agent-browser is a required dependency for end-to-end testing the Fleet Console. You also need specific configuration and setup for isolation and unique session management to ensure reliable and precise test execution.

Can I use real-browser web automation to diagnose Theater or Operation interaction problems?▼

Real-browser web automation diagnoses Theater or Operation interaction problems by executing end-to-end test scenarios on the Fleet Console UI. This isolates system response times and validates UI interactions to pinpoint the root cause of strange behaviors.

Why does end-to-end testing require specific configuration and session isolation for the Fleet Console?▼

End-to-end testing requires configuration and session isolation to guarantee unique session management during real-browser scenarios. This prevents test interference, ensuring precise and reliable diagnosis of UI functionality and system response times.

Related Skills

Explore More Software Engineering Skills→
wormholecowboywormholecowboy
1

agent-browser

Automate browser tasks via CLI with headless Chromium.

Community
Intermediate
Im5tuIm5tu
6

systematic-debugging

Identify root causes of software bugs through a four-phase debugging process.

Community
Advanced
redpanda-dataredpanda-data
34

visual-review

Automate visual and accessibility reviews of frontend UI changes with Playwright.

Official
Advanced
BuilderIOBuilderIO
11

playwright-cli

Automate browser interactions and Playwright test workflows via command-driven tooling.

Official
Advanced