Skip to content

jaktestowac/awesome-copilot-for-testers / plugins/designing-functional-tests/skills/designing-functional-tests

designing-functional-tests

Verified

Designs risk-based functional test plans, manual test cases, regression slices, and automation handoff packs from requirements, URLs, or exploratory notes. Use when preparing manual QA coverage before automation, turning feature descriptions into scenario catalogs, or converting exploratory findings into structured test assets.

FileKindSize
SKILL.mdskill md6.3 KB
resources/manual-test-cases-template.mdmarkdown975 B
resources/test-plan-template.mdmarkdown2.1 KB

resources/test-plan-template.md

View on GitHub
# Functional Test Plan - [Feature / Flow Name]

## 1. Goal

State the user or business outcome this plan is validating.

## 2. Test basis

- Source: [story / AC / URL / exploratory notes]
- Environment: [dev / stage / prod-like]
- Roles covered: [guest / user / admin / other]

## 3. Scope

### In scope

- [flow or capability]
- [flow or capability]

### Out of scope

- [explicitly excluded area]
- [explicitly excluded area]

## 4. Risk and priority map

| Area              | Priority | Why it matters   | Coverage notes                |
| ----------------- | -------- | ---------------- | ----------------------------- |
| [Checkout]        | High     | [Money movement] | [Happy + negative + recovery] |
| [Profile editing] | Medium   | [High usage]     | [Happy + boundary]            |

## 5. Scenario catalog

### SCN-001 - [Short scenario title]

- **Type:** happy / negative / boundary / permission / recovery / a11y-smoke
- **Priority:** High / Medium / Low
- **Preconditions:** [required starting state]
- **Steps:**
  1. [action]
  2. [action]
- **Expected result:** [observable outcome]
- **Notes:** [data, assumptions, open questions]

### SCN-002 - [Short scenario title]

- **Type:** happy / negative / boundary / permission / recovery / a11y-smoke
- **Priority:** High / Medium / Low
- **Preconditions:** [required starting state]
- **Steps:**
  1. [action]
  2. [action]
- **Expected result:** [observable outcome]
- **Notes:** [data, assumptions, open questions]

## 6. Assumptions and open questions

- [ASSUMPTION] [missing rule or expected behavior]
- [OPEN QUESTION] [what still needs clarification]

## 7. Automation handoff

| Scenario ID | Automation candidate | Why                     | Suggested next step         |
| ----------- | -------------------- | ----------------------- | --------------------------- |
| SCN-001     | high                 | [stable and repeatable] | [send to Playwright prompt] |
| SCN-002     | medium               | [needs data setup]      | [add fixtures first]        |

## 8. Exit signal

This plan is ready when:

- scope is explicit
- risky flows have deeper coverage
- assumptions are visible
- scenarios are identifiable and reusable
finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the workStars: 322kUpdated Claude CodeCodexVerifiedInstall
systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesStars: 322kUpdated Claude CodeCodexVerifiedInstall
test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation codeStars: 322kUpdated Claude CodeCodexVerifiedInstall
skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.Stars: 198kUpdated Claude CodeCodexVerifiedInstall