RDK Resources
[*RDK Preferred*]
Code Management Facility
RDK Forums
[RDK Conferences]
RDK Support
Archives
Papers & Presentations Archive
...
...
...
...
...
Hence, Automatics helps in faster release of RDK builds by validating builds using automated test execution. The results of test execution can be viewed from results page of Automatics.
Setup details will guide the user to setup Automatics system in their environment. It includes following details.
-DAutomatics -DhibernateUI.config.file = {path to hibernate config file} -DloggerUI.properties.file = {path to log properties file}
./startup.sh
...
The system configuration page has following parameters and partner has to configure values for their environment. The description of each parameter is provided below which helps to configure them.
...
System Config Param
...
Description
...
DEFAULT_SYNDICATION_PARTNER
...
Default syndication partner.
...
SYNDICATION_PARTNERS
...
Syndication partner names in comma separated format
...
DEVICE_INVENTORY_BASE_URL
...
Base URL which is having the rest implementation of device management
...
EXECUTION_ENVIRONMENT_TYPES
...
Execution environment types in comma separated format. Supported values are RDKV, RDKB
...
JUN
...
Jenkins Username
...
JUP
...
Jenkins Password
...
LDAP
...
LDAP Configuration values
...
Test_Types
...
Test Types supported by Automatics, QUICK, 1HOUR, 4HOUR, FAST_QUICK
...
EXECUTION_PRIORITY
...
Test cases will be executed based on the priority. Default provided values in comma separated format for execution priority are P0,P1,P2,P3
...
JOB_NAME_PREFIX
...
Prefix of the Jenkins job name. Default provided value is “GENERIC_RDKM_JOB”
...
RDK_PORTAL_AUTH
...
Authentication token to access the RDK portal
...
MINIMUM_FAIL_PERCENTAGE_TO_RETRY_TEST
...
The percentage limit to test retry the failed tests. Default provided value is 20
...
USER_DEFAULT_MODULES
...
Values of the default modules that can be accessed by the guest user. Default provided values separated by hyphen -3-5-6-8-9-13-
...
MASTER
...
Comma separated string keywords to identify a build name as master
...
SPRINT
...
Comma separated string keywords to identify a build name as sprint
...
STABLE
...
Comma separated string keywords to identify a build name as stable
...
CI_BUILD
...
Comma separated string keywords to identify a build name as CI build
...
TM_TYPE
...
Automatics deployment environment. Valid values DEV or PROD
...
HEAD_ENDS
...
Device head end values provided in comma separated format
...
SERVICE_CI_VERIFICATION_VALUE
...
Value for service CI_VERFICATION. Supported value CI_VERIFICATION.
...
SERVICE_FUNCTIONAL_VERIFICATION_VALUE
...
Value for service FUNCTIONAL_VERIFICATION. Supported value FUNCTIONAL _VERIFICATION.
...
REASON_TYPES
...
Reasons for adding/updating/deleting scripts added in comma separated format
Automatics Framework and Tools - Release V15.0 is available
Automatics Framework and Tools - Release V10.0 is available
Automatics RDK-B Test script Release V10.0is available
Page Tree | ||
---|---|---|
|
Resource Details
User can configure Jenkins details in resource details.
Device Group
Add the device groups available in device inventory. Automatics use device group to validate if user has permission to use devices from given device group.
Job Settings
User has to configure job settings for each test type. This is template used for creating corresponding job.
Source Code Repository
User can configure source repos of test project in Automatics. This is passed during Jenkins execution. Jenkins will clone the repo based on input from Automatics and execute the tests.
The following features should be accessible only for Admin.
...
Admin can upgrade the Automatics by going to Settings -> Upgrade Automatics
...
Admin can manage all the users of the Automatics. Go to Settings -> User Management.
Admin can Add/Delete the user details and groups. Also, manages the user group module access.
...