RDK Resources
[*RDK Preferred*]
Code Management Facility
RDK Forums
[RDK Conferences]
RDK Support
Archives
Papers & Presentations Archive
Repository Name | Repository Path | Branch | Description |
---|---|---|---|
RDKB-Utils | rdk/tools/automatics/rdkb-test-utils | rdk-next | Holds RDKB Util APIs for execution. This test project is maven dependent on Automatics Core project and the JAR is deployed to repository and downloaded as a dependency from RDKB-Tests. |
RDKB-Tests | rdk/tools/automatics/rdkb-tests | rdk-next | Holds RDKB tests for execution. This is the project checkout by jenkins and executes tests in them. This test project is maven dependent on Automatics Core project via transitive dependency with Partner Java API implementation |
Table of Contents |
---|
To use Automatics system, partner has to provide implementation for Providers based API specification at Automatics API Specification.
There are two types of implementations required from partner.
...
Partner Java API
implementation
...
Maven project based on specification Automatics API Specification.
This project adds Automatics Core as maven dependency in its pom.xml and implements all Java based providers.
Partner implementation project is added as maven dependency in Automatics Generic Tests. Direct dependency to Automatics Core in Generic Tests project is
replaced with Partner implementation. This project is added as dependency in Generic Tests.
Only generic tests, use this project as maven dependency. This project will have only Java API implementation.
...
Partner REST API
implementation
...
REST api implementation based on specification Automatics API Specification. REST APIs are used by both Automatics orchestration and Automatics Core.
This project will have only REST based implementation.
...
. |