How krestenkrab/triq works
Main Components
a) Core Testing Engine Components:
• Property Generator (triq_dom.erl)
• Test Runner (triq.erl)
• Expression Evaluator (triq_expr.erl)
• State Machine Components (triq_statem.erl, triq_fsm.erl)
b) Application Infrastructure:
• Application Supervisor (triq_sup.erl)
• Application Controller (triq_app.erl)
c) Support Components:
• Auto-export Functionality (triq_autoexport.erl)
• Files/API Definitions (include/*.hrl)
[User Code/Tests] --> [Triq API Layer]
• v
• [Property Engine]
• ____________
• [Generators] [Test Runner]
• v v
• [Domain Types] [Evaluator]
• v v
• [State Machines/FSM Layer]
• v
• [Application Support]
• (OTP Supervision Tree)
Important Relationships to Highlight
a) Control Flow:
• How property definitions flow from user code through the API
• Test generation and execution pipeline
• Demonstrate the relationship between state machines and the core engine
b) Dependencies:
• OTP application structure
• How the supervision tree manages components
• Relationship between include files and implementation
Technical Details
• Erlang/OTP specific patterns (supervision, behaviors)
• Property definition syntax and flow
• Generator composition and domain types
• State machine and FSM integration points