test-plan

place-to-stand's avatarfrom place-to-stand

Generate manual test plans with test cases, role-based scenarios, and edge cases. Use when preparing for QA, before releases, after completing features, or when asked to create test documentation.

⭐0stars🔀0forks📁View on GitHub🕐Updated Jan 9, 2026
[Testing and QA]

When & Why to Use This Skill

This Claude skill automates the generation of comprehensive manual test plans, encompassing functional requirements, edge cases, and role-specific scenarios. It streamlines the quality assurance process by providing structured test cases with clear preconditions, steps, and expected results, ensuring robust software releases and thorough feature validation.

Use Cases

  • Pre-release Quality Assurance: Generate a full suite of prioritized test cases before a major release to ensure all critical paths and edge cases are covered.
  • Feature Validation: Create specific test plans immediately after completing a new feature to verify functional requirements, state transitions, and data persistence.
  • Security and Role-Based Testing: Define scenarios to validate permission boundaries and access control between different user roles like ADMIN and CLIENT.
  • Cross-Platform and Accessibility Audits: Produce checklists for responsive design across various devices and keyboard-only navigation for accessibility compliance.
  • Regression Testing Documentation: Quickly document manual testing procedures for legacy features to prevent regressions during system updates.
nametest-plan
descriptionGenerate manual test plans with test cases, role-based scenarios, and edge cases. Use when preparing for QA, before releases, after completing features, or when asked to create test documentation.

Manual Test Plan Generator

Generate comprehensive manual test plans for features, changes, or releases.

Scope

Create test plans covering:

1. Functional Testing

  • Happy path scenarios
  • Edge cases and boundary conditions
  • Error handling and validation
  • State transitions
  • Data persistence

2. User Flow Testing

  • Complete user journeys
  • Multi-step workflows
  • Navigation and routing
  • Form submissions
  • File uploads (task-attachments, user-avatars)

3. Role-Based Testing

  • ADMIN role scenarios
  • CLIENT role scenarios
  • Permission boundaries
  • Access control verification
  • Client membership scoping

4. Cross-Browser Testing

  • Chrome (latest)
  • Firefox (latest)
  • Safari (latest)
  • Edge (latest)

5. Responsive Testing

  • Mobile (320px+)
  • Tablet (768px+)
  • Desktop (1024px+)
  • Per AGENTS.md: no horizontal scroll

6. Accessibility Testing

  • Keyboard-only navigation
  • Screen reader compatibility
  • Focus management
  • Color contrast

7. Integration Points

  • Supabase Auth flows
  • Supabase Storage operations
  • Email sending (Resend)
  • External API integrations

Output Format

# Test Plan: [Feature Name]

## Overview
Brief description of what's being tested

## Prerequisites
- Required test data
- User accounts needed
- Environment setup

## Test Cases

### TC-001: [Test Case Name]
**Priority:** P0|P1|P2
**Type:** Functional|UI|Integration|Security
**Role:** ADMIN|CLIENT|Unauthenticated

**Preconditions:**
- List of required states

**Steps:**
1. Step-by-step instructions
2. Be specific about clicks/inputs
3. Include expected intermediate states

**Expected Result:**
- What should happen

**Actual Result:**
- [ ] Pass
- [ ] Fail (describe issue)

---

Actions

  1. Analyze the feature or change scope
  2. Identify all user-facing behaviors
  3. Map permission requirements
  4. Consider failure modes
  5. Include regression scenarios

Test Plan Principles

  • Cover both positive and negative cases
  • Include data boundary conditions
  • Test with different user roles
  • Verify soft delete behavior
  • Check loading and empty states

Post-Generation

Provide:

  • Prioritized test case list (P0 first)
  • Estimated testing time
  • Required test data setup scripts
  • Automation candidates for future