48dfa915c7
Phase 2: Hooks System - Event-driven execution with HookEvent/HookAction types - HookManager for registration and execution Phase 3: Multi-Agent Workflow - Workflow orchestration with dependency graphs - WorkflowStep with conditions and retry support Phase 4: MCP (Model Context Protocol) Support - McpServer for external tool servers - McpManager for multiple server management Also includes core modules: cache, error_policy, feature_flags, git, logger, plugin, retry, rules 662 tests passing 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
33 lines
778 B
Markdown
33 lines
778 B
Markdown
# Test Generation
|
|
|
|
Generate comprehensive tests for the specified code:
|
|
|
|
## Test Types
|
|
1. **Unit Tests** - Test individual functions in isolation
|
|
2. **Integration Tests** - Test component interactions
|
|
3. **Edge Cases** - Boundary conditions, empty inputs, max values
|
|
4. **Error Cases** - Invalid inputs, failure scenarios
|
|
|
|
## Requirements
|
|
- Use the project's testing framework
|
|
- Follow Arrange-Act-Assert pattern
|
|
- Descriptive test names that explain the scenario
|
|
- Mock external dependencies
|
|
- Aim for high coverage of critical paths
|
|
|
|
## Output Format
|
|
```rust
|
|
#[cfg(test)]
|
|
mod tests {
|
|
use super::*;
|
|
|
|
#[test]
|
|
fn test_function_name_scenario() {
|
|
// Arrange
|
|
// Act
|
|
// Assert
|
|
}
|
|
}
|
|
```
|
|
|
|
Include explanation of test strategy and coverage goals.
|