You can use this set of commands to log the timing metrics about the performance of your application under test, from within your automated tests during their run-time execution. 

Using these commands your tests can capture/log the time taken for key events (like page load, DOM load, etc) or the specific actions to be performed within your test.

At the time of development of your automated tests (specifically the test scripts), you can build logic within your scripts to read from a user-defined variable (or from a data file) the log level that determined how much information you want to be captured/logged from within your automated test during its run-time execution. At the time of execution of the automated tests, you dynamically pass the value to the user-defined variable (or feed value from within a data file bound to a test) that defines the actual amount of timing metrics captured/logged within your test. The log levels supported are DEBUG, INFO, WARN, FATAL and ERROR. 

The commands in this category also allow your tests to persist the timing metrics captured/logged (in a Data Set) to a Data File within your project.

Sometimes you may want to log the cumulative execution time of a block of test instructions within your test as a key event's timing metric you want to report on. Some other times, you may want to get key application performance related timing metric (like page load time, DOM load time, etc., ) using JavaScript functions (using libraries like Resource Timing API that many browsers natively support, that you can get using runScript command within Worksoft SaaS) or using the Worksoft SaaS supported functions by tapping into the 'runEventTimingFunction' command and log the response from those functions as your key event timing metric that you want to report on. In the same test, Worksoft SaaS allows you to log some key event timings using the former approach described above and some other key event timing metrics using the latter approach.

At a high level, here is a flow that you will have to implement to reap the value from the commands in this category.

First, define your dataset using the command 'createDataset'                 

Then,

a) For each block of test instructions that you want the 'cumulative' execution time captured as a key event timing, define a block like the one portrayed below:

Lastly, the key events' timing metrics that are captured using either or both of the approaches described above, can be persisted into 'Data Files' within your project, from within your automated tests in execution. Optionally, if you want, you can additionally log the key event timing values into analytics reports for performance testing using  'echoForReporting' command.

The table(s) below lists the commands in the ascending alphabetic order within each category along with a brief description of the purpose behind the command. By clicking on the hyperlinked command name in the table(s) below, you can review more detailed information about a specific command that includes the syntax for you to follow when using the commands. Please note that these commands (constructs) are supported within Worksoft SaaS application (Edit Test Script screen) only and NOT supported in QaSCRIBE test authoring tool.