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⇛

end denotes the end of a while→, foreach→, if→, with→ or withvector→ block. Each of those block openers must be matched with a corresponding end. more⇛

The optional keyword is used in map construction to allow a value not to exist. Normally if an RValue→ does not exist if will trigger an error. more⇛

while loops on a block of code so long as a given condition remains true. more⇛

The main unit→ entry point can be specified on the command line. Alternately it may be specified as the item System.Main. This is useful in cases where all configuration data should come from a ptest→ file. more⇛