Skip to content

Framework Usage

Overview

This details the requirements for generating and building testing suites for the RDK-E Project for the vendor layer

A document outlining the tests for external interfaces will be created. This document will detail how to use the python_raft infrastructure to test the following:

  • Selecting testing suite requirements from the platform-specific deviceSettings.yaml.
  • Defining module-specific options for downloading assets required for testing.
  • Building the necessary components for testing.
  • Utilizing sc docker to access the toolchain.
  • Tests should be designed to be platform independent, and driven by yaml configuration / profiles (see example: https://github.com/rdk-e/hal/wiki/Validation-Profiles).

The module must be build-able and testable using the specified methods. A phased delivery model with collaboration between Tata and Sky teams is required.

It should be noted that Vendor Layer testing is Black Box Testing.

Levels of Test

The levels of test to be implemented are defined here:

https://github.com/rdkcentral/ut-core/wiki/3.-Standards:-Levels-of-Test-for-Vendor-Layer

Testing Frameworks:

See also FAQ:-UT-Core-Framework-Overview

Phased Delivery:

The team will follow the phased delivery which defines git tasks and review checkpoints.

See also 3.2.1: Standards: Phased Delivery with Checkpoints