qa-test

Execute structured QA test plans for the Wheelbase Electron app via Electron MCP tools.

Updated Mar 6, 2026
One-click install
npx skills add https://github.com/jcteague/wheelbase --skill qa-test-jcteague
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-test
Source: https://github.com/jcteague/wheelbase/tree/main/.claude/skills/qa-test
Command: npx skills add https://github.com/jcteague/wheelbase --skill qa-test-jcteague

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures the Wheelbase Electron app functions correctly by running structured manual QA tests, validating UI flows, and verifying acceptance criteria against live builds.

Core Features & Use Cases

  • Reads and drives test plans from docs/epics/02-stories/ to exercise new features and regression coverage.
  • Executes actions via the Electron MCP tools (window inspection, screenshots, navigation, form interactions, and log review).
  • Performs adversarial testing to surface edge cases not covered by happy-path scenarios and validate robustness.

Quick Start

Execute a full manual QA pass by loading the relevant test plans and driving the app with MCP tools to verify UI flows and data handling.

Frequently Asked Questions about qa-test

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

FAQPage Schema
How do I automate end-to-end QA testing for an Electron app?

Automate end-to-end QA testing for an Electron app by reading structured test plans and executing them through Electron MCP tools. This validates UI flows, form interactions, and navigation against live builds.

How do I validate new features and run regression tests using test plans?

Validate new features and run regression tests by loading structured manual test plans from docs/epics/02-stories and driving the application with Electron MCP tools to verify acceptance criteria.

Can I perform adversarial edge-case testing for UI verification?

Yes, you can perform adversarial edge-case testing for UI verification to surface edge cases not covered by happy-path scenarios. This validates application robustness and ensures data handling stability.

Does this QA testing approach support window inspection and screenshots?

Yes, this QA testing approach supports window inspection, screenshots, navigation, form interactions, and log review. It executes these actions via Electron MCP tools to verify UI flows and log test results.

What is the best way to execute a manual QA pass for a live build?

The best way to execute a manual QA pass for a live build is to load the relevant test plans and drive the application with Electron MCP tools to verify UI flows, applying clear pass/fail criteria to log results.