Test scenarios

Combine generated tables with a runnable HTTP test scenario for supported tools. A scenario pairs generated records with requests and checks. Describe data in GBDDL, set the base URL and request actions in the scenario projection, then choose a supported runner. Keep credentials and environment-specific URLs outside the recipe. GBDDL validation and pricing are shared across Chef, the HTTP API and MCP. Consult the recipe language, output formats, and credit model for the supported syntax and behavior.

Supported targets are k6, artillery, jmeter, postman, hurl and http. Scenario outputs require a root projection and at least one request. Requests declare a method, path, optional headers and expected status codes. Supported request strings can interpolate root columns with {{column}} and runtime environment values with {{env.NAME}}.

Scenario options include baseurl, users, duration, iterations and rate; their effect depends on the runner. Generated packages contain data, runner-specific assets and a README. Run them externally and review their configuration before targeting your service.