Cursor rule

1---
2alwaysApply: false
3---
4 
5# Build and Test
6 
7**Purpose**: Build all units and execute comprehensive testing strategy
8 
9## Prerequisites
10- Code Generation must be complete for all units
11- All code artifacts must be generated
12- Project is ready for build and testing
13 
14---
15 
16## Step 1: Analyze Testing Requirements
17 
18Analyze the project to determine appropriate testing strategy:
19- **Unit tests**: Already generated per unit during code generation
20- **Integration tests**: Test interactions between units/services
21- **Performance tests**: Load, stress, and scalability testing
22- **End-to-end tests**: Complete user workflows
23- **Contract tests**: API contract validation between services
24- **Security tests**: Vulnerability scanning, penetration testing
25 
26---
27 
28## Step 2: Generate Build Instructions
29 
30Create `aidlc-docs/construction/build-and-test/build-instructions.md`:
31 
32```markdown
33# Build Instructions
34 
35## Prerequisites
36- **Build Tool**: [Tool name and version]
37- **Dependencies**: [List all required dependencies]
38- **Environment Variables**: [List required env vars]
39- **System Requirements**: [OS, memory, disk space]
40 
41## Build Steps
42 
43### 1. Install Dependencies
44\`\`\`bash
45[Command to install dependencies]
46# Example: npm install, mvn dependency:resolve, pip install -r requirements.txt
47\`\`\`
48 
49### 2. Configure Environment
50\`\`\`bash
51[Commands to set up environment]
52# Example: export variables, configure credentials
53\`\`\`
54 
55### 3. Build All Units
56\`\`\`bash
57[Command to build all units]
58# Example: mvn clean install, npm run build, brazil-build
59\`\`\`
60 
61### 4. Verify Build Success
62- **Expected Output**: [Describe successful build output]
63- **Build Artifacts**: [List generated artifacts and locations]
64- **Common Warnings**: [Note any acceptable warnings]
65 
66## Troubleshooting
67 
68### Build Fails with Dependency Errors
69- **Cause**: [Common causes]
70- **Solution**: [Step-by-step fix]
71 
72### Build Fails with Compilation Errors
73- **Cause**: [Common causes]
74- **Solution**: [Step-by-step fix]
75```
76 
77---
78 
79## Step 3: Generate Unit Test Execution Instructions
80 
81Create `aidlc-docs/construction/build-and-test/unit-test-instructions.md`:
82 
83```markdown
84# Unit Test Execution
85 
86## Run Unit Tests
87 
88### 1. Execute All Unit Tests
89\`\`\`bash
90[Command to run all unit tests]
91# Example: mvn test, npm test, pytest tests/unit
92\`\`\`
93 
94### 2. Review Test Results
95- **Expected**: [X] tests pass, 0 failures
96- **Test Coverage**: [Expected coverage percentage]
97- **Test Report Location**: [Path to test reports]
98 
99### 3. Fix Failing Tests
100If tests fail:
1011. Review test output in [location]
1022. Identify failing test cases
1033. Fix code issues
1044. Rerun tests until all pass
105```
106 
107---
108 
109## Step 4: Generate Integration Test Instructions
110 
111Create `aidlc-docs/construction/build-and-test/integration-test-instructions.md`:
112 
113```markdown
114# Integration Test Instructions
115 
116## Purpose
117Test interactions between units/services to ensure they work together correctly.
118 
119## Test Scenarios
120 
121### Scenario 1: [Unit A] → [Unit B] Integration
122- **Description**: [What is being tested]
123- **Setup**: [Required test environment setup]
124- **Test Steps**: [Step-by-step test execution]
125- **Expected Results**: [What should happen]
126- **Cleanup**: [How to clean up after test]
127 
128### Scenario 2: [Unit B] → [Unit C] Integration
129[Similar structure]
130 
131## Setup Integration Test Environment
132 
133### 1. Start Required Services
134\`\`\`bash
135[Commands to start services]
136# Example: docker-compose up, start test database
137\`\`\`
138 
139### 2. Configure Service Endpoints
140\`\`\`bash
141[Commands to configure endpoints]
142# Example: export API_URL=http://localhost:8080
143\`\`\`
144 
145## Run Integration Tests
146 
147### 1. Execute Integration Test Suite
148\`\`\`bash
149[Command to run integration tests]
150# Example: mvn integration-test, npm run test:integration
151\`\`\`
152 
153### 2. Verify Service Interactions
154- **Test Scenarios**: [List key integration test scenarios]
155- **Expected Results**: [Describe expected outcomes]
156- **Logs Location**: [Where to check logs]
157 
158### 3. Cleanup
159\`\`\`bash
160[Commands to clean up test environment]
161# Example: docker-compose down, stop test services
162\`\`\`
163```
164 
165---
166 
167## Step 5: Generate Performance Test Instructions (If Applicable)
168 
169Create `aidlc-docs/construction/build-and-test/performance-test-instructions.md`:
170 
171```markdown
172# Performance Test Instructions
173 
174## Purpose
175Validate system performance under load to ensure it meets requirements.
176 
177## Performance Requirements
178- **Response Time**: < [X]ms for [Y]% of requests
179- **Throughput**: [X] requests/second
180- **Concurrent Users**: Support [X] concurrent users
181- **Error Rate**: < [X]%
182 
183## Setup Performance Test Environment
184 
185### 1. Prepare Test Environment
186\`\`\`bash
187[Commands to set up performance testing]
188# Example: scale services, configure load balancers
189\`\`\`
190 
191### 2. Configure Test Parameters
192- **Test Duration**: [X] minutes
193- **Ramp-up Time**: [X] seconds
194- **Virtual Users**: [X] users
195 
196## Run Performance Tests
197 
198### 1. Execute Load Tests
199\`\`\`bash
200[Command to run load tests]
201# Example: jmeter -n -t test.jmx, k6 run script.js
202\`\`\`
203 
204### 2. Execute Stress Tests
205\`\`\`bash
206[Command to run stress tests]
207# Example: gradually increase load until failure
208\`\`\`
209 
210### 3. Analyze Performance Results
211- **Response Time**: [Actual vs Expected]
212- **Throughput**: [Actual vs Expected]
213- **Error Rate**: [Actual vs Expected]
214- **Bottlenecks**: [Identified bottlenecks]
215- **Results Location**: [Path to performance reports]
216 
217## Performance Optimization
218 
219If performance doesn't meet requirements:
2201. Identify bottlenecks from test results
2212. Optimize code/queries/configurations
2223. Rerun tests to validate improvements
223```
224 
225---
226 
227## Step 6: Generate Additional Test Instructions (As Needed)
228 
229Based on project requirements, generate additional test instruction files:
230 
231### Contract Tests (For Microservices)
232Create `aidlc-docs/construction/build-and-test/contract-test-instructions.md`:
233- API contract validation between services
234- Consumer-driven contract testing
235- Schema validation
236 
237### Security Tests
238Create `aidlc-docs/construction/build-and-test/security-test-instructions.md`:
239- Vulnerability scanning
240- Dependency security checks
241- Authentication/authorization testing
242- Input validation testing
243 
244### End-to-End Tests
245Create `aidlc-docs/construction/build-and-test/e2e-test-instructions.md`:
246- Complete user workflow testing
247- Cross-service scenarios
248- UI testing (if applicable)
249 
250---
251 
252## Step 7: Generate Test Summary
253 
254Create `aidlc-docs/construction/build-and-test/build-and-test-summary.md`:
255 
256```markdown
257# Build and Test Summary
258 
259## Build Status
260- **Build Tool**: [Tool name]
261- **Build Status**: [Success/Failed]
262- **Build Artifacts**: [List artifacts]
263- **Build Time**: [Duration]
264 
265## Test Execution Summary
266 
267### Unit Tests
268- **Total Tests**: [X]
269- **Passed**: [X]
270- **Failed**: [X]
271- **Coverage**: [X]%
272- **Status**: [Pass/Fail]
273 
274### Integration Tests
275- **Test Scenarios**: [X]
276- **Passed**: [X]
277- **Failed**: [X]
278- **Status**: [Pass/Fail]
279 
280### Performance Tests
281- **Response Time**: [Actual] (Target: [Expected])
282- **Throughput**: [Actual] (Target: [Expected])
283- **Error Rate**: [Actual] (Target: [Expected])
284- **Status**: [Pass/Fail]
285 
286### Additional Tests
287- **Contract Tests**: [Pass/Fail/N/A]
288- **Security Tests**: [Pass/Fail/N/A]
289- **E2E Tests**: [Pass/Fail/N/A]
290 
291## Overall Status
292- **Build**: [Success/Failed]
293- **All Tests**: [Pass/Fail]
294- **Ready for Operations**: [Yes/No]
295 
296## Next Steps
297[If all pass]: Ready to proceed to Operations phase for deployment planning
298[If failures]: Address failing tests and rebuild
299```
300 
301---
302 
303## Step 8: Update State Tracking
304 
305Update `aidlc-docs/aidlc-state.md`:
306- Mark Build and Test stage as complete
307- Update current status
308 
309---
310 
311## Step 9: Present Results to User
312 
313Present completion message in this structure:
314     1. **Completion Announcement** (mandatory): Always start with this:
315 
316```markdown
317# 🔨 Build and Test Complete
318```
319 
320     2. **AI Summary** (optional): Provide structured bullet-point summary of build and test results
321        - Format: "Build and test has completed with the following results:"
322        - List build status and artifacts
323        - List test results by category (unit, integration, performance, etc.)
324        - List generated instruction files
325        - DO NOT include workflow instructions ("please review", "let me know", "proceed to next phase", "before we proceed")
326        - Keep factual and content-focused
327     3. **Formatted Workflow Message** (mandatory): Always end with this exact format:
328 
329```markdown
330> **📋 <u>**REVIEW REQUIRED:**</u>**  
331> Please examine the build and test summary at: `aidlc-docs/construction/build-and-test/build-and-test-summary.md`
332 
333 
334 
335> **🚀 <u>**WHAT'S NEXT?**</u>**
336>
337> **You may:**
338>
339> 🔧 **Request Changes** - Ask for modifications to the build and test instructions based on your review
340> ✅ **Approve & Continue** - Approve build and test results and proceed to **Operations**
341 
342---
343```
344 
345---
346 
347## Step 10: Log Interaction
348 
349**MANDATORY**: Log the stage completion in `aidlc-docs/audit.md`:
350 
351```markdown
352## Build and Test Stage
353**Timestamp**: [ISO timestamp]
354**Build Status**: [Success/Failed]
355**Test Status**: [Pass/Fail]
356**Files Generated**:
357- build-instructions.md
358- unit-test-instructions.md
359- integration-test-instructions.md
360- performance-test-instructions.md
361- build-and-test-summary.md
362 
363---
364```
365