CDRouter Testlists
Testlists are a collection of tests chosen from different test modules that can be named and referenced within test packages to make it easy to add multiple tests with a single click. There are several pre-defined testlists available, and users may create additional testlists with their own custom sets of tests.
Testlists can be found on the Packages tab in CDRouter, and are indicated by an orange “testlist” icon.
User-defined Testlists
Users may define their own testlists by creating a new package on the packages tab and selecting the “Use As Testlist” checkbox.
See “How to Create and Run a Testlist” for detailed instructions on creating and managing user-defined testlists.
Predefined Testlists
CDRouter contains a set of predefined testlists. When configuring your first test package, we recommend starting with one of CDRouter’s predefined Testlists below. Each testlist contains a selection of fundamental test cases in specific categories. They provide a starting point to give you basic test coverage which you can then supplement with additional tests to attain more complete coverage as needed.
Note that predefined testlists must not be modified or customized. They are locked by default, and any changes made to them will be automatically overwritten whenever CDRouter is updated or reinstalled.
Instead, make a copy of a predefined testlist, which you can customize to suit your needs.
Top 100 Testlists
We recommend starting with these “Top 100” testlists if you are new to CDRouter or are testing a new device for the first time. Each testlist contains a broad variety of tests across multiple areas of functionality that most every CPE should be able to pass.
| Testlist Name | Description | Number of Tests | Required Expansions |
|---|---|---|---|
| CDRouter-Top-100 | Basic IPv4 functionality | 100 | CDRouter |
| CDRouter-IPv6-Top-100 | Basic IPv6 functionality | 100 | CDRouter, IPv6 |
Advanced Testlists
The Advanced Test Lists each contain a set of tests to provide additional coverage in specific areas. Each one is designed to verify specific areas of functionality within a CPE device. These advanced testlists compliment the Top 100 tests, and are intended to be a simple starting point that may be combined with different WAN modes, performance metrics, and configuration options to provide improved test coverage and increased confidence.
Note that additional configuration of both CDRouter and the device under test (DUT) may required in order successfully run some tests.
| Testlist Name | Description | Number of Tests | Required Expansions |
|---|---|---|---|
| CDRouter-Application | HTTP/HTTPS, SIP, DynDNS, UPnP tests | 288 | IPv6 |
| CDRouter-BBF069-Certification | Broadband Forum’s BBF.069 certification tests | 83 | BBF.069, TR-069 |
| CDRouter-DNS | DNS, DNS Proxy, DoH, DoT, DNS over TCP tests | 286 | IPv6 |
| CDRouter-DOCSIS | Cable Modem and eRouter interface tests | 101 | DOCSIS, IPv6 |
| CDRouter-IPv4-CPE | DHCP, DNS, firewall and NAT tests | 155 | CDRouter |
| CDRouter-IPv6-CPE | DHCPv6, DNS, and IPv6 Neighbor Discovery tests | 317 | IPv6 |
| CDRouter-Multicast | IGMP and MLD on LAN tests | 62 | IPv6, Performance |
| CDRouter-TR-069 | TR-069 basic functionality tests | 39 | TR-069 |
| CDRouter-Security | Firewall, scans, and vulnerabilities test | 205 | IPv6, Security, TR-069, DOCSIS |
| CDRouter-USP-Certification | Broadband Forum’s BBF.369 certification tests | 78 | USP |
| CDRouter-Wireless-AP | Scaling, DHCP, and guest network tests | 131 | IPv6, Multiport |
| RDK-Wireless-IPv4 | RDK IPv4 Wireless Test Cases | 346 | Multiport, Performance |
| RDK-Wireless-IPv6 | RDK IPv6 Wireless Test Cases | 277 | IPv6, Multiport |
| RDK-Ethernet-IPv4-IPv6 | RDK Ethernet IPv4/IPv6 Test Cases | 731 | IPv6, Multiport |
| RDK-Docsis-IPv6 | RDK Docsis IPv6 Test Cases | 24 | IPv6, Multiport |
Expected Results
The DUT may not pass all tests in any given testlist. Most devices should fail no more than 10 test cases when properly configured. A group of failures for a specific testlist feature indicates that the DUT may not support or may not be configured for that particular feature.
