• Created by Unknown User (jdiana), last modified on Sept 25, 2018

Currently 4 Jenkins flow jobs are actively used for testing in accordance with each device (with exception to RPIB-E2E which will be discussed in a later section).

  • test-atf-start-flow-emub
  • test-atf-start-flow-rpib
  • test-atf-start-flow-rpiv
  • test-atf-start-flow-rpib-e2e


Parameters

ATF is designed to run with a minimal set of parameters to describe a test run. The table below describes each parameter and the options available.




Example values for various types of test runs
ParameterDescription
releasenightly/nightly-fullmaster
RUNTYPEtest run type
releasenightly or nightly-fullrelease or nightly or nightly-full

TMSVERSION

tms version as a TDK release number
latestlatest or 62(specific version)latest or 62(specific version)

UPGRADETMS

flag set to trigger tms upgrade
truetruetrue
PUBLISHRESULTSflag set to trigger publishing of generated reports
truetruetrue
TECHTYPEtechnology type (rdkb or rdkv)
rdkbrdkbrdkb
IMAGETYPEimage type (gateway or client)
gatewaygatewaygateway
DEVICETYPEhardware type (emu or rpi)
emuemuemu
IMAGEVERSIONversion of device image (in some cases matches jenkins build job number)
4329907
SETUPtesting setup (device or system or all)
devicedevicedevice
RELEASETAGrelease tag or nightly branch name or master
20180830nightly/20180925master
MASTERFLAGflag set to implicate master testing
falsefalsetrue



Phases

The test flow can be broken down into phases where each phase can be run as their own separate jobs as desired.

Prepare TMS

asdf

Prepare DUT

asdf

Prepare Test List

asdf

Run Tests

asdf

Generate Reports

asdf


  • No labels