skills.rest
tuanemuy
tuanemuyCOMMUNITY
Explore all skills by this author →
GitHub

manual-test

Automate browser-based manual tests with agent-browser and generate screenshot reports.

Updated Feb 27, 2025
Search Tags:#automation#reporting#issue-tracking#browser-testing#qa-engineering#manual-test
One-click install
npx skills add https://github.com/tuanemuy/dotfiles --skill manual-test
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: manual-test
Source: https://github.com/tuanemuy/dotfiles/tree/main/config/claude/skills/manual-test
Command: npx skills add https://github.com/tuanemuy/dotfiles --skill manual-test

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill automates the execution of browser-based manual tests described in testing.md and spec/manual-tests/ by using agent-browser to run end-to-end verification, capture results, and surface defects.

Core Features & Use Cases

  • Automates browser-based test execution for documentation-driven QA workflows, including Web server startup with portable port auto-detection, seed data preparation, test case execution, and screenshot-powered reports.
  • Generates structured results and, on failures, triggers issue creation workflows; supports per-test-session isolation and documentation of outcomes for traceability.
  • Suitable for validating UI flows, regression checks, and manual-test automation in projects that rely on agent-browser to validate browser behavior.

Quick Start

Run the manual-test skill to automatically execute testing procedures with agent-browser and generate a report.

Frequently Asked Questions about manual-test

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

FAQPage Schema
How do I automate browser-based manual testing from documentation?▼

Browser-based manual testing is automated by executing documentation-driven test steps through agent-browser, which navigates UI flows and generates screenshot-laden reports for end-to-end verification.

What's the best way to generate test reports and track defects from browser testing?▼

Browser testing generates structured screenshot-powered reports after execution and automatically triggers GitHub issue creation workflows when test failures surface defects for traceability.

How does agent-browser handle Web server startup and seed data preparation for QA engineering?▼

Agent-browser handles QA workflows by automating seed data preparation and Web server startup with portable port auto-detection before executing documentation-driven test cases.

Can I use documentation in testing.md and spec directories to drive deterministic test execution?▼

Yes, testing.md and spec/manual-tests/ directories drive deterministic test execution by providing frontmatter metadata and optional resources in scripts, references, and assets folders.

Does browser test automation support per-test-session isolation for regression checks?▼

Yes, browser test automation supports per-test-session isolation to ensure clean regression checks and validate UI flows without cross-test contamination during end-to-end verification.

Why do I need frontmatter metadata like name and description for manual test automation?▼

Frontmatter metadata containing name and description is required to drive deterministic manual test automation tasks and provide rich context for agent-browser execution phases.

Related Skills

Explore More Software Engineering Skills→
cryborg1211cryborg1211

vc:agent-browser

Automate long-running browser tasks via CLI with context-efficient snapshots and refs.

Community
Intermediate
concept2cureconcept2cure

qa

Test web applications, identify defects, and document fixes with health scores.

Community
Advanced
brsblbrsbl
14

browser

Automate browser tasks to inspect UI, capture screenshots, fill forms, and extract page data.

Community
Intermediate
JBonfimJBonfim

qa-report

Generate test plans, test cases, regression suites, and bug reports.

Community
Advanced