evaluate

Automate end-to-end smoke testing of the PMTools web app with Playwright.

9|3|Updated Jan 29, 2022
One-click install
npx skills add https://github.com/I194/PMTools_2.0 --skill evaluate-i194
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: evaluate
Source: https://github.com/I194/PMTools_2.0/tree/main/.claude/skills/evaluate
Command: npx skills add https://github.com/I194/PMTools_2.0 --skill evaluate-i194

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual QA of live web apps is time-consuming and error-prone; this skill automates end-to-end testing to surface bugs and regressions in the PMTools app.

Core Features & Use Cases

  • Playwright-based live-user testing to exercise critical flows across the app.
  • Structured feedback with bug reports, observations, and quality scores for quick triage.
  • Use Case: after releases, run full smoke tests to verify landing, navigation, and data workflows.

Quick Start

Run the evaluator on a live instance to begin a full smoke test.

Frequently Asked Questions about evaluate

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

FAQPage Schema
How do I automate end-to-end smoke testing for a live web app?

You can automate end-to-end smoke testing for a live web app using Playwright-based browser control. This skill runs full smoke tests across critical flows like landing, navigation, and data interactions to surface bugs and quality gaps.

How does Playwright-based browser control work for QA testing?

Playwright-based QA testing works by automating live-user interactions against a live environment to exercise critical navigation and data workflows. It enforces read-only testing to safely evaluate application behavior.

What is the best way to generate a structured bug report from automated web app testing?

The best way to generate a structured bug report from automated web app testing is to run a full smoke test evaluation. The process outputs a structured report outlining failures, observations, and quality scores for quick triage.

Can I run read-only automated testing against a live environment?

Yes, you can run read-only automated testing against a live environment. This skill enforces read-only testing during its Playwright-based browser control to ensure QA evaluations do not modify application data.

Does automated QA testing work for navigation and data interaction workflows?

Automated QA testing works for navigation and data interaction workflows by targeting full smoke testing scenarios across PCA and DIR pages. It exercises these critical flows to identify regressions and quality gaps.

When should I run automated smoke tests after a release?

You should run automated smoke tests after releases to verify landing, navigation, and data workflows. This surfaces regressions and quality gaps early by executing critical user flows against the live environment.