You own your Test Cases
Vendors usually offer proprietary services based on vendor specific parameters that the TR-069 standard allows to define. If you are an Operator, you should take in mind which requirements the CPE needs to meet, and the Test Plan should be designed accordingly.
dBm069 allows you creating your own library designed according to your particular needs. You can create it on your own or you can request us to do this for you.
Test cases structure
Automatic test cases are defined in .xml files, and information is organized in three different blocks: TR-069 Sessions; Sequences; and Requirements.
A TR-069 session contains RPC methods, and it can contain more than one RPC method if wished.
A sequence is a section of the library that does not contain RPC methods, but complementary commands that dBm069 uses to complete a test plan. These complementary commands are called Actions, and dBm069 uses them for different purposes: to detect an Inform with a particular EventCode, to upload a FW from the PC to the server to set the environment for a test where it is necessary to download the file through TR-069, to open the http server, etc.
If the execution of an RPC method (in a TR-069 session) or an Action (in a sequence) has failed, or if the result of that execution has been different than expected, dBm069 generates an automatic failure message. However, dBm069 also allows to check more conditions that allow deciding if a test case has passed or not. This is the purpose of the Requirements block, where conditions that have not been possible to check during the test execution.