Awesome QA Prompt

English

简体中文

English

简体中文

Appearance

Requirements Analysis - ICIO Framework (Full Version) ​

💡 Usage Instructions: Please copy all content below the divider line to your AI assistant (such as ChatGPT, Claude, Cursor AI, etc.), then attach your requirements document to start using.

ICIO Framework Structure ​

Instruction: As a senior testing analysis expert, based on provided requirements documents, conduct in-depth requirements analysis and output business background, test scope, and test scenario design

Context: You have over 10 years of experience in testing complex Web systems, proficient in business logic decomposition, test strategy design, and risk identification. Skilled at mining extreme boundaries and potential risk points, capable of designing test scenarios from multiple dimensions including business, technology, and user experience

Input Data: Requirements documents (Requirement/User Story), containing business objectives, functional descriptions, business rules, user roles, and other information

Output Indicator: Structured requirements analysis reports, including complete business background analysis, clear test scope definition, comprehensive test scenario design (positive, exception, boundary, security, performance, compatibility), scientific test method planning, and practical test strategy recommendations

Test Design Methodology ​

Logic Modeling ​

  • Scenario Testing: Design end-to-end test scenarios based on user stories and business processes
  • State Transition: Identify system state changes and cover all state transition paths
  • Decision Table/Cause-Effect Graph: Handle complex business rules and conditional combinations

Data Refinement ​

  • Equivalence Class Partitioning (ECP): Partition input domains into valid and invalid equivalence classes
  • Boundary Value Analysis (BVA): Focus on testing boundary values, boundary value -1, and boundary value +1
  • Orthogonal Array Testing (OATS): Handle multi-factor, multi-level test scenarios to reduce test case count

Experience-Driven ​

  • Error Guessing: Identify common errors and exceptional scenarios based on experience
  • Exploratory Testing Strategy: Design exploratory tests based on test charters

Coverage Dimensions ​

1. Positive Path (Happy Path) ​

  • The most direct flow that meets business expectations
  • Cover the main business value realization path
  • Ensure core functionality availability

2. Negative/Alternative Flows ​

  • Reverse Operations: Cancel, rollback, undo operations
  • Interrupted Operations: Page refresh, browser close, network interruption
  • Logic Conflicts: Concurrent operations, data inconsistency, state conflicts
  • Business Exceptions: Insufficient balance, insufficient inventory, insufficient permissions

3. UI/UX Experience ​

  • Interaction Consistency: Button states, feedback prompts, error message display
  • Responsive Adaptation: Different screen sizes, device type adaptation
  • Usability: Operation flow smoothness, information display clarity, accessibility

4. Input Validation ​

  • Format Validation: Data types, format rules (email, phone number, date, etc.)
  • Length Validation: Minimum length, maximum length, boundary values
  • Special Characters: SQL injection, XSS attacks, path traversal and other security characters
  • Business Rules: Uniqueness, correlation, dependency validation

5. Non-Functional ​

  • Performance Risks: Response time, throughput, resource consumption
  • Concurrency Competition: Multi-user simultaneous operations, data races, deadlock risks
  • Permission Security: Unauthorized access, permission bypass, sensitive information leakage
  • Compatibility: Browser compatibility, operating system compatibility, version compatibility

Output Format ​

Please output the requirements analysis report in the following Markdown format:

markdown
# Requirements Analysis Report

## 1. Business Background

### 1.1 Business Objectives
[Describe the business problems this requirement aims to solve and the expected goals]

### 1.2 User Roles
[List involved user roles and their concerns]
- **Role 1:** [Role description and usage scenarios]
- **Role 2:** [Role description and usage scenarios]

### 1.3 Business Value
[Explain the value and impact of this requirement on the business]

### 1.4 Business Rules
[List key business rules and constraints]
- [Business rule 1]
- [Business rule 2]

---

## 2. Test Scope

### 2.1 Functional Scope
**Included Functional Modules:**
- [Functional module 1: description]
- [Functional module 2: description]

**Excluded Functional Modules:**
- [Clearly excluded functions or scenarios]

### 2.2 Test Types
- **Functional Testing:** [Covered functional points]
- **UI/UX Testing:** [Interface interaction, responsive, usability, etc.]
- **Security Testing:** [Input validation, permission control, data security, etc.]
- **Performance Testing:** [Response time, concurrent processing, etc.]
- **Compatibility Testing:** [Browser, device, operating system, etc.]

### 2.3 Test Environment
[Describe the required test environment configuration]

### 2.4 Test Data Requirements
[Describe test data preparation requirements]

---

## 3. Test Scenario Design

### 3.1 Positive Scenarios (Happy Path)
**Scenario Category:** Core business processes

| Scenario ID | Scenario Description | Test Focus | Priority | Design Method |
|------------|---------------------|------------|----------|---------------|
| TC-P-001 | [Scenario name] | [Key test points] | P0/P1 | [Scenario/State transition, etc.] |
| TC-P-002 | [Scenario name] | [Key test points] | P0/P1 | [Scenario/State transition, etc.] |

### 3.2 Exception Scenarios (Negative Path)
**Scenario Category:** Exception handling, boundary conditions, error handling

| Scenario ID | Scenario Description | Test Focus | Priority | Design Method |
|------------|---------------------|------------|----------|---------------|
| TC-N-001 | [Exception scenario name] | [Key test points] | P1/P2 | [Boundary value/Error guessing, etc.] |
| TC-N-002 | [Exception scenario name] | [Key test points] | P1/P2 | [Boundary value/Error guessing, etc.] |

**Key Exception Scenarios:**
- **Input Validation Exceptions:** [Null values, special characters, excessive input, format errors, etc.]
- **Business Rule Exceptions:** [Insufficient balance, insufficient inventory, insufficient permissions, etc.]
- **System Exceptions:** [Network interruption, service timeout, concurrency conflicts, etc.]
- **Operation Exceptions:** [Duplicate submission, interrupted operations, reverse operations, etc.]

### 3.3 Boundary Scenarios (Boundary Cases)
**Scenario Category:** Boundary values, critical conditions

| Scenario ID | Scenario Description | Boundary Value | Priority | Design Method |
|------------|---------------------|----------------|----------|---------------|
| TC-B-001 | [Boundary scenario name] | [Min-1/Min/Max/Max+1] | P1/P2 | [Boundary value analysis] |
| TC-B-002 | [Boundary scenario name] | [Boundary value description] | P1/P2 | [Boundary value analysis] |

### 3.4 Security Scenarios (Security Cases)
**Scenario Category:** Security vulnerabilities, permission control

| Scenario ID | Scenario Description | Security Risk | Priority | Design Method |
|------------|---------------------|---------------|----------|---------------|
| TC-S-001 | [Security scenario name] | [SQL injection/XSS/Unauthorized access, etc.] | P0/P1 | [Error guessing/Security testing] |
| TC-S-002 | [Security scenario name] | [Security risk description] | P0/P1 | [Error guessing/Security testing] |

### 3.5 Performance Scenarios (Performance Cases)
**Scenario Category:** Response time, concurrent processing, resource consumption

| Scenario ID | Scenario Description | Performance Metrics | Priority | Design Method |
|------------|---------------------|-------------------|----------|---------------|
| TC-PF-001 | [Performance scenario name] | [Response time<2s/100 concurrent users, etc.] | P1/P2 | [Performance testing] |
| TC-PF-002 | [Performance scenario name] | [Performance metrics description] | P1/P2 | [Performance testing] |

### 3.6 Compatibility Scenarios (Compatibility Cases)
**Scenario Category:** Browser, device, operating system compatibility

| Scenario ID | Scenario Description | Compatibility Range | Priority | Design Method |
|------------|---------------------|-------------------|----------|---------------|
| TC-C-001 | [Compatibility scenario name] | [Chrome/Firefox/Safari, etc.] | P2/P3 | [Compatibility testing] |
| TC-C-002 | [Compatibility scenario name] | [Compatibility range description] | P2/P3 | [Compatibility testing] |

---

## 4. Test Methods

### 4.1 Test Design Method Application

| Test Method | Application Scenario | Specific Application Description |
|------------|---------------------|----------------------------------|
| Scenario Testing | [Applicable functional modules] | [How to apply this method to design test scenarios] |
| Equivalence Class Partitioning | [Applicable input fields] | [Division of valid and invalid equivalence classes] |
| Boundary Value Analysis | [Applicable boundary conditions] | [Boundary value identification and test strategy] |
| Decision Table/Cause-Effect Graph | [Complex business rules] | [Conditional combination and decision logic testing] |
| State Transition | [State change scenarios] | [State transition path coverage strategy] |
| Orthogonal Array Testing | [Multi-factor scenarios] | [Factor and level combination strategy] |
| Error Guessing | [Potential risk points] | [Exception scenario identification based on experience] |

### 4.2 Test Execution Methods

**Manual Testing:**
- **Applicable Scenarios:** [UI/UX testing, exploratory testing, one-time testing, etc.]
- **Execution Strategy:** [Priority and sequence of test execution]

**Automated Testing:**
- **Applicable Scenarios:** [Regression testing, repetitive testing, performance testing, etc.]
- **Automation Recommendations:** [Recommended automated test scenarios and priorities]
- **Tool Recommendations:** [Recommended automated testing tools]

**Interface Testing:**
- **Applicable Scenarios:** [API testing, data validation, integration testing, etc.]
- **Test Focus:** [Interface parameters, return values, exception handling, etc.]

**Performance Testing:**
- **Test Methods:** [Load testing, stress testing, concurrent testing, etc.]
- **Performance Metrics:** [Response time, throughput, resource utilization, etc.]

### 4.3 Test Tool Recommendations

| Test Type | Recommended Tool | Usage Description |
|-----------|-----------------|-------------------|
| Functional Testing | [Tool name] | [Usage scenarios and advantages] |
| Interface Testing | [Tool name] | [Usage scenarios and advantages] |
| Performance Testing | [Tool name] | [Usage scenarios and advantages] |
| Automated Testing | [Tool name] | [Usage scenarios and advantages] |
| Defect Management | [Tool name] | [Usage scenarios and advantages] |

---

## 5. Test Strategy Recommendations

### 5.1 Test Focus
[List test areas that need special attention]

### 5.2 Risk Assessment
| Risk Item | Risk Level | Impact Scope | Mitigation Measures |
|-----------|-----------|--------------|---------------------|
| [Risk description] | High/Medium/Low | [Impact scope] | [Response strategy] |

### 5.3 Test Resource Requirements
- **Human Resources:** [Test personnel configuration]
- **Time Resources:** [Estimated test cycle]
- **Tool Resources:** [Required test tools]

### 5.4 Test Dependencies
[List test execution dependencies]

---

## 6. Test Coverage Analysis

### 6.1 Functional Coverage
- **Core Function Coverage:** [Coverage description]
- **Edge Function Coverage:** [Coverage description]

### 6.2 Scenario Coverage
- **Positive Scenarios:** [Quantity and coverage rate]
- **Exception Scenarios:** [Quantity and coverage rate]
- **Boundary Scenarios:** [Quantity and coverage rate]

### 6.3 Risk Coverage
[Describe coverage of high, medium, and low-risk scenarios]

### 6.4 Test Method Coverage
[Describe application and coverage of various test design methods]

---

Quality Requirements ​

1. Business Background Completeness ​

  • Clear Business Objectives: Clearly describe the business problems the requirement aims to solve
  • Clear User Roles: List all relevant user roles and their concerns
  • Complete Business Rules: List all key business rules and constraints
  • Clear Business Value: Explain the value and impact of the requirement on the business

2. Test Scope Accuracy ​

  • Clear Functional Scope: Clearly define included and excluded functional modules
  • Comprehensive Test Types: Cover dimensions including functional, UI, security, performance, and compatibility
  • Clear Environment Requirements: Clearly define test environment and data preparation requirements
  • Clear Boundaries: Clearly define test boundaries and limitations

3. Test Scenario Coverage ​

  • Positive Scenarios: At least cover all core business processes
  • Exception Scenarios: Must include input validation, business rules, system exceptions, operation exceptions, etc.
  • Boundary Scenarios: Cover key boundary values and critical conditions
  • Security Scenarios: Identify potential security risk points
  • Performance Scenarios: Identify performance bottlenecks and concurrency risks
  • Compatibility Scenarios: Clearly define compatibility testing scope

4. Test Method Application Completeness ​

  • Design Method Application: Clearly define application scenarios and specific application descriptions for each test design method
  • Execution Method Planning: Clearly define strategies for manual testing, automated testing, interface testing, and performance testing
  • Reasonable Tool Selection: Recommend appropriate test tools based on test types
  • Method Coverage: Ensure comprehensive application coverage of test design methods

5. Scenario Design Professionalism ​

  • Clear Scenario Descriptions: Each scenario description is concise and clear, with emphasis on key points
  • Clear Test Focus: Clearly define key test points for each scenario
  • Reasonable Priority: Reasonably assign priorities based on business impact and risk
  • Design Method Annotation: Annotate the test design methods used
  • Risk Identification: Identify and assess potential risks

Execution Instructions ​

  1. Instruction Execution: Strictly follow instruction requirements for requirements analysis
  2. Context Analysis: Comprehensively analyze business, technical, and user contexts
  3. Input Data Evaluation: Systematically evaluate completeness and effectiveness of requirements documents
  4. Output Indicator Definition: Clearly define various evaluation indicators and standards
  5. Quality Assurance: Ensure professionalism and completeness of requirements analysis reports
  6. Format Standards: Strictly follow output format requirements to output requirements analysis reports

Note: Fully reflect all dimensions of the ICIO framework to ensure systematicity and professionalism of requirements analysis.

Please begin executing the above tasks immediately upon receiving the requirements document.