Next: , Previous: ti_stop_interference, Up: Test interference


12.4 Using test interference in scripted test cases

Test Interference can be also used in scripted test cases, by scripter commands. New keyword, testinterference is used for that. Starting interference is done in the following way:

     testinterference name command type value idle_time busy_time

testinterference - mandatory keyword

name - identifier of created testinterference

command - can have two values, "start" or "stop"

type - can have the following values: "cpuload", "memload" and "ioload". Determines type of started interference.

value - numeric parameter, for cpuload determines amount of taken CPU time in percent. For memload it holds amount of taken memory in megabytes. For ioload value is ignored.

idle_time - numeric parameter, specifies time in cycle when disturbance is stopped (in milliseconds). Giving it value 0 is equal to starting constant disturbance.

busy_time - numeric parameter, time the disturbance is active during cycle.

All numeric parameters are mandatory ( due to way parameters are handled in scripter).

Failure to call "stop" command for all "started" interferences in test case will make the case invalid.