How chorus-bdd/chorus works
Main Components
a) Core Components:
• Parser
• Execution Engine
• Handler Manager
• Step Invoker
b) Extension Modules (arranged around core):
• Selenium Extension
• Spring Extension
• SQL Extension
• WebSockets Extension
c) Services Layer:
• Web Agent Service
• XML Service
• Mock Suite Service
Key Relationships
• Interpreter Core → Extension Modules (one-way dependency)
• Interpreter Core → Services Layer (one-way dependency)
• Extension Modules ↔ External Systems (bi-directional for remote testing)
Component Details
a) Interpreter Core:
• Interpreter Core |
• Feature Parser |
• Step Processor |
• Handler Manager |
• Context Manager |
• Config Manager |
b) Extension Modules:
• Extensions |
• Selenium |
• Spring |
• SQL |
• WebSockets |
c) Services:
• Services |
• Web Agent |
• XML |
• Mock Suite |
Integration Points
Connections for:
• Remote Step Execution
• JMX Communication
• WebSocket Connections
• Database Connections
Additional Elements
Include:
• Configuration Flow
• Test Execution Flow
• Remote Communication Channels
• Handler Registration Process
The service integration points
Keep the abstraction level high enough to show the main architectural components while including sufficient detail to understand the system's distributed testing capabilities.
This design reflects Chorus's unique ability to handle distributed testing scenarios while maintaining a clean separation between core functionality and extensions.