skills.rest
lucasfcosta
lucasfcostaCOMMUNITY
Explore all skills by this author →
Website𝕏@thewizardlucasGitHub

manual-testing

Manually verify live application behavior and document evidence for pass/fail decisions.

62|2|Updated May 29, 2026
Search Tags:#verification#evidence#end-to-end#playwright#api-testing#curl#manual-testing
One-click install
npx skills add https://github.com/lucasfcosta/backpressured --skill manual-testing-lucasfcosta
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: manual-testing
Source: https://github.com/lucasfcosta/backpressured/tree/main/skills/manual-testing
Command: npx skills add https://github.com/lucasfcosta/backpressured --skill manual-testing-lucasfcosta

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual testing verifies that a feature works in the running application, not just in automated tests, ensuring real-world behavior is validated.

Core Features & Use Cases

  • End-to-end verification of feature behavior in a live system, including API calls and UI flows.
  • Documentation of evidence for pass/fail decisions, such as curl responses and Playwright screenshots.
  • Use Case: perform before-done checks in Phase 3 to confirm new behavior before finishing a task.

Quick Start

Boot the app, run the manual-testing gate against the live system, and document the evidence from curl commands, UI interactions, and screenshots.

Frequently Asked Questions about manual-testing

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

FAQPage Schema
How do I validate end-to-end behavior in a live application beyond automated tests?▼

Manual testing validates end-to-end behavior by interacting with the running application to confirm real-world results. It executes live API calls and browser interactions, including unhappy paths, to verify actual system behavior.

What is the best way to record evidence for manual API testing and UI checks?▼

Record evidence for manual testing by documenting executed curl commands, observed API responses, and Playwright screenshots. Capturing this output provides concrete proof to determine pass or fail status and identify blockers.

Can I use Playwright to capture screenshots for end-to-end testing evidence?▼

Yes, Playwright captures screenshots during end-to-end testing to document UI interactions and unhappy paths. These screenshots serve as visual evidence to confirm feature behavior and support pass or fail decisions.

How do I verify live API calls using curl during end-to-end testing?▼

Verify live API calls during end-to-end testing by executing curl commands against the running application. Documenting the observed curl responses provides evidence to validate real-world behavior and identify blockers.

When should I perform manual end-to-end verification instead of relying on automated tests?▼

Perform manual end-to-end verification during Phase 3 to validate live behavior that automated tests might not cover. It confirms real-world API calls and UI interactions before finishing a task and declaring done.

Related Skills

Explore More Software Engineering Skills→
brdloushbrdloush
5

livewire

Provide live nREPL access to a running Spring Boot application.

Community
Advanced
ShinyGuaShinyGua

mm-report-reviewer

Score research reports across six dimensions and output pass/fail JSON.

Community
Advanced
billydeeii136billydeeii136

webapp-testing

Automate local web application testing with Playwright and Python scripts.

Community
Advanced
eng-vmessiaheng-vmessiah
2

ai-regression-testing

Automate regression tests validating API response shapes and state integrity.

Community
Intermediate