testing

Name: testing
Availability: InStock
Author: not-subhu

Run Playwright-based end-to-end UI tests in real browsers.

Updated Jun 30, 2026

Search Tags:#playwright #ui testing #automated testing #end-to-end testing #real browser testing

Ready to run

npx skills add https://github.com/not-subhu/screech --skill testing-not-subhu

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: testing
Source: https://github.com/not-subhu/screech/tree/main/.local/skills/testing
Command: npx skills add https://github.com/not-subhu/screech --skill testing-not-subhu

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill simplifies the process of running automated UI tests against your application, ensuring that newly implemented features work as expected.

Core Features & Use Cases

Automated UI Testing: Execute tests against your application using a Playwright-based testing subagent.
Real Browser Execution: Testers simulate real browser behavior for accurate results.
Test History and State: Persistent testers maintain history and state for continuous follow-ups.
Use Case: When a new feature is added to an application, use this Skill to create a tester to automatically verify its functionality.

Quick Start

Run automated UI tests on your application with 'subagent({ name: "ui-tester", config: { $kind: "testing" } })'.

Frequently Asked Questions about testing

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

FAQPage Schema

How do I run automated end-to-end tests for my application's UI?▼

Automated end-to-end tests for your UI can be executed using a Playwright-based subagent that validates functionality in real browsers. Instantiate a tester via the subagent command to verify newly implemented features automatically.

Do I need Playwright installed to use this UI testing subagent?▼

Yes, Playwright is required for this UI testing subagent because it executes tests in real browsers to simulate real browser behavior. The dependency is necessary to validate accurate UI functionality results.

Can I maintain test history and state for continuous end-to-end testing?▼

Yes, persistent testers maintain test history and state for continuous end-to-end testing. This allows you to perform follow-up tests on your application's UI without losing the context of previous automated test executions.

What is the best way to verify newly implemented application features automatically?▼

The best way to verify newly implemented application features automatically is to create a Playwright-based tester subagent. It executes automated UI tests in real browsers to ensure new functionality works as expected.

How does real browser execution improve automated UI testing?▼

Real browser execution improves automated UI testing by simulating actual browser behavior through Playwright, which ensures accurate validation results for your application's UI functionality rather than relying on simulated environments.