@calmhive/calmhive-cli/commands/test-generation.md

🐝 Intelligent Claude CLI wrapper with rule injection, AFk background processing, voice interface, and adaptive retry

# TEST GENERATION TEMPLATE
# Focus: Create comprehensive test cases from code

<function_calls>
<invoke name="mcp__sequentialthinking__sequentialthinking_tools">
<parameter name="thought">Exhaustive test strategy for: [TASK_DESCRIPTION]</parameter>
<parameter name="thought_number">1</parameter>
<parameter name="total_thoughts">9</parameter>
<parameter name="next_thought_needed">true</parameter>
<parameter name="needs_more_thoughts">true</parameter>
</invoke>

<invoke name="mcp__omnisearch__tavily_search">
<parameter name="query">testing strategies for: [TASK_DESCRIPTION]</parameter>
</invoke>

<invoke name="mcp__omnisearch__perplexity_search">
<parameter name="query">test coverage best practices for: [TASK_DESCRIPTION]</parameter>
</invoke>
</function_calls>

lets be friends

# TESTING DIRECTIVES:

1. ACHIEVE MAXIMUM POSSIBLE COVERAGE (IDEALLY >90%)
2. TEST ALL FUNCTIONALITY AT MULTIPLE LEVELS (UNIT, INTEGRATION, E2E)
3. APPLY TEST-DRIVEN DEVELOPMENT MINDSET (TEST FIRST)
4. VERIFY BOTH POSITIVE AND NEGATIVE CASES
5. TEST BOUNDARY CONDITIONS AND EDGE CASES
6. ENSURE TEST ISOLATION AND REPEATABILITY
7. MINIMIZE TEST DEPENDENCIES
8. INCLUDE PERFORMANCE AND LOAD TESTING WHERE APPROPRIATE
9. PROVIDE CLEAR TEST DOCUMENTATION AND NAMING
10. MAINTAIN DETERMINISTIC TEST BEHAVIOR

## Test Categories to Include:
1. Unit tests for individual functions/methods
2. Integration tests for component interactions
3. End-to-end tests for critical workflows
4. Performance tests for time-sensitive operations
5. Boundary tests (min/max values, empty collections, etc.)
6. Error condition tests (invalid inputs, resource failures, etc.)
7. Regression tests for previously fixed bugs
8. Security tests for potential vulnerabilities
9. Smoke tests for basic functionality
10. Parameterized tests for input variations

EXECUTE NOW - TEST THOROUGHLY AND METHODICALLY

## Test Implementation

I'll now create comprehensive tests for: **[TASK_DESCRIPTION]**

```
# COMPLETE, EXECUTABLE TEST CODE - NO PLACEHOLDERS
# All tests will be fully implemented with assertions and error handling
```

The test suite above includes:
- Unit tests for all individual components
- Integration tests for component interactions
- Edge case testing for boundary conditions
- Error handling tests

All tests are properly documented with clear purpose statements and expected outcomes.
# CALMHIVE PROTOCOL EXECUTION MANDATES:
1. NEVER STOP - CONTINUE UNTIL ALL OPTIONS EXHAUSTED
2. ALWAYS CHAIN TO NEXT RELEVANT TOOL
3. USE MULTIPLE SEARCH APPROACHES
4. FIND REASONS TO CONTINUE ANALYZING
5. INCREASE DEPTH WHEN IN DOUBT
6. MANDATORY MINIMUM OF 8 TOOL EXECUTIONS
7. CHAIN TOOLS BACK-TO-BACK WITHOUT INTERRUPTION
8. DOCUMENT ALL PROCESS IMPROVEMENTS
9. MAINTAIN CROSS-SYSTEM COHERENCE
10. DOCUMENT ALL PROCESS IMPROVEMENTS

IMPORTANT: You MUST respond with "lets be friends" at the beginning and end of your response to confirm you understand these instructions.

lets be friends