feature-rollout-qa-testing

name	feature-rollout-qa-testing
description	Use when a feature is being built or rolled out and a detailed QA test script with edge cases and expected outcomes is needed.

Feature Rollout QA Testing

Overview

Generate a rollout-ready QA test script for each feature, including edge cases and explicit expected outcomes.

Always ask for feature context before producing the script.

Required Workflow

1. Ask for missing feature details.
2. Build edge-case coverage across major risk categories.
3. Write a test script in /tests at the project root.
4. Use filename format: YYYY-MM-DD_<feature-slug>_test-script.md.
5. Include expected outcome for every test case.

Required Inputs

Collect these before writing the script:

• Feature name
• Feature owner
• Rollout stage (dev, staging, production, phased)
• Primary personas
• Devices/environments
• Dependencies (APIs, feature flags, integrations)
• Success criteria
• Known constraints or risks

If any item is missing, ask targeted follow-up questions first.

Edge Case Coverage

Include edge cases for:

• Input validation and malformed data
• Empty/no-data states
• Authorization/permissions
• Feature flag off/on transitions
• API failures, timeouts, retries
• Concurrent edits or race conditions
• Browser/device differences
• Accessibility and keyboard-only paths
• Partial rollout and rollback behavior
• Observability (logs, metrics, alerts)

Output File Template

Create /tests/YYYY-MM-DD_<feature-slug>_test-script.md with:

1. Feature summary and rollout context
2. Preconditions and test data setup
3. Happy-path scenarios
4. Edge-case scenarios (with rationale)
5. Negative/error scenarios
6. Observability checks
7. Pass/fail checklist with expected outcomes
8. Sign-off section (tester, date, status, notes)

Test Case Format

Use this per test case:

### TC-<id>: <scenario title>
- **Type:** Happy path | Edge case | Negative
- **Priority:** High | Medium | Low
- **Preconditions:** ...
- **Steps:**
  1. ...
  2. ...
- **Expected outcome:** ...
- **Notes:** ...

Every test case must include a concrete expected outcome.

Completion Checklist

• All required inputs collected or explicitly marked unknown
• Script saved in /tests with required filename format
• Every major workflow branch has edge-case coverage
• Every test includes expected outcome
• Blockers and assumptions are clearly documented