qualiow-exploratory-testing-skills

Run a full AI-driven exploratory testing session on a simulator/emulator — works for BOTH a NATIVE app (the installed app is the system under test) and a WEB app loaded in the real device browser (iOS Simulator Safari / Android emulator Chrome). The mode is selected from the target config. Same Principal-QA mindset as /qa-explore, but the driver is Maestro (via the mobile-cli shim) instead of Playwright, and the phases are adapted for mobile concerns (app/browser lifecycle, rotation, on-screen keyboard, deep links, offline, permissions, native a11y tree). Use when user says: "test on the simulator/emulator", "explore the app on iOS/Android", "find bugs on mobile", "QA the mobile build", or provides a mobile-sim target (native or web).

Quick focused exploratory testing session on a single page or feature (~15 min). No full site mapping — goes directly to the target, applies heuristics, reports findings. Use when user says: "quick check", "test this page", "quick explore", or wants a fast review.

Run a full AI-driven exploratory testing session against a web application. Acts as a Principal QA Engineer — understands the business first, risk-ranks features, tests end-to-end user journeys, verifies data integrity, finds what's MISSING, and writes bug reports that executives act on. Use when user says: "explore", "test this site", "find bugs", "QA check", "exploratory session", or provides a URL to test.

Interactive setup for a new target application. Navigates to the URL, detects auth requirements, walks through login flow creation, auto-detects scope, and saves target config. Use when user says: "setup target", "add target", "configure app", "new target".

Quick focused exploratory testing session on a single page or feature (~15 min). No full site mapping — goes directly to the target, applies heuristics, reports findings. Use when user says: "quick check", "test this page", "quick explore", or wants a fast review.

Run a full AI-driven exploratory testing session against a web application. Acts as a Principal QA Engineer — understands the business first, risk-ranks features, tests end-to-end user journeys, verifies data integrity, finds what's MISSING, and writes bug reports that executives act on. Use when user says: "explore", "test this site", "find bugs", "QA check", "exploratory session", or provides a URL to test.

Manage exploratory testing sessions — list, archive, or delete old sessions. Use when user says: "cleanup sessions", "delete old sessions", "archive", "list sessions".

Capture post-session feedback to improve future exploratory testing sessions. Identifies false positives, missed bugs, and extracts patterns for the knowledge base. Use after completing an exploratory session or when user says: "review session", "false positive", "missed bug", "session feedback".

Generate, regenerate, or reformat reports from existing exploratory testing sessions. Use when user says: "show report", "generate report", "reformat bugs", "session summary", or wants to review past session findings.

Gather and analyze requirements from various sources to prepare context for exploratory testing sessions. Collects from Jira tickets, Confluence pages, design docs, PRs, acceptance criteria, pasted text, URLs — and produces structured context that /qa-explore consumes. Use when user says: "gather requirements", "prepare context", "analyze this ticket", "what should I test", or provides requirements documents before an explore session.

Add new QA knowledge to the knowledge base — heuristics, techniques, checklists, references, or patterns. Supports text input, URLs, and file ingestion. Use when user says: "add knowledge", "add heuristic", "learn this", "save this technique", "add to knowledge base", or provides QA documentation to ingest.

Browse and search the QA knowledge base. List entries by type, domain, or tag. Show changelog and stats. Use when user says: "list knowledge", "show heuristics", "what's in the knowledge base", "knowledge stats", "show changelog".