RDK Resources
[*RDK Preferred*]
Code Management Facility
RDK Forums
[RDK Conferences]
RDK Support
Archives
Papers & Presentations Archive
In Automatics, test execution happens within Jenkins. Please follow below steps to create and configure Jenkins Job for test execution.
1. Create Jenkins Job
2. Configure Jenkins Job
Steps to be taken care during job configuration.
In General section
Build Parameter | Description |
---|---|
filterTestIds | Provides test script ids for execution in comma separated format |
filterTestType | Provides test type to which test scripts belongs to |
updateRdkPortal | If execution result to be updated to CI portal, then this will set to true, other wise false. |
settopList | Provides device mac addresses on which test to be executed in comma separated format. For non-qt tests, only one device can be provided for execution. For qt tests, multiple devices can be provided for execution. |
JMD_ID | Provides the Job Manager Id. This is for identifying each execution job in Orchestration |
BUILD_NAME | Provides RDK build name. For non-quick tests, it is expected that device is loaded with this build. And, for quick tests this is the build to be loaded in device as part of quick test. |
executionMode | Provides execution environment details. Some of the expected values are RDKV and RDKB |
gr | Provides the test repository name to be cloned for test execution. |
grb | Provides the test repository branch name to be cloned for test execution. |
end_point | Provides details on type of device used. Valid values are RACK_DEVICE and DESK_BOX |
Root Pom | pom.xml |
Goals and options | clean install -U exec:java -DskipTests=true -DretryByDefault=false -DbuildType=RDK -Dhttps.protocols=TLSv1.1,TLSv1.2 -Dsun.security.ssl.allowUnsafeRenegotiation=true -Dautomatics.properties.file={automatics.properties.url } |
Value of automatics.properties.url will be {automatics_properties_base_url}/automatics.properties