When recording a Metric→ or otherwise reporting a period of elapsed time, the Duration→ type may need to be converted. The durationAs function enables these conversions. more⇛

TestPlan generally uses lazy type conversion: when a variable needs to be a specific type it as converted at the time it is needed. This means that when you assign items in the context they tend to be a direct copy of whatever they are being assigned from. more⇛

createHTTPRequest allows creation of an arbitrary HTTP Request→ object. This is used in cases where simply specifying a URL or using one of the standard functions is not sufficient. This often arises when trying to use a REST API or to test very specific requests. more⇛

Can be used to store the content of a request→ into a file. This will execute the request and store the result into the file. more⇛

Creates the Request→ that would result from the Click→ function. In many cases this can only be an approximation of the request, not the exact same request that the browser would submit. more⇛

A Request is an object which specifies how something can be retrieved. Rather than dealing directly with URLs many functions work with these abstract request objects -- as does TestPlan internally. more⇛

If doing data extraction with TestPlan you will likely need to write data into a file. The DataFile commands offer a simple way to store structured data into a CSV or XML file. more⇛

The InvokeAction# commands are used to perform individual user actions on UI elements. They are particular useful in cases with a lot of dynamic behaviour or inputs not within a form. more⇛

seqInteger is a set→ function which creates an iterable sequence. It is most commonly used to count between two numbers in a foreach→ statement. more⇛

Sleep causes the current script to pause a specified period of time. Other units running in parallel will be unaffected by this call. more⇛