assert_data
Assert a 1C data-layer value against an expected result via read-only OData by locating a record with a filter or key and matching a field with equals, contains, or regex.
Instructions
DEPRECATED for a test-client-held base — see below. Assert a value in the DATA LAYER via
read-only 1C OData. Locate a record in entity_set (e.g. 'Catalog_Товары') by an OData filter (e.g.
"Description eq 'Обувь'") or a key (Ref_Key guid / code), then assert field against expected with
match = equals|contains|regex. Connection from params or env (QA_MCP_ODATA_URL/USER/PASSWORD). Returns {ok,
actual, expected, record_count, deprecated, deprecation, …}.
DEPRECATION: an infobase opened by a «Клиент тестирования» is EXCLUSIVELY LOCKED, so OData cannot read it — an
OData read-back of what the running test client just did is impossible on that base. Verify UI writes through the
SAME client's protocol value-read (write_form_fields_by_label returns a value-read committed;
read_record / read_form_descriptor read committed values). This tool is valid ONLY against a SEPARATELY
published, non-exclusive OData endpoint.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"entity_set": "<entity_set>",
"field": "<field>",
"expected": "<expected>"
},
"name": "assert_data"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| key | No | ||
| user | No | ||
| field | Yes | ||
| match | No | equals | |
| filter | No | ||
| select | No | ||
| base_url | No | ||
| expected | Yes | ||
| password | No | ||
| entity_set | Yes |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||