execute-manual-tests

Execute manual test suites against released artifacts and generate PASS/FAIL reports.

6|Updated Aug 3, 2025
One-click install
npx skills add https://github.com/foomakers/pair --skill execute-manual-tests
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: execute-manual-tests
Source: https://github.com/foomakers/pair/tree/main/packages/knowledge-hub/dataset/.skills/capability/execute-manual-tests
Command: npx skills add https://github.com/foomakers/pair --skill execute-manual-tests

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the execution of manual test suites against software artifacts, ensuring quality and providing structured reports without manual intervention.

Core Features & Use Cases

  • Automated Test Execution: Runs predefined manual test cases against deployed applications or packages.
  • Structured Reporting: Generates detailed PASS/FAIL reports with evidence for each test case and critical path.
  • Use Case: After a new version of a web application is deployed to staging, this Skill can automatically run the critical path test suite, verify core functionality, and report any regressions.

Quick Start

Execute the manual test suite located in the 'qa/suites' directory for version 1.2.3.

Frequently Asked Questions about execute-manual-tests

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

FAQPage Schema
How do I run manual test suites against released artifacts and generate a report?

To run manual test suites against released artifacts, this Skill executes predefined test cases, resolves test variables, iterates through critical paths, records PASS/FAIL per case, and generates a structured report from a manual-test-report template.

What is the best way to automate manual test execution for a deployed web application?

Automating manual test execution involves running predefined critical path test cases against deployed applications or packages to verify core functionality, automatically recording PASS/FAIL results, and generating detailed reports to identify any regressions.

Can I use this manual testing Skill independently for post-merge validation?

Yes, you can invoke manual test execution independently to validate released artifacts, or it can be composed by a review process for post-merge validation to ensure quality without manual intervention.

Does manual test execution require specific test variables or a dedicated suite directory?

Manual test execution resolves test variables automatically and iterates through critical paths, requiring predefined manual test suites located within your project directories to successfully execute and generate structured reports.

What limitations exist when automating manual test reporting for staging environments?

Automating manual test reporting requires predefined manual test cases and deployed artifacts; it does not create test cases dynamically, but rather executes existing suites to verify core functionality and report regressions.

How does automated manual test execution handle PASS/FAIL reporting for critical paths?

Automated manual test execution handles PASS/FAIL reporting by iterating through critical paths, resolving test variables, recording the outcome per test case, and generating a structured report with evidence from a manual-test-report template.