triad-behaviors

Behaviors — the BDD DSL

This is the most load-bearing skill for writing correct TriadJS code. The assertion parser is heuristic — phrases that don't match a supported pattern exactly fail with "Unrecognized assertion". The phrase table in §Assertion phrases below is authoritative; don't guess.

The builder

import { scenario } from '@triadjs/core';

scenario('Pets can be created with valid data')   // the Scenario: line in Gherkin
  .given('a valid pet payload')                   // narrative string
  .body({ name: 'Buddy', species: 'dog', age: 3 })
  .when('I create a pet')                         // narrative string
  .then('response status is 201')                 // parsed assertion
  .and('response body matches Pet')               // parsed assertion
  .and('response body has name "Buddy"');         // parsed assertion

A scenario is documentation, a test, and a Gherkin line in one. Writing an endpoint without behaviors defeats the framework.

.given() stage methods

Everything between .given(...) and .when(...) sets up the request and the fixture bag.

Method	Effect
.body(data)	Sets the request body. Placeholders interpolated from fixtures.
.params({ id: '{petId}' })	Path params. {placeholder} substituted from fixtures.
.query({ limit: 10 })	Query string.
.headers({ authorization: 'Bearer {token}' })	Request headers.
.setup(async (services) => { ... })	Seed the database. Return value is merged into fixtures.
.fixtures({ key: value })	Inline fixtures (merged on top of setup() return).

Fixtures and {placeholder} substitution

Two sources of fixtures, merged at run time:

1. .setup() return value — anything it returns becomes fixtures.
2. .fixtures({...}) — static values.

Inside strings, {key} is replaced with String(fixtures[key]). Special case: if a string is entirely one token (e.g. '{petId}') and the fixture value is not a string, the raw non-string value is substituted (so numbers stay numbers).