How dekelund/gomate works
Main Components Identification
a) Compiler Package
• Feature Parser
• Definition Handler
• Code Generator
b) Unbrokenwing Package (Runtime/Execution)
• Test Driver
• Error Handler
• Type System
c) Internal Support Systems
• Highlighter (for pretty printing)
• Logging System
[Feature Files] → [Gomate Core] → [Generated Test Binary] → [Test Execution]
Component Relationships
a) Input Processing Flow:
• Feature files (.feature) → Compiler/Feature Parser
• Step Definition files (.go) → Compiler/Definition Handler
b) Compilation Flow:
• Parser outputs → Code Generator
• Generated Code → Go Compiler → Executable Binary
c) Execution Flow:
• Test Binary → Unbrokenwing Driver
• Driver → Test Results
Important Elements
• Blue: Input files and sources
• Green: Processing components
• Yellow: Generated artifacts
• Red: Error handling components
• Purple: Support systems
b) Component Types:
• Use rectangles for processing units
Specific Implementation Details
Key architectural elements:
• Feature file processing pipeline
• Step definition compilation process
• Test execution environment
• Logging and output formatting system
The support systems (logging, highlighting) as cross-cutting concerns
Key Relationships to Show:
• How the compiler package processes both feature files and step definitions
• How the unbrokenwing package provides the runtime environment
• How the logging system integrates across all components
• How the highlighter affects output presentation
Level of Detail:
• Keep main components visible at the top level
• Clear boundaries between compile-time and runtime components
• Integration points with the Go toolchain