How devenjarvis/sundew works
Main Components
a) Core Framework Components (Primary Layer):
• Test Runner Module
• Test Writer Module
• Graph Module (for dependency management)
• Side Effects Handler
• Configuration System
b) Integration Layer:
• CLI Interface
• Example Integrations
• Test Generation System
┌─ Framework Core Layer ─────────────────────┐
• ┌─────────┐ ┌─────────┐ ┌─────────┐ │
• Graph │──│ Test │ │ Side │ │
• Module │ │ Runner │ │ Effects │ │
• ┘ └─────────┘ └─────────┘ │
• ┼─────────────┘ │
• ┌─────────┐ │
• Test │ │
• Writer │ │
• ┘ │
• ┬───────────────────────┘
┌───────────────────┼───────────────────────┐
• Integration Layer │
• ┌─────────┐ ┌─────────┐ ┌─────────┐ │
• CLI │ │ Example │ │ Test │ │
• Interface│ │ Projects│ │Generator│ │
• ┘ └─────────┘ └─────────┘ │
• ┘
Key Elements to Highlight
• Core Components: Blue
• Integration Layer: Green
• External Interfaces: Orange
b) Component Relationships:
• Bidirectional communication between Graph Module and Test Runner
• How Side Effects Handler integrates with Test Runner
• Demonstrate Test Writer's relationship with other components
Important Details
a) File Organization:
• How the sundew/ directory structure maps to components
• Where example integrations (boto3, fastapi, etc.) connect
b) Testing Flow:
• How test generation works
• Path from test writing to execution
Technical Specifications
A section showing supported integrations:
• FastAPI
• Boto3
• Async Support
• Simple Examples
Implementation Notes
• Version control and CI/CD workflow connections
• Documentation system integration
Specific Recommendations
• Center on the core testing framework components
• Clear separation between framework and examples
• Novel testing approach mentioned in README
• CI/CD pipeline integration
Remember to:
• Notes about the experimental nature of the project
• Clear extension points for future development