Previous Next

The invoke recordable action provides the usage of subtests by making it possible to call the execution of some subtest from the execution of an embedding (invoking) test. Short frequently used tests can be recorded as normal tests, and then be invoked as subtests.

Invokes within invokes are allowed, but looping is not allowed: a test must end at some point. If you add an invoke action with the Invoke WB_clipinvoke icon, Web Benchmark checks that loops do not occur, but by chaing invoked test names manually later, you could still cause a loop to occur. Loops will probably cause the test execution to crash or to hang, so this is not recommended.  if youmanually changing the called test names afterwards may make it possible to still cause this behavior. However, making tests loop will probably crash (hang) the test execution completely so we do not recommend this.Cannot be nested (loop recursion), although an invoked test may call another test that contains more invokes.


The following properties are in scope:




Test name


The name of the test to be invoked.

Test suite


The test suite where the test to be invoked must be found.


NOTE: If the invoked test requires you to pass input parameter values, these values must be entered as part of this action, or else the playback engine will report them as missing.



See also

List of recordable actions