+ + + + + titleValue + + + + + titleValue + + + + Title commmand requires test title as an argument + + +The title keyword is used to give a verbal description for a test case. + + + + + + + timeoutValue + + + + Timeout keyword should have a timeout value as an argument + + +Timeout is used to give a timeout value for a test case. +Timeout value is passed in milliseconds. + + + + + + + + normal + + + priorityValue + + + high + + + + low + + + + + "priority" keyword should have a priority value as an argument + + +Priority is used to give a priority for a test case. +Priority value either as an integer or as the string high, normal or low. + + + + + + + TestObjectName + + + + + yes + + + + "print" keyword has invalid argument + + +The print keyword can be used to print, for example, progress information to UI. + + + + + + + "canceliferror" keyword takes no arguments + + +The canceliferror keyword is used to cancel the execution of the remaining test cases if one of the executed test cases has failed. +This keyword is normally used to stop the test case execution when some of the test cases are long running. + + + + + + + pausecombinerValue + + + + "pausecombiner" keyword takes number of miliseconds as an argument" + + +The pausecombiner keyword is used to pause test combiner for a specified time + +Arguments: +Timeout: The timeout for the pause, specified in milliseconds. + + + + + + + + testmodule + + + configfile + + + TestCaseNumber + + + + + expect + + + testid + + + ini + + + category + + + timeout + + + title + + + + "run" keyword takes test module name, configuration file and test case number as argumets + + +The run keyword is used to start a specified test case. It has several mandatory and optional arguments. + +Arguments: +testmodule: The test module name. +configfile: The test case configuration file. +Test case number: The test case number to be executed from configfile. + +expect: The expected result (0 = KErrNone). +testid: Test case identification, which is used by other keywords to identify the test case (). +ini: The initialization file for test module (). +category: The result category; either normal, leave, panic, exception or timeout. +timeout: Test case timeout (not supported yet). +title: Test case title. + + + + + + + + testid + + + + "cancel" keyword takes test an identification of a test case as an argument + + +The cancel keyword is used to cancel a started test case. +The test case is cancelled by immediately killing the thread that executes the test case. + +Arguments: +testid: The test ID from the run command. + + + + + + + + testid + + + + + time + + + + "cancel" keyword takes test an identification of a test case as an argument and optonal argument: number of miliseconds + + +The pause keyword is used to pause a test case. +The test case is paused by pausing the thread that executes the test case. + +Arguments: +testid: The test ID from the run command. +Time Pause time in milliseconds. After this time, resume is called automatically. + + + + + + + + testid + + + + "resume" keyword takes an identification of a test case as an argument + + +The resume keyword is used to resume a paused test case. + +Arguments: +testid: The test ID from the run command. + + + + + + + testid + + + + "complete" keyword takes an identification of a test case as an argument + + +The complete keyword is used to have a started test case wait to complete. +It blocks until the test case has finished. + +Arguments: +testid: The test ID from the run command. + + + + + + + + start + + + stop + + + + + measurementplugin01 + + + measurementplugin02 + + + measurementplugin03 + + + measurementplugin04 + + + measurementplugin05 + + + stifbappeaprofiler + + + + + + STIF Test measurement parameters + + + + + "testmeasurement" keyword must be follwed by a command, type and optionaly parameters + + +The testmeasurement keyword is used for test measurement testing. + +Arguments: +STIF Test measurement command: Command for STIF Test Measurement control. +The supported values are: "start" for starting test measurement and "stop" for stopping test measurement. It also releases all allocated resources. +STIF Test measurement type: Test measurement type. +The supported values are: measurementplugin01, measurementplugin02, measurementplugin03, measurementplugin04, measurementplugin05, bappeaprofiler +STIF Test measurement parameters: Optional. Test measurement module configuring etc. user and test measurement module specific. This is returned as a descriptor to the test measurement module in start operation. + + + + + + + + loopTimes + + + + + + msec + + + passlimit + + + + + "loop" keyword must be followed by the loop count, optionaly the "msec" word, optional "passlimit" word and passlimit value + + +The loop keyword is used to repeat a section of the test case file for the specified number of iterations. +The section to be repeated is enclosed with the loop and endloop keywords. +Nested loops are not supported. + +Arguments: +Loop times: The loop count, that is, the number of times that the loop is executed. + +msec: This keyword says that ‘Loop times’ argument stands for the time in milliseconds during which loop will be looped +passlimit: This keyword turns on passlimit (endurance) feature +Passlimit value: Says how many iteration must pass to let pass the whole loop + + + + + + "endloop" takes no arguments + + +The endloop keyword is used to specify the end of a looped section. + + + + + + + Event + + + + "request" keyword must be follwed by an event name + + +The request keyword is used to request an event. +If someone wants to use an event, it must first be requested and after that it can be waited. +After the event is not used anymore, it must be released. + +Arguments: +Event: The event name. + + + + + + + Event + + + + "wait" keyword must be follwed by an event name + + +The wait keyword is used to wait an event. +Request must be called before wait, and wait blocks until the requested event is set. +Wait may proceed immediately if the requested event is a state event and already pending + +Arguments: +Event: The event name. + + + + + + + Event + + + + "release" keyword must be follwed by an event name + + +The release keyword is used to release an event. +Every requested event must be released explicitly after it is not used anymore + +Arguments: +Event: The event name. + + + + + + + + Event + + + + + state + + + + "set" keyword must be follwed by an event name + + +The set keyword is used to set an event. Every set state event must be explicitly unset. + +Arguments: +Event: The event name. +state If set to 1, indicates that this is a state event, i.e. it remains set until it is unset explicitly with the unset keyword. +If set to 0, indicates that the event is an indication, so it is set only once to every requester and implicitly unset after that. + + + + + + + + Event + + + + "unset" keyword must be follwed by an event name + + +The unset keyword is used to unset a state event. Every set state event must be unset. +Indication events cannot be unset. +Unset blocks until everyone who has requested the specified event have released the event. + +Arguments: +Event: The event name. + + + + + + + SlaveType + + + SlaveName + + + + "allocate" keyword must be follwed by slave type ans slave name + + +The allocate keyword is used to allocate a slave, for example for running a test case on a remote phone. +It uses Remote Control Protocol (RPC). +The slave must always be allocated first before it can be used. + +Arguments: +Slave type: The type of the slave. +STIF only supports slave phone. phone indicates that slave phone is also running STIF. +Other types must be handled by the slave implementation, i.e. when implementing separate support for external network simulator. + +Slave name: A unique name for the slave. + + + + + + + + + SlaveName + + + + "free" keyword must be follwed by slave name + + +Every allocated slave must be freed with free when it becomes unused. + +Arguments: +Slave type: The type of the slave. +STIF only supports slave phone. phone indicates that slave phone is also running STIF. +Other types must be handled by the slave implementation, i.e. when implementing separate support for external network simulator. + + + + + + + + objectName + + + + run + + + request + + + wait + + + set + + + unset + + + set + + + release + + + + module + + + + + testmodule + + + configfile + + + testCaseNumber + + + expect + + + testid + + + ini + + + category + + + timeout + + + title + + + + syntax error error + + +The remote keyword is used to start the execution of a test case in a slave and also to request and release events from the slave. +Other test case controlling for remote test cases is done with the same keywords as for the local test cases. + +Arguments: +Slave name: The slave name, the same that was given for allocate. +Command name: The remote command name +supported commands: +-run +-request +-wait +-set +-unset +-release + + + + + +