Step reference

Every step a test can name in uses:, with the parameters it accepts under with: and the output fields it publishes — the names returns:, validate: and later steps read. The reference is generated from the steps' declared Pydantic models, so it cannot drift from the implementation. For where these blocks sit in a test file, see the TCK syntax.

56 steps. The checks a step's outputs are held to are listed under Validations.

Categories and modules

Category	Module	Steps
`connector`	`consumer`	`discover_connector`, `do_dsp`, `do_dsp_with_bpnl`, `extract_dataset`, `get_edr`, `initiate_transfer`, `negotiate`, `pull_data_filtered`, `pull_data_filtered_by_policy`, `query_catalog`, `query_catalog_by_asset_id`, `query_catalog_by_bpnl`, `query_catalog_with_filters`
`connector`	`dataplane`	`http_request`
`connector`	`discover/digital-twin-registry`	`auth`
`connector`	`provider`	`create_asset`, `create_contract_definition`, `create_policy`, `delete_asset`, `delete_contract_definition`, `delete_policy`
`connector`	`provider/wizard`	`create_asset`, `create_policy`
`digital-twin-registry`	`consumer/dataplane`	`get_shell_descriptor`, `get_shell_descriptors`, `lookup_shell`, `lookup_shells_by_asset_link`
`digital-twin-registry`	`provider`	`create_shell_descriptor`, `create_submodel_descriptor`, `delete_shell_descriptor`, `get_shell_descriptor`, `lookup_shells`
`digital-twin-registry`	`provider/wizard`	`create_shell_descriptor`, `create_submodel_descriptor`
`digital-twin-registry`	`submodel`	`delete`, `upload`
`flow`	—	`delay`, `if`, `retry`
`http`	—	`http_request`
`mock`	—	`api`, `discovery`, `dtr`
`mock`	`wait/dataplane`	`http_request`
`mock`	`wait`	`http_request`
`notification`	`consumer`	`discover_assets`, `send`
`security`	`oauth2`	`client_credentials`, `password`, `refresh_token`
`util`	—	`base64`, `generate_uuid`, `json_path_extract`, `log`, `parse_kv`, `validate_path`