The move towards open-source reference designs for broadband customer-premises equipment (CPE) and Wi-Fi routers is quickly becoming the standard for many operators looking for interoperable, heterogeneous end-user connectivity devices. The Reference Design Kit for Broadband, commonly referred to as RDK-B, is an open-source software platform that provides a standardized approach and framework for powering various devices such as routers, modems, and gateways.
Repeatable, standardized testing is critical to the creation of a platform as powerful as RDK-B, and it is critical to anyone who is building solutions based on them. The RDK-B team employs CDRouter to validate the open-source implementation of RDK-B, underscoring the importance of rigorous and thorough testing in ensuring reliable broadband services. Here is a little bit about how RDK-B implementations can be tested with CDRouter and what to look at when building your automated test strategy for RDK-B based products.
RDK-B was initiated to address some of the inherent challenges in the rapidly evolving broadband ecosystem. With the multitude of broadband devices coming from different manufacturers, there was an acute need for standardization to ensure interoperability, quick deployment, and consistent user experiences. It’s currently maintained by a consortium of participating companies through the RDK Management, LLC.
These benefits don’t come lightly, and the RDK-B team’s automated test strategy for validating the solution during their agile development process is what makes the solution robust and trustworthy for operators to safely deploy.
RDK-B uses a test framework dubbed “Automatics” that incorporates a number of test processes and tools. QA Cafe’s CDRouter solution is integrated via the CDRouter API into the RDK-B team’s Automatics test framework. This integration streamlines the testing process, ensuring consistent and repeatable tests. The Automatics framework can start CDRouter test packages and read back the pass/fail results as part of the development pipeline.
The official CDRouter test cases used by the RDK-B team are built into CDRouter via an easy-to-use “test list” that lets users select the same tests used by RDK-B and incorporate them into their CDRouter test packages. This test list is a comprehensive set of feature and performance tests that exercise the most important functionality of your RDK-based products.
The RDK-B test lists we developed for CDRouter in partnership with the RDK-B development team to create a comprehensive set of test cases that can be used to replicate the same testing the RDK-B team uses to validate the open-source implementation. These tests cover:
In addition, RDK-B has an extensive custom data model for TR-069 and its successor, USP (TR-369) that is defined with vendor extensions. The RDK-B team runs CDRouter’s data model validation tests to exercise these features as well.
To optimally test RDK-B implementations, certain CDRouter expansions are essential:
For those looking to delve deeper into data model testing, the TR-069 or USP expansions are optional but recommended. These expansions, especially with the integration of the custom RDK-B TR-181 data model, provide an in-depth analysis ensuring robustness in real-world deployments.
If you are building RDK-B based products, whether or not you are using the Automatics framework for testing, CDRouter is built to validate your entire solution. Running the same tests used by the RDK-B team will help you validate your own implementation to ensure it will perform well in the field. Here’s some things you can do as part of your strategy:
For more information on testing your RDK-B based solution, check out our complete guide to building an automated test strategy!