skills.rest
zeveck
zeveckCOMMUNITY
Explore all skills by this author →
GitHub

manual-testing

Automate manual UI testing of the block-diagram editor with Playwright CLI.

Updated Mar 25, 2026
Search Tags:#qa#ui-testing#quality-assurance#manual-testing#playwright-cli#block-editor
One-click install
npx skills add https://github.com/zeveck/zskills --skill manual-testing-zeveck
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: manual-testing
Source: https://github.com/zeveck/zskills/tree/main/skills/manual-testing
Command: npx skills add https://github.com/zeveck/zskills --skill manual-testing-zeveck

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual UI testing of the block-diagram editor requires real-user interactions to verify correctness and catch regressions, rather than relying on automated unit tests alone.

Core Features & Use Cases

  • Guided end-to-end manual testing of the editor's block operations (add block, connect ports, run simulations, edit parameters) using Playwright CLI.
  • Deterministic test routines that reproduce user interactions across sessions for reliable verification.
  • Real-world workflow validation across editor scenarios, from library usage to parameter changes.

Quick Start

Open the dev server and run the Playwright CLI tests against the editor to verify UI interactions end-to-end.

Frequently Asked Questions about manual-testing

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

FAQPage Schema
How do I automate manual UI testing for a block-diagram editor?▼

Manual UI testing of a block-diagram editor is automated using Playwright CLI to drive deterministic routines that reproduce real-user interactions across browser-based workflows, validating block operations end-to-end for reliable verification.

What block editor interactions can I validate with Playwright CLI?▼

You can validate block editor interactions such as adding blocks, connecting ports, running simulations, and editing parameters by executing deterministic test routines that reproduce user interactions across sessions for reliable real-world workflow validation.

Do I need a running dev server to run Playwright tests on a block editor?▼

Yes, running Playwright CLI tests against the block-diagram editor requires a running dev server. You also need predefined selectors in the repository and Playwright CLI tooling installed to drive deterministic tests and ensure reproducible interactions.

Why use Playwright CLI for manual testing instead of automated unit tests?▼

Playwright CLI manual testing catches regressions through real-user interactions, whereas unit tests alone cannot validate end-to-end editor scenarios. It applies guided testing to library usage, parameter changes, and block operations across browser sessions.

What are the limitations of manual testing a block editor with Playwright CLI?▼

Manual testing with Playwright CLI requires predefined selectors in the repository to drive deterministic tests. Without these selectors, the tooling cannot reproduce user interactions or ensure reproducible testing across the block-diagram editor's browser-based workflows.

Related Skills

Explore More Software Engineering Skills→
ShunmeiChoShunmeiCho
2

playwright-skill

Automate browser testing with Playwright scripts and dev-server detection.

Community
Advanced
Qiue-GQiue-G

verify

Execute an application and observe outcomes to validate code changes.

Community
Basic
zinohomezinohome
1

e2e-test-builder

Generate end-to-end browser tests for critical user flows with Playwright or Cypress.

Community
Advanced
MathiasPaulenkoMathiasPaulenko

WaveXis Session Recording

Capture and replay browser interactions as YAML sessions via the WaveXis CLI.

Community
Advanced