Goal
Summary
Extend python_raft under framework/core to support additional controller/module abstractions required for broader device interaction and automation coverage.
Background
python_raft is a modular, config-driven low-level testing framework. To improve hardware and platform test coverage, we need to expand the supported components in framework/core so they can be used consistently by RAFT-based tests.
Proposed additions
Add support for the following under framework/core:
HdmiController -> Review HDMI Analyzer PR and get backNetworkModule -> explore ut-raft for real device for sending network packetSwitchController (Front Panel)-> need more discussion/right equipmentsMotionGeneratorController -> need to identify equipmentVoiceGeneratorController -> need more discussions
Goals
- Define clear core abstractions/interfaces for each controller/module
- Ensure implementations fit the existing modular RAFT architecture
- Allow configuration-driven initialization and usage
- Make the new components reusable across test suites
- Keep naming, structure, and patterns aligned with existing
framework/core design
Scope of work
- Review current
framework/core structure and extension points
- Add new controller/module base classes or integrations where appropriate
- Introduce config support for the new components
- Add example usage or documentation for each supported module
- Add/extend unit tests where applicable
Expected outcome
RAFT can initialize and use these additional controllers/modules through the core framework, enabling future engineering tests to interact with HDMI, network, remote inputs, switching, HDMI-CEC, motion generation, and voice generation capabilities in a standardized way.
Acceptance criteria
framework/core includes support for:
HdmiControllerNetworkModuleSwitchControllerMotionGeneratorControllerVoiceGeneratorController
- Configuration model supports enabling and initializing these components
- New APIs/classes follow existing RAFT architectural conventions
- Basic documentation/examples are added
- Tests are added or updated for the new functionality
Notes
Please align implementation with the current structure under:
framework/core
Reference:
https://github.com/rdkcentral/python_raft/tree/develop/framework/core
Notes (Optional)
No response
Goal
Summary
Extend
python_raftunderframework/coreto support additional controller/module abstractions required for broader device interaction and automation coverage.Background
python_raftis a modular, config-driven low-level testing framework. To improve hardware and platform test coverage, we need to expand the supported components inframework/coreso they can be used consistently by RAFT-based tests.Proposed additions
Add support for the following under
framework/core:HdmiController-> Review HDMI Analyzer PR and get backNetworkModule-> explore ut-raft for real device for sending network packetSwitchController(Front Panel)-> need more discussion/right equipmentsMotionGeneratorController-> need to identify equipmentVoiceGeneratorController-> need more discussionsGoals
framework/coredesignScope of work
framework/corestructure and extension pointsExpected outcome
RAFT can initialize and use these additional controllers/modules through the core framework, enabling future engineering tests to interact with HDMI, network, remote inputs, switching, HDMI-CEC, motion generation, and voice generation capabilities in a standardized way.
Acceptance criteria
framework/coreincludes support for:HdmiControllerNetworkModuleSwitchControllerMotionGeneratorControllerVoiceGeneratorControllerNotes
Please align implementation with the current structure under:
framework/coreReference:
https://github.com/rdkcentral/python_raft/tree/develop/framework/core
Notes (Optional)
No response