Template tokens & filters

Test-Lab resolves four kinds of {{...}} placeholders in your prompts, cookies, headers, and data-fixture values.

Run context

Use run.shortId to tag resources the test creates so a per-run cleanup webhook can scope its DELETE:

Create a property named "QA-{{run.shortId}}".

Both timestamp variants come from the same source; pick the precision your use case needs.

Pipeline context

For multi-step pipelines, each step runs as its own job. {{run.timestampMs}} resolves to slightly different values in step 1 vs. step 2 (off by milliseconds), and {{run.id}} is the step's own job id, not a shared identifier.

{{pipeline.X}} is allocated once per dispatch and shared across every step. Step 1 and step 2 see identical values, which is what makes flows like "step 1 creates a contact, step 2 finds the same contact" work.

Single-step plans also get a fresh pipeline context per dispatch, so the same prompt vocabulary works in both cases.

Data fixtures

See Test data for the full reference. Quick summary:

Sign up as {{data.contact.first_name}} {{data.contact.last_name}}
with email {{data.contact.email}}.

Each field is either Static (same value every run, until you change it) or Dynamic (auto-generates a fresh value on every dispatch).

A static field's stored value can itself embed {{run.X}} or {{pipeline.X}} for per-run uniqueness. The substitution chain resolves the embedded tokens after the fixture lookup.

Credentials

See Credentials.

Filters

Apply a filter chain to format any resolved value, Liquid-style:

{{ run.timestamp | format: 'DD.MM.YYYY' }}
{{ pipeline.timestampMs | format: 'YYYY-MM-DD HH:mm' }}
{{ run.timestamp | format: 'YYYY-MM-DD HH:mm', 'Europe/Bucharest' }}

Whitespace inside the braces is tolerated. Filters apply after the namespace lookup resolves the bare value, so they work on any of the four namespaces above.

format

The first argument is the pattern. The second (optional) argument is an IANA timezone name (Europe/Bucharest, America/Los_Angeles, Asia/Tokyo, etc.). When omitted, the value formats in UTC.

Format tokens

Anything else in the pattern emits verbatim. Separators like ., -, :, /, and spaces don't need escaping.

Examples

Input formats

The format filter accepts:

• Unix seconds (10-digit string): {{run.timestamp}} emits this shape.
• Unix milliseconds (13-digit string): {{run.timestampMs}} and {{pipeline.timestampMs}} emit this shape.
• ISO 8601 strings, useful when a data-fixture value stores a date.

Anything else passes through unchanged.

Unknown filters

A typo in a filter name (e.g. | upper when only format is supported) is a no-op: the value passes through unchanged. The substitution stays lossy-but-survivable so a typo doesn't blow up the middle of an AI prompt.