RDK Resources
[*RDK Preferred*]
Code Management Facility
RDK Forums
[RDK Conferences]
RDK Support
Archives
Papers & Presentations Archive
...
Repository Name | Repository Path | Branch | Description |
---|---|---|---|
Automatics Orchestration | rdk/tools/automatics | rdk-next | Standalone UI based tool which helps user to trigger executions and view results |
Automatics Core | rdk/tools/automatics/automatics-core | rdk-next | Main component of Automatics system that manages test execution. This project is executed in jenkins. |
Automatics Properties | rdk/tools/automatics/automatics-props | rdk-next | Standalone UI based tool where user can configure urls and other data required for test execution For eg: Base url for REST implementation by partner will be configured in this tool which is used by Automatics orchestration and Automatics core. |
Automatics Generic Tests | rdk/tools/automatics/generic-automation-tests | rdk-next | Holds generic 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. |
...
Project | Repository | Description |
---|---|---|
Partner Java API implementation | Partner repository | 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. |
Partner REST API implementation | Partner repository | REST api implementation based on specification Automatics API Specification. REST APIs are used by both Automatics orchestration and Automatics Core. |
...