| name | test-case-template |
| description | Organizational test case document template and format enforcement rules. Use when generating manual test case files, formatting test case documents, writing coverage summaries, validating the organizational template structure, or ensuring compliance with the mandatory file format including header, individual test case blocks, feature toggle OFF test case, and coverage summary. |
| user-invocable | false |
Organizational Test Case Template
Header Variant Selection
Use the Jira Header when input source is a Jira Story ID.
Use the Non-Jira Header when input source is a User Story, Business Flow, Use Case, API Spec, or freeform text.
Variant A: Jira Story Header
============================================================================================
MANUAL TEST CASES - [FEATURE NAME FROM STORY TITLE]
============================================================================================
Story ID & Title : [STORY-ID] - [Story Title from Jira]
Value Stream : [from customfield_22200]
Subvalue Stream : [from customfield_22201]
Portfolio Team : [from customfield_15604]
Story Description : [Clean rewrite — never copy directly from Jira description]
Feature Toggle State : [toggle-name] is [ON/OFF] (Default)
============================================================================================
PRE-CONDITIONS (Test Suite Level):
============================================================================================
1. [LaunchDarkly/feature toggle state — e.g., "EXPORT_HISTORY toggle is ON in target environment"]
2. [User permissions — e.g., "User has System Administrator role with Web Access Rights"]
3. [Business Rules access — e.g., "User has Business Rules feature access enabled"]
4. [System navigation — e.g., "User can navigate to Settings > Employee History Export"]
5. [Browser/dev tools — e.g., "Chrome DevTools available for network monitoring"]
[Add up to 8 items as appropriate for the story]
============================================================================================
Variant B: Non-Jira Source Header
Use for: User Story, Business Flow, Use Case, API Specification, or freeform feature description.
============================================================================================
MANUAL TEST CASES - [FEATURE NAME]
============================================================================================
Reference ID & Title : [REF-ID] - [Derived Feature Title]
Source Type : [User Story | Business Flow | Use Case | API Specification | Freeform]
Input Source : [Brief description of the provided input — e.g., "POST /api/v1/payments spec"]
Value Stream : [User-provided or N/A]
Subvalue Stream : [User-provided or N/A]
Portfolio Team : [User-provided or N/A]
Feature Description : [Clean rewrite of the provided input — summarise the feature being tested]
Feature Toggle State : [toggle-name] is [ON/OFF] (Default) | N/A (if no toggle mentioned)
Derived Requirements:
============================================================================================
AC-1: [First extracted requirement / testable behavior]
AC-2: [Second extracted requirement]
AC-3: [Additional extracted requirements...]
[Number all derived ACs sequentially — each distinct testable behavior = one AC]
============================================================================================
PRE-CONDITIONS (Test Suite Level):
============================================================================================
1. [System/environment state required before running tests]
2. [Authentication or API token availability — if applicable]
3. [Test data prerequisites]
4. [Required service dependencies or feature state]
5. [Browser/tool requirements if UI-based — or API client if API-based]
[Add up to 8 items as appropriate]
============================================================================================
Individual Test Case Block (Exact Format)
Opening and closing separator (must be exact — character count matters):
////********************************************************************************
Use [STORY-ID] for Jira-sourced test cases. Use [REF-ID] for all other source types.
////********************************************************************************
Reference ID & Title : [STORY-ID or REF-ID] — [Title]
Acceptance Criteria : AC-[X]
Test Case ID : [STORY-ID or REF-ID]-AC[X]-TC[010]
Scenario Type : [Positive | Negative | Boundary]
Test Design Technique: [Technique Name]
Feature Toggle State : [ON | OFF]
Test Title : [Specific, descriptive scenario title — what is being validated]
Test Steps :
GIVEN [feature toggle state and system precondition — exactly 8 spaces]
AND [additional precondition if needed]
WHEN [user action]
AND [additional action if needed]
THEN [expected result]
AND [additional expected result if needed]
Notes :
- [Implementation note or testing consideration]
- [Additional context, edge case note, or dependency]
////********************************************************************************
Format Enforcement Rules (Non-Negotiable)
| Rule | Requirement |
|---|
| Separator line | Exactly ////******************************************************************************** |
| Test Case ID | [STORY-ID]-AC[X]-TC[010] — increments of 10 (010, 020, 030...) |
| Story title punctuation | Em dash — (U+2014) in "Story ID & Title" — NOT hyphen - |
| BDD indentation | Exactly 8 space characters before GIVEN/WHEN/THEN/AND — never tabs |
| Pre-generation check | If ANY rule fails: stop, fix the issue, then generate |
Mandatory: Feature Toggle OFF Test Case
Every story MUST include this test case (minimum one):
////********************************************************************************
Story ID & Title : <STORY-ID> — <Story Title>
Acceptance Criteria : Feature Toggle OFF
Test Case ID : <STORY-ID>-TOGGLE-TC010
Scenario Type : Negative
Test Design Technique: State Transition Testing
Feature Toggle State : OFF
Test Title : Verify [feature name] is inaccessible when feature toggle is OFF
Test Steps :
GIVEN [Feature Toggle Name] feature toggle is OFF
AND User has access to [Feature Area]
WHEN User navigates to [Feature Location]
AND User attempts to [Primary Action]
THEN [Feature] functionality is not accessible to the user
AND No feature-specific UI elements are visible
AND No toggle-related errors or exceptions occur
Notes :
- Verify backward compatibility and graceful degradation
- Ensure no regression in existing non-toggle-dependent functionality
////********************************************************************************
Coverage Summary (Mandatory End Section)
Every test case file MUST end with this complete section:
============================================================================================
COVERAGE SUMMARY
============================================================================================
## MASTER TEST COVERAGE MATRIX
| AC # | Description | Test Case IDs | Techniques Applied | Positive | Negative | Boundary | Status |
|------|-------------|---------------|--------------------|----------|----------|----------|--------|
| AC-1 | [AC-1 Description] | [STORY-ID]-AC1-TC010, TC020, TC030 | Use Case Testing, BVA | X | X | X | ✅ |
| AC-2 | [AC-2 Description] | [STORY-ID]-AC2-TC010, TC020 | State Transition, Error Guessing | X | X | 0 | ✅ |
| General | Feature Toggle | [STORY-ID]-TOGGLE-TC010 | State Transition | 0 | X | 0 | ✅ |
## OVERALL METRICS SUMMARY
| Metric | Value | Details |
|--------|-------|---------|
| **Total Test Cases** | [XX] | Comprehensive coverage across all ACs |
| **Acceptance Criteria** | [X] Primary | All covered with multiple scenarios |
| **Test Design Techniques** | [X] | [List techniques used] |
| **Scenario Distribution** | P:[X], N:[X], B:[X] | Balanced coverage |
| **Coverage Completeness** | 100% | All ACs addressed |
Coverage Highlights:
========================================================================================
✔ All [X] Primary Acceptance Criteria addressed with comprehensive test scenarios
✔ State transition testing ensures proper toggle behavior in all states
✔ Feature functionality validated in both ON/OFF toggle states with edge cases
✔ Error handling and resilience testing included
✔ Authorization and security validation with unauthorized access testing
========================================================================================
Pre-Generation Validation Checklist
Verify ALL items before writing the output file:
Header
Test Cases
Footer
