UAT Test Case Generator
Overview
This skill generates UAT (User Acceptance Testing) test case documents in Excel format for Salesforce CRM projects. The generated documents include a summary sheet with category breakdowns and a detailed test case list with all required fields for UAT execution.
When to Use This Skill
Use this skill when:
- Creating UAT test case documents for Salesforce implementations
- Generating test cases based on system requirements or user stories
- Converting system flow diagrams or requirement documents into test cases
- Needing a standardized Excel format for UAT documentation with Japanese field names
Workflow
Step 1: Gather Information
Collect the following from the user:
- Project Name: The name of the project (e.g., "Redac Salesforce CRM")
- Requirements Source: User stories, system flow diagrams, or requirement documents
- Test Categories: Main categories (e.g., "Data Migration", "Business Scenarios", "Security")
- Priority Criteria: Guidelines for assigning High/Medium/Low priorities (if not provided, use business criticality)
Step 2: Analyze Requirements
Review the source material and:
- Identify main test categories and sub-categories
- Determine test scenarios for each category
- Group related test cases together
- Assign priorities based on business impact
Step 3: Generate Test Cases
Create test cases with the following structure:
| Field |
Description |
Example |
| テストケースID |
Unique ID (CATEGORY-###) |
DATA-001 |
| 優先度 |
High/Medium/Low |
High |
| カテゴリ |
Main category |
データ移行検証 |
| サブカテゴリ |
Sub-category |
移行データ件数照合 |
| テストシナリオ |
Brief scenario |
Account件数照合 |
| 事前条件 |
Preconditions |
既存CRMからデータ移行済み |
| テスト手順 |
Step-by-step procedure |
1. 既存CRMのAccount総件数を確認\n2. Salesforce UAT環境のAccount総件数を確認\n3. 件数を比較 |
| 期待結果 |
Expected outcome |
移行元と移行先のAccount件数が一致すること |
| 実際の結果 |
Actual result (empty) |
(empty) |
| 合格基準 |
Pass criteria |
件数差異0件 |
| 合否判定 |
Pass/Fail (empty) |
(empty) |
| 実施日 |
Test date (empty) |
(empty) |
| 実施者 |
Tester (empty) |
(empty) |
| 備考 |
Notes (empty) |
(empty) |
| 不具合ID |
Bug ID (empty) |
(empty) |
Test Case ID Format: CATEGORY_CODE-###
- DATA: データ移行検証
- BIZ: 業務シナリオテスト
- SEC: 認証・セキュリティテスト
- EXT: 外部連携テスト
- RPT: レポート・ダッシュボードテスト
- PERF: 性能テスト
- MOB: モバイルテスト
Step 4: Create Excel File
Use the Python script to generate the Excel file:
python scripts/generate_uat_testcases.py \
--project "Redac Salesforce CRM" \
--output "UAT受入試験テストケース一覧.xlsx" \
--testcases testcases.json
The script will:
- Create a "サマリー" (Summary) sheet with category counts and progress tracking
- Create a "全テストケース" (All Test Cases) sheet with detailed test cases
- Apply conditional formatting for visual clarity
Step 5: Review and Deliver
- Verify all test cases are complete and actionable
- Check that priorities are correctly assigned
- Ensure test steps are clear and numbered
- Deliver the Excel file to the user
Common Test Categories
Use these standard categories for Salesforce CRM projects:
1. データ移行検証 (Data Migration Verification)
Sub-categories:
- 移行データ件数照合 (Record count validation)
- データ品質検証 (Data quality validation)
- 関連データ整合性 (Relational integrity)
- 特殊文字・日本語テスト (Special characters and Japanese text)
2. 業務シナリオテスト (Business Scenario Testing)
Sub-categories:
- リード管理 (Lead management)
- 商談管理 (Opportunity management)
- 取引先/取引先責任者管理 (Account/Contact management)
- タスク/活動管理 (Task/Activity management)
- 契約管理 (Contract management)
- 承認プロセス (Approval processes)
3. 認証・セキュリティテスト (Authentication & Security)
Sub-categories:
- ユーザー認証 (User authentication)
- 権限管理 (Permission management)
- データ可視性 (Data visibility/sharing rules)
- プロファイル設定 (Profile settings)
4. 外部連携テスト (External Integration)
Sub-categories:
- API連携 (API integration)
- バッチ処理 (Batch processing)
- ファイル入出力 (File I/O)
- 外部システム連携 (External system integration)
5. レポート・ダッシュボードテスト (Reports & Dashboards)
Sub-categories:
- レポート表示 (Report display)
- ダッシュボード表示 (Dashboard display)
- データフィルタ (Data filtering)
- エクスポート機能 (Export functionality)
Example Usage
User Request:
"Create UAT test cases for our Salesforce data migration. We need to verify Account, Contact, and Opportunity record counts, and also test data quality like required fields and special characters."
Claude's Response Process:
Identify Categories:
- Category: データ移行検証
- Sub-categories: 移行データ件数照合, データ品質検証
Generate Test Cases:
[
{
"id": "DATA-001",
"priority": "High",
"category": "データ移行検証",
"sub_category": "移行データ件数照合",
"scenario": "Account件数照合",
"precondition": "既存CRMからデータ移行済み",
"steps": "1. 既存CRMのAccount総件数を確認\n2. Salesforce UAT環境のAccount総件数を確認\n3. 件数を比較",
"expected": "移行元と移行先のAccount件数が一致すること",
"criteria": "件数差異0件"
},
{
"id": "DATA-002",
"priority": "High",
"category": "データ移行検証",
"sub_category": "移行データ件数照合",
"scenario": "Contact件数照合",
"precondition": "既存CRMからデータ移行済み",
"steps": "1. 既存CRMのContact総件数を確認\n2. Salesforce UAT環境のContact総件数を確認\n3. 件数を比較",
"expected": "移行元と移行先のContact件数が一致すること",
"criteria": "件数差異0件"
},
...
]
Execute Script: Run scripts/generate_uat_testcases.py
Deliver File: Provide the generated Excel file to the user
Scripts
scripts/generate_uat_testcases.py
Python script to generate UAT test case Excel files with proper formatting.
Usage: See script header for detailed usage instructions and examples.
References
references/uat_best_practices.md
UAT testing best practices and guidelines for writing effective test cases.
Tips
- Use clear, action-oriented language in test steps
- Number test steps for clarity (1. 2. 3...)
- Make expected results specific and measurable
- Define objective pass/fail criteria
- Group related test cases under the same sub-category
- Assign priorities based on business impact, not technical complexity
- Keep test scenarios focused on one specific aspect
1---2name: uat-testcase-generator3description: This skill should be used when creating UAT (User Acceptance Testing) test cases in Excel format for Salesforce CRM projects. It generates standardized test case documents with summary sheets and detailed test case lists, following a specific format structure with test case ID, priority, category, scenario, preconditions, test steps, expected results, and acceptance criteria.4---56# UAT Test Case Generator78## Overview910This skill generates UAT (User Acceptance Testing) test case documents in Excel format for Salesforce CRM projects. The generated documents include a summary sheet with category breakdowns and a detailed test case list with all required fields for UAT execution.1112## When to Use This Skill1314Use this skill when:15- Creating UAT test case documents for Salesforce implementations16- Generating test cases based on system requirements or user stories17- Converting system flow diagrams or requirement documents into test cases18- Needing a standardized Excel format for UAT documentation with Japanese field names1920## Workflow2122### Step 1: Gather Information2324Collect the following from the user:25261. **Project Name**: The name of the project (e.g., "Redac Salesforce CRM")272. **Requirements Source**: User stories, system flow diagrams, or requirement documents283. **Test Categories**: Main categories (e.g., "Data Migration", "Business Scenarios", "Security")294. **Priority Criteria**: Guidelines for assigning High/Medium/Low priorities (if not provided, use business criticality)3031### Step 2: Analyze Requirements3233Review the source material and:34- Identify main test categories and sub-categories35- Determine test scenarios for each category36- Group related test cases together37- Assign priorities based on business impact3839### Step 3: Generate Test Cases4041Create test cases with the following structure:4243| Field | Description | Example |44|-------|-------------|---------|45| **テストケースID** | Unique ID (CATEGORY-###) | `DATA-001` |46| **優先度** | High/Medium/Low | `High` |47| **カテゴリ** | Main category | `データ移行検証` |48| **サブカテゴリ** | Sub-category | `移行データ件数照合` |49| **テストシナリオ** | Brief scenario | `Account件数照合` |50| **事前条件** | Preconditions | `既存CRMからデータ移行済み` |51| **テスト手順** | Step-by-step procedure | `1. 既存CRMのAccount総件数を確認\n2. Salesforce UAT環境のAccount総件数を確認\n3. 件数を比較` |52| **期待結果** | Expected outcome | `移行元と移行先のAccount件数が一致すること` |53| **実際の結果** | Actual result (empty) | _(empty)_ |54| **合格基準** | Pass criteria | `件数差異0件` |55| **合否判定** | Pass/Fail (empty) | _(empty)_ |56| **実施日** | Test date (empty) | _(empty)_ |57| **実施者** | Tester (empty) | _(empty)_ |58| **備考** | Notes (empty) | _(empty)_ |59| **不具合ID** | Bug ID (empty) | _(empty)_ |6061**Test Case ID Format**: `CATEGORY_CODE-###`62- DATA: データ移行検証63- BIZ: 業務シナリオテスト64- SEC: 認証・セキュリティテスト65- EXT: 外部連携テスト66- RPT: レポート・ダッシュボードテスト67- PERF: 性能テスト68- MOB: モバイルテスト6970### Step 4: Create Excel File7172Use the Python script to generate the Excel file:7374```python75python scripts/generate_uat_testcases.py \76 --project "Redac Salesforce CRM" \77 --output "UAT受入試験テストケース一覧.xlsx" \78 --testcases testcases.json79```8081The script will:821. Create a "サマリー" (Summary) sheet with category counts and progress tracking832. Create a "全テストケース" (All Test Cases) sheet with detailed test cases843. Apply conditional formatting for visual clarity8586### Step 5: Review and Deliver8788- Verify all test cases are complete and actionable89- Check that priorities are correctly assigned90- Ensure test steps are clear and numbered91- Deliver the Excel file to the user9293## Common Test Categories9495Use these standard categories for Salesforce CRM projects:9697### 1. データ移行検証 (Data Migration Verification)98**Sub-categories**:99- 移行データ件数照合 (Record count validation)100- データ品質検証 (Data quality validation)101- 関連データ整合性 (Relational integrity)102- 特殊文字・日本語テスト (Special characters and Japanese text)103104### 2. 業務シナリオテスト (Business Scenario Testing)105**Sub-categories**:106- リード管理 (Lead management)107- 商談管理 (Opportunity management)108- 取引先/取引先責任者管理 (Account/Contact management)109- タスク/活動管理 (Task/Activity management)110- 契約管理 (Contract management)111- 承認プロセス (Approval processes)112113### 3. 認証・セキュリティテスト (Authentication & Security)114**Sub-categories**:115- ユーザー認証 (User authentication)116- 権限管理 (Permission management)117- データ可視性 (Data visibility/sharing rules)118- プロファイル設定 (Profile settings)119120### 4. 外部連携テスト (External Integration)121**Sub-categories**:122- API連携 (API integration)123- バッチ処理 (Batch processing)124- ファイル入出力 (File I/O)125- 外部システム連携 (External system integration)126127### 5. レポート・ダッシュボードテスト (Reports & Dashboards)128**Sub-categories**:129- レポート表示 (Report display)130- ダッシュボード表示 (Dashboard display)131- データフィルタ (Data filtering)132- エクスポート機能 (Export functionality)133134## Example Usage135136**User Request**:137> "Create UAT test cases for our Salesforce data migration. We need to verify Account, Contact, and Opportunity record counts, and also test data quality like required fields and special characters."138139**Claude's Response Process**:1401411. **Identify Categories**:142 - Category: データ移行検証143 - Sub-categories: 移行データ件数照合, データ品質検証1441452. **Generate Test Cases**:146 ```json147 [148 {149 "id": "DATA-001",150 "priority": "High",151 "category": "データ移行検証",152 "sub_category": "移行データ件数照合",153 "scenario": "Account件数照合",154 "precondition": "既存CRMからデータ移行済み",155 "steps": "1. 既存CRMのAccount総件数を確認\n2. Salesforce UAT環境のAccount総件数を確認\n3. 件数を比較",156 "expected": "移行元と移行先のAccount件数が一致すること",157 "criteria": "件数差異0件"158 },159 {160 "id": "DATA-002",161 "priority": "High",162 "category": "データ移行検証",163 "sub_category": "移行データ件数照合",164 "scenario": "Contact件数照合",165 "precondition": "既存CRMからデータ移行済み",166 "steps": "1. 既存CRMのContact総件数を確認\n2. Salesforce UAT環境のContact総件数を確認\n3. 件数を比較",167 "expected": "移行元と移行先のContact件数が一致すること",168 "criteria": "件数差異0件"169 },170 ...171 ]172 ```1731743. **Execute Script**: Run `scripts/generate_uat_testcases.py`1751764. **Deliver File**: Provide the generated Excel file to the user177178## Scripts179180### `scripts/generate_uat_testcases.py`181182Python script to generate UAT test case Excel files with proper formatting.183184**Usage**: See script header for detailed usage instructions and examples.185186## References187188### `references/uat_best_practices.md`189190UAT testing best practices and guidelines for writing effective test cases.191192## Tips193194- Use clear, action-oriented language in test steps195- Number test steps for clarity (1. 2. 3...)196- Make expected results specific and measurable197- Define objective pass/fail criteria198- Group related test cases under the same sub-category199- Assign priorities based on business impact, not technical complexity200- Keep test scenarios focused on one specific aspect