exploratory-test

Identify acceptance criteria gaps through guided exploratory walks with captured evidence.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Cottage-Energy/cottage-tests --skill exploratory-test
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: exploratory-test
Source: https://github.com/Cottage-Energy/cottage-tests/tree/main/.claude/skills/exploratory-test
Command: npx skills add https://github.com/Cottage-Energy/cottage-tests --skill exploratory-test

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps testers and developers systematically explore applications to uncover bugs, verify edge cases, and document findings through interactive walks or scaffolded specs.

Core Features & Use Cases

  • Interactive exploration to uncover hidden bugs and understand behavior under edge cases
  • Scaffolded specs generation to share investigations with the team
  • Documentation of findings and recommended improvements for faster remediation

Quick Start

Initiate an exploratory session on a ticket to walk through acceptance criteria and capture evidence

Frequently Asked Questions about exploratory-test

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

FAQPage Schema
How do I conduct exploratory testing to uncover hidden bugs and edge cases?

Exploratory testing uncovers hidden bugs by conducting guided interactive walks across your product to identify gaps in acceptance criteria and verify behavior under edge cases.

Can I capture screenshots and DB state during interactive QA exploration?

Yes, you can capture evidence such as screenshots, DB state, and network activity during both interactive exploration and scaffolded spec generation to document findings.

How do I turn exploratory testing findings into actionable test artifacts?

You can convert exploratory testing findings into actionable test artifacts and process improvements by generating scaffolded specs that share investigations with your team.

Does this exploratory testing approach work with Playwright for edge case verification?

Playwright is supported within the testing workflow, enabling you to conduct guided exploratory walks and verify edge cases interactively across the product.

What is the best way to document QA findings for faster team remediation?

The best way to document QA findings is to capture evidence like DB state and network activity during interactive walks, then convert them into scaffolded specs for remediation.