Executable contract syntax

SpecTestEngine DSL reference

The DSL reference documents every supported field for REST, SOAP, GraphQL, flows, and fragments with complete examples, recipes, and an autocomplete playground.

What you can do

  • Browse protocol-specific documents and field-by-field explanations.
  • Compare complete executable examples and common recipes.
  • Experiment with autocomplete and validation without changing project data.

Starts with

  • A document family such as REST, SOAP, GraphQL, Flow, or Fragment.
  • A field, behavior, or recipe that needs exact syntax.

Produces

  • Copyable DSL examples and precise field semantics.
  • Validated draft content ready to use in a specification, flow, or fragment editor.

Use it when

  • Use the DSL reference when UI labels are not enough to explain a raw definition.
  • Use the interactive product page when you want to save or execute the resulting asset.

Related documentation

FragmentsCreate reusable typed building blocks from documented DSL.SpecificationsCreate and execute complete protocol contracts.
  • DSL
  • REST DSL
  • SOAP DSL
  • GraphQL DSL
  • Flow DSL
Executable test language

Understand the complete DSL before composing its pieces.

SpecTestEngine specifications keep the request and its expected behavior together. Pick a complete contract, inspect any field, then edit the same example with live syntax assistance in the playground.

DSL familyFragments

Save one reusable request or assertion concern, then assemble compatible fragments into a complete engine-owned specification.

Complete JSONFragments
Click any line to reveal its field guide
Field guideRequest

Fragment name

namestring Required

A readable library name that explains what this reusable piece contributes.

Request

Protocol

Response

Filtering

Attachments

Playground

Practice with the same editor assistance

Start typing a field name to see context-aware suggestions. This workspace is local to the page: it does not save, run, or change any project asset.

URL and method
Valid
{
"url": "https://api.example.com/catalog",
"method": "GET"
}
Continue in the product guide

See how this contract is created, assembled, run, and reviewed.

The Automation and Flow guides use populated product screens, so you can connect these fields to the controls and evidence users work with every day.

Open Fragments guide