JanviMl commited on
Commit
4bb06e6
·
verified ·
1 Parent(s): 44eab5b

Create prompts.yaml

Browse files
Files changed (1) hide show
  1. prompts.yaml +278 -0
prompts.yaml ADDED
@@ -0,0 +1,278 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ # STLC-AI Prompt Templates for Insurance QA Automation
2
+ # These templates guide the LLM to generate appropriate outputs for each stage
3
+
4
+ bdd_generation:
5
+ name: "BDD Scenario Generation"
6
+ description: "Convert user stories into comprehensive Gherkin BDD scenarios"
7
+ template: |
8
+ You are an expert QA engineer specializing in insurance domain testing. Convert the following user story into a comprehensive Gherkin BDD scenario.
9
+
10
+ User Story: {user_story}
11
+
12
+ Requirements:
13
+ 1. Create realistic BDD scenarios for insurance billing/payment domain
14
+ 2. Include multiple scenarios covering happy path and edge cases
15
+ 3. Use proper Gherkin syntax (Feature, Scenario, Given, When, Then)
16
+ 4. Include specific insurance domain terminology
17
+ 5. Add data examples where relevant
18
+ 6. Consider validation rules and error handling
19
+ 7. Make scenarios testable and specific
20
+
21
+ Format your response as:
22
+ ```gherkin
23
+ Feature: [Feature Name]
24
+ [Feature Description]
25
+
26
+ Scenario: [Scenario Name]
27
+ Given [precondition]
28
+ When [action]
29
+ Then [expected result]
30
+ And [additional verification]
31
+
32
+ Scenario: [Edge Case Scenario]
33
+ Given [edge case setup]
34
+ When [edge case action]
35
+ Then [edge case result]
36
+ ```
37
+
38
+ Focus on insurance-specific validations like:
39
+ - Policy validation and status checks
40
+ - Premium calculations and billing cycles
41
+ - Payment processing and fraud detection
42
+ - Customer notification requirements
43
+ - Regulatory compliance checks
44
+
45
+ test_script_generation:
46
+ name: "Python Test Script Generation"
47
+ description: "Convert BDD scenarios into executable Python pytest scripts"
48
+ template: |
49
+ You are a senior test automation engineer. Convert the following BDD scenario into a comprehensive Python pytest test script.
50
+
51
+ BDD Scenario:
52
+ {bdd_scenario}
53
+
54
+ Story Context: {story_title}
55
+
56
+ Requirements:
57
+ 1. Create a complete pytest test class with proper structure
58
+ 2. Include setup and teardown methods
59
+ 3. Write realistic test methods that match the BDD steps
60
+ 4. Use appropriate mocking for external dependencies
61
+ 5. Include proper assertions and error handling
62
+ 6. Add comprehensive comments explaining test logic
63
+ 7. Follow pytest best practices and naming conventions
64
+ 8. Include both positive and negative test cases
65
+
66
+ Generate Python code with:
67
+ - Import statements for required libraries (pytest, unittest.mock, etc.)
68
+ - Test class with descriptive name
69
+ - setup_method() for test preparation
70
+ - Individual test methods for each scenario
71
+ - Mock objects for external services (payment gateways, databases, email services)
72
+ - Realistic test data and assertions
73
+ - Error handling and edge case testing
74
+
75
+ Focus on insurance domain specifics:
76
+ - Policy management systems
77
+ - Billing and payment processing
78
+ - Customer communication systems
79
+ - Regulatory compliance validation
80
+ - Data security and privacy checks
81
+
82
+ defect_summary:
83
+ name: "Intelligent Defect Report Generation"
84
+ description: "Analyze test failures and generate comprehensive defect reports"
85
+ template: |
86
+ You are an experienced QA analyst specializing in defect analysis. Analyze the test failure and create a professional defect report.
87
+
88
+ BDD Scenario:
89
+ {bdd_scenario}
90
+
91
+ Test Failure Log:
92
+ {failure_log}
93
+
94
+ Generate a comprehensive defect report with:
95
+
96
+ **Defect Title:** [Clear, specific title]
97
+ **Severity:** [Critical/High/Medium/Low]
98
+ **Priority:** [P0/P1/P2/P3]
99
+ **Component:** [System component affected]
100
+
101
+ **Description:**
102
+ [Clear description of the defect and its impact]
103
+
104
+ **Steps to Reproduce:**
105
+ 1. [Step 1]
106
+ 2. [Step 2]
107
+ 3. [Step 3]
108
+
109
+ **Expected Behavior:**
110
+ [What should happen]
111
+
112
+ **Actual Behavior:**
113
+ [What actually happened]
114
+
115
+ **Root Cause Analysis:**
116
+ [Technical analysis of why the defect occurred]
117
+
118
+ **Suggested Fix:**
119
+ [Recommended solution approach]
120
+
121
+ **Impact Assessment:**
122
+ - Business Impact: [High/Medium/Low]
123
+ - Customer Impact: [Description]
124
+ - Security Impact: [If applicable]
125
+ - Compliance Impact: [Regulatory considerations]
126
+
127
+ **Test Evidence:**
128
+ [Key evidence from logs and test execution]
129
+
130
+ Consider insurance domain factors:
131
+ - Customer satisfaction and trust
132
+ - Regulatory compliance (PCI DSS, GDPR, etc.)
133
+ - Financial impact and risk
134
+ - Data security and privacy
135
+ - Business continuity requirements
136
+
137
+ test_data_generation:
138
+ name: "Test Data Generation"
139
+ description: "Generate realistic test data for insurance domain testing"
140
+ template: |
141
+ Generate realistic test data for insurance domain testing based on the following scenario:
142
+
143
+ Scenario: {scenario_description}
144
+ Data Type: {data_type}
145
+
146
+ Create test data that includes:
147
+ 1. Valid data sets for positive testing
148
+ 2. Invalid data sets for negative testing
149
+ 3. Edge cases and boundary values
150
+ 4. Realistic insurance domain values
151
+
152
+ Format as JSON with clear labeling:
153
+ ```json
154
+ {
155
+ "valid_data": [...],
156
+ "invalid_data": [...],
157
+ "edge_cases": [...]
158
+ }
159
+ ```
160
+
161
+ coverage_analysis:
162
+ name: "Test Coverage Analysis"
163
+ description: "Analyze test coverage and suggest improvements"
164
+ template: |
165
+ Analyze the test coverage for the following insurance system component:
166
+
167
+ Component: {component_name}
168
+ Current Tests: {existing_tests}
169
+ Business Requirements: {requirements}
170
+
171
+ Provide analysis including:
172
+ 1. Current coverage assessment
173
+ 2. Missing test scenarios
174
+ 3. Risk areas not covered
175
+ 4. Recommended additional tests
176
+ 5. Priority ranking for new tests
177
+
178
+ Focus on insurance-specific coverage areas:
179
+ - Regulatory compliance testing
180
+ - Security and fraud prevention
181
+ - Customer data protection
182
+ - Financial accuracy validation
183
+ - Business rule enforcement
184
+
185
+ performance_testing:
186
+ name: "Performance Test Generation"
187
+ description: "Generate performance testing scenarios for insurance systems"
188
+ template: |
189
+ Create performance testing scenarios for the insurance system component:
190
+
191
+ System: {system_component}
192
+ User Story: {user_story}
193
+ Expected Load: {load_requirements}
194
+
195
+ Generate performance test scenarios covering:
196
+ 1. Load testing (normal usage)
197
+ 2. Stress testing (peak usage)
198
+ 3. Volume testing (large data sets)
199
+ 4. Endurance testing (extended periods)
200
+ 5. Scalability testing (growth scenarios)
201
+
202
+ Include specific metrics for insurance systems:
203
+ - Payment processing response times
204
+ - Policy issuance speed
205
+ - Claims processing throughput
206
+ - Customer portal responsiveness
207
+ - Regulatory reporting generation time
208
+
209
+ security_testing:
210
+ name: "Security Test Scenario Generation"
211
+ description: "Generate security testing scenarios for insurance applications"
212
+ template: |
213
+ Create security testing scenarios for the insurance application:
214
+
215
+ Component: {component_name}
216
+ User Story: {user_story}
217
+ Security Requirements: {security_requirements}
218
+
219
+ Generate security test scenarios for:
220
+ 1. Authentication and authorization
221
+ 2. Data encryption and protection
222
+ 3. Input validation and sanitization
223
+ 4. Session management
224
+ 5. API security
225
+ 6. Database security
226
+
227
+ Focus on insurance-specific security concerns:
228
+ - PCI DSS compliance for payment data
229
+ - Personal data protection (GDPR/CCPA)
230
+ - Financial fraud prevention
231
+ - Customer identity verification
232
+ - Regulatory audit requirements
233
+
234
+ # Configuration settings for prompt usage
235
+ settings:
236
+ max_tokens: 2000
237
+ temperature: 0.7
238
+ model_preference: "gpt-4"
239
+ fallback_model: "gpt-3.5-turbo"
240
+ timeout_seconds: 30
241
+ retry_attempts: 3
242
+
243
+ # Domain-specific keywords for context enhancement
244
+ insurance_keywords:
245
+ billing:
246
+ - premium
247
+ - invoice
248
+ - payment
249
+ - billing cycle
250
+ - due date
251
+ - late fees
252
+ - payment methods
253
+
254
+ policy:
255
+ - policyholder
256
+ - coverage
257
+ - deductible
258
+ - benefits
259
+ - exclusions
260
+ - renewal
261
+ - cancellation
262
+
263
+ claims:
264
+ - claim processing
265
+ - adjuster
266
+ - settlement
267
+ - investigation
268
+ - approval
269
+ - denial
270
+ - fraud detection
271
+
272
+ compliance:
273
+ - regulatory requirements
274
+ - audit trail
275
+ - data retention
276
+ - privacy protection
277
+ - financial reporting
278
+ - risk assessment