testing

Automates end-to-end UI testing with a Playwright-based subagent and logs diagnostics.

Updated Apr 3, 2026
One-click install
npx skills add https://github.com/gopforever/Idle-Echoes --skill testing-gopforever
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: testing
Source: https://github.com/gopforever/Idle-Echoes/tree/main/.local/skills/testing
Command: npx skills add https://github.com/gopforever/Idle-Echoes --skill testing-gopforever

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Run automated UI tests against your application using a Playwright-based testing subagent. Use after implementing features to verify they work correctly. (support overriding clerk auth)

Core Features & Use Cases

  • End-to-end testing in a real browser with a Playwright-based subagent.
  • Collects browser and backend logs, provides detailed feedback including diagnostics and screenshots.
  • Supports programmatic auth configuration overrides (Clerk or Replit) for test flows.

Quick Start

Write a test plan describing a user flow and runTest with that plan and any relevant technical documentation.

Frequently Asked Questions about testing

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

FAQPage Schema
How do I automate end-to-end UI testing for my web application?▼

Automate end-to-end UI testing by writing a test plan that describes a user flow and passing it to a Playwright-based subagent. The subagent runs the tests in a real browser, validates interactions, and returns diagnostics with screenshots for feature verification.

Can I automate Playwright tests that require Clerk authentication?▼

Yes, you can automate Playwright tests requiring Clerk authentication. The testing flow supports programmatic auth configuration overrides for Clerk, allowing the subagent to handle login steps automatically when your test plan requires authentication.

How do I get browser and backend logs when running e2e tests?▼

To get browser and backend logs during e2e tests, run your test plan through the Playwright subagent. It automatically collects both browser and backend logs during execution and provides detailed feedback alongside screenshots for diagnostics.

What is the best way to verify frontend and backend interactions after implementing a feature?▼

The best way to verify frontend and backend interactions is running automated e2e tests with a Playwright subagent. It validates the interactions across your application stack, collects logs, and provides screenshots to confirm the new feature works correctly.

Do I need to install Playwright separately to run these e2e tests?▼

No, you do not need to install Playwright separately. The testing is executed using a Playwright-based subagent that handles the browser automation, allowing you to focus on writing the test plan and relevant technical documentation.

Why are my e2e UI tests failing during the login step?▼

Your e2e UI tests may be failing during login if the auth configuration is missing. Ensure your test plan includes relevant technical documentation so the subagent can properly apply Clerk or Replit programmatic auth overrides for the test flow.