'; Device Compliance Test Suites | Incognito Help
Array
(
    [0] => Array
        (
            [version] => 4.3
            [language] => en
        )

    [1] => Array
        (
            [version] => 4.2
            [language] => en
        )

    [2] => Array
        (
            [version] => 4.1
            [language] => en
        )

    [3] => Array
        (
            [version] => 4.0
            [language] => en
        )

    [4] => Array
        (
            [version] => 3.5
            [language] => en
        )

    [5] => Array
        (
            [version] => 3.4
            [language] => en
        )

    [6] => Array
        (
            [version] => 4.2
            [language] => fr
        )

    [7] => Array
        (
            [version] => 4.2
            [language] => es
        )

)
Rel: acs/topics/acs/dita/device_compliance_test_suites
URI: acs/topics/device_compliance_test_suites
=== Tags ===
Array
(
    [920] => device compliance test suites
)

=== Related ===
Array
(
)

Device Compliance Test Suites

This feature enables you to verify that devices and firmware versions support the critical functions necessary for successful deployment on your network. By standardizing your operator-level certification tests, and eliminating repetitive tasks, you can minimize the amount of time needed for certification testing. This is a separately licensed feature, available from ACS 3.4+, which may not be included in your deployment solution. For more information, contact Incognito.

For details on creating device compliance test suites, see the tutorial Device Compliance Test Suites.

Operator-level certification can include tests to verify:
  • Required RPC calls function
  • Device bootstrap event does not return an error
  • Device supports SSL or TLS security
  • Data Model (TR-098 or TR-181)
  • Default discovery algorithm returns a complete list of supported parameters, and if not, tests are performed to select the best discovery algorithm
  • Device is compliant to TR-143 and diagnostics such as ping, traceroute, upload, download function as expected
  • Support for parameters related to specific features, such as STUN and XMPP
  • Objects are available for the services you are offering, such as parental controls or triple play (data, voice, and video)

Device Compliance Test Suite Details

In a test suite, each test covers one verification. You can create separate suites to organize your tests by functional grouping or by device type, such as LTE or GPON.

For example you might create a suite for:
  • Base TR-069 tests
  • LTE tests
  • GPON tests
  • VIP Client tests
  • Triple Play Device tests

The service provides some out-of-the-box tests that you can import from the Incognito Repository or you can write your own. To do this you can use the GUI or write tests outside of ACS and import them into the service (XML format). To view an example of how to write your own test suite, you can export an out-of-the-box script. Incognito Professional Services can also create compliance tests customized to your requirements. For further information please visit the services page at incognito.com/services.

Use these settings to create and manage device compliance tests.

To do this: Follow these steps:
Create a test suite Click the add symbol ().
Delete a test suite and all of its tests Click the delete symbol (X) next to a test suite.
Import your own test suite Click Import and select Local File.
Import a test suite from the Incognito repository Click Import and select Remote File.
Export a test suite (XML format) to a zip file Select a test, and click Export.
Select a test suite From the TEST SUITES list, click a test.
Customize tests in a test suite Use the add () and remove (X) controls.
Modify test settings Click Edit.
Run compliance tests Navigate to Devices > View Device > Device Hub > Run Compliance Test Suite.
Go back one screen Click the back symbol ().
Return to the main screen of the service Click the hub symbol ().
Test Suite Setup Logic that is executed, once, before the first test begins. Use it to initialize the test, or to provision necessary parameters on the device, such as the connection request username and password. The setup method does not pass or fail, but exceptions thrown at this stage prevent execution of the test suite.
Test Suite Teardown Logic that is executed after the last test finishes.
Top