SEC-AUTH-001 Server rejects invalid or missing auth credentialsRunner MUST attempt a SendMessage request without valid credentials and verify rejection.
capabilities: + authentication: true
method: POST + path: / + headers: + Content-Type: application/json + A2A-Version: 1.0 + body: + jsonrpc: 2.0 + id: sec-auth-001 + method: SendMessage + params: + message: + role: ROLE_USER + parts: + - text: auth should be required
status: + one_of: + - 200 + - 401 + - 403 + body: + any_of: + - error: exists: true + - title: type: string
SEC-AUTH-002 Server returns authorization error for insufficient permissionsRunner MUST attempt a request with valid but insufficient credentials and verify rejection.
capabilities: + authentication: true
method: POST + path: / + headers: + Content-Type: application/json + A2A-Version: 1.0 + Authorization: Bearer {{insufficientAuthToken}} + body: + jsonrpc: 2.0 + id: sec-auth-002 + method: SendMessage + params: + message: + role: ROLE_USER + parts: + - text: authorization should fail
status: + one_of: + - 200 + - 403 + body: + any_of: + - error: exists: true + - title: type: string
SEC-AUTH-003 Server does not reveal unauthorized resource existenceRunner MUST verify that getting a task belonging to another user returns the same error as getting a nonexistent task.
capabilities: + authentication: true
id: {{otherUserTaskId}}
message: + type: string
id: 00000000-0000-0000-0000-000000000000
message: + type: string
SEC-AUTH-004 Server authenticates every incoming requestRunner MUST verify that unauthenticated requests to all endpoints are rejected.
capabilities: + authentication: true
method: POST + path: / + headers: + Content-Type: application/json + A2A-Version: 1.0 + body: + jsonrpc: 2.0 + id: sec-auth-004 + method: GetTask + params: + id: 00000000-0000-0000-0000-000000000000
status: + one_of: + - 200 + - 401 + - 403 + body: + any_of: + - error: exists: true + - title: type: string
SEC-AUTH-005 In-task auth transitions to AUTH_REQUIRED stateVerifies that an in-task authentication challenge transitions the task into TASK_STATE_AUTH_REQUIRED with a status message.
message: + role: ROLE_USER + parts: + - text: tck-auth-required trigger auth
status: 200 + body: + task: + status: + state: TASK_STATE_AUTH_REQUIRED + message: + exists: true
SEC-PUSH-001 Push notification webhook includes auth credentialsRunner MUST set up a webhook and verify auth credentials are present in request headers.
capabilities: + pushNotifications: true
message: + role: ROLE_USER + parts: + - text: tck-long-running start + configuration: + returnImmediately: true
status: 200 + body: + task: + id: + type: string
taskId: task.id
taskId: {{create-task.taskId}} + pushNotificationConfig: + url: {{webhookUrl}} + authentication: + scheme: Bearer + credentials: test-token
status: 200 + body: + id: + type: string
SEC-PUSH-002 Client validates push notification webhook authenticityRunner MUST verify that webhook requests with invalid auth are rejected by the client.
capabilities: + pushNotifications: true
message: + role: ROLE_USER + parts: + - text: tck-long-running start + configuration: + returnImmediately: true
status: 200 + body: + task: + id: + type: string
taskId: task.id
taskId: {{create-task.taskId}} + pushNotificationConfig: + url: {{webhookUrl}} + authentication: + scheme: Bearer + credentials: expected-token
status: 200 + body: + id: + type: string
SEC-EXTCARD-001 Extended Agent Card requires authenticationVerifies that fetching the extended Agent Card without authentication is rejected.
capabilities: + extendedAgentCard: true
method: GET + path: /extendedAgentCard + headers: + Accept: application/json + A2A-Version: 1.0
status: + one_of: + - 401 + - 403 + body: + any_of: + - title: type: string + - error: exists: true
SEC-EXTCARD-002 Extended Agent Card verifies permissions before returningRunner MUST verify that an authenticated request with insufficient permissions is rejected.
capabilities: + extendedAgentCard: true
method: GET + path: /extendedAgentCard + headers: + Accept: application/json + A2A-Version: 1.0 + Authorization: Bearer {{insufficientAuthToken}}
status: + one_of: + - 401 + - 403 + body: + any_of: + - title: type: string + - error: exists: true
SEC-EXTCARD-003 Missing extended-card support returns specified errorVerifies that Get Extended Agent Card returns the specified error when the capability is not advertised.
capabilities: + extendedAgentCard: false
extended: true
code: UnsupportedOperationError
SEC-EXTCARD-004 Extended cards enforce access controlsRunner MUST verify that extended Agent Cards enforce access controls consistently with the registered endpoint.
capabilities: + extendedAgentCard: true
method: GET + path: /extendedAgentCard + headers: + Accept: application/json + A2A-Version: 1.0
status: + one_of: + - 401 + - 403 + body: + any_of: + - title: type: string + - error: exists: true
SEC-AUTH-006 Server uses binding-specific auth challenge or rejectionRunner SHOULD verify that authentication rejection uses the binding-appropriate mechanism, such as HTTP 401 for HTTP transports.
capabilities: + authentication: true
method: GET + path: /.well-known/agent-card.json + headers: + Accept: application/json + A2A-Version: 1.0
status: + one_of: + - 200 + - 401 + - 403 + body: + any_of: + - title: type: string + - error: exists: true
CLIENT-PARSE-001 Parse SendMessage response with completed taskVerifies the SDK client can parse a SendMessage response containing a completed task with artifacts. +
operation: send_message + wire_payload: + jsonrpc: 2.0 + id: req-001 + result: + task: + id: task-abc-123 + contextId: ctx-001 + status: + state: TASK_STATE_COMPLETED + timestamp: 2025-05-25T20:00:00Z + artifacts: + - artifactId: art-1 + parts: - text: hello world
task: + id: task-abc-123 + contextId: ctx-001 + status: + state: TASK_STATE_COMPLETED + artifacts: + count_gte: 1
CLIENT-PARSE-002 Parse SendMessage response with message (no task)Verifies the SDK client can parse a SendMessage response containing a direct message (no task created). +
operation: send_message + wire_payload: + jsonrpc: 2.0 + id: req-002 + result: + message: + messageId: msg-001 + role: ROLE_AGENT + parts: + - text: I can help with that
message: + messageId: msg-001 + role: ROLE_AGENT + parts: + count_gte: 1
CLIENT-PARSE-003 Parse GetTask responseVerifies the SDK client can parse a GetTask response with full task state including history and artifacts. +
operation: get_task + wire_payload: + jsonrpc: 2.0 + id: req-003 + result: + id: task-xyz-789 + contextId: ctx-002 + status: + state: TASK_STATE_COMPLETED + timestamp: 2025-05-25T20:05:00Z + artifacts: + - artifactId: art-1 + parts: - text: result text + - artifactId: art-2 + parts: - data: key: value + history: + - role: ROLE_USER + parts: - text: original request + - role: ROLE_AGENT + parts: - text: processing...
id: task-xyz-789 + contextId: ctx-002 + status: + state: TASK_STATE_COMPLETED + artifacts: + count_gte: 2 + history: + count_gte: 2
CLIENT-PARSE-004 Parse error responseVerifies the SDK client can parse a JSON-RPC error response and surface the A2A error code and message. +
operation: get_task + wire_payload: + jsonrpc: 2.0 + id: req-004 + error: + code: -32001 + message: Task not found + data: + taskId: nonexistent-task-id
error: + code: -32001 + message: + contains: not found
CLIENT-PARSE-005 Parse task with INPUT_REQUIRED stateVerifies the SDK client correctly parses a task in INPUT_REQUIRED state with a status message prompting for more input. +
operation: send_message + wire_payload: + jsonrpc: 2.0 + id: req-005 + result: + task: + id: task-multi-001 + contextId: ctx-multi-001 + status: + state: TASK_STATE_INPUT_REQUIRED + timestamp: 2025-05-25T20:10:00Z + message: + messageId: status-msg-001 + role: ROLE_AGENT + parts: + - text: Please provide more details
task: + id: task-multi-001 + status: + state: TASK_STATE_INPUT_REQUIRED + message: + role: ROLE_AGENT + parts: + count_gte: 1
CLIENT-PARSE-006 Parse task with mixed artifact typesVerifies the SDK client can parse artifacts containing text, data, file, and fileUrl parts in a single response. +
operation: get_task + wire_payload: + jsonrpc: 2.0 + id: req-006 + result: + id: task-mixed-001 + contextId: ctx-mixed-001 + status: + state: TASK_STATE_COMPLETED + timestamp: 2025-05-25T20:15:00Z + artifacts: + - artifactId: art-text + parts: - text: Plain text result + - artifactId: art-data + parts: - data: temperature: 72.5 + unit: fahrenheit + - artifactId: art-file + parts: - file: name: report.pdf + mediaType: application/pdf + bytes: JVBERi0xLjQ= + - artifactId: art-url + parts: - fileUrl: url: https://example.com/report.pdf + name: report.pdf + mediaType: application/pdf
id: task-mixed-001 + artifacts: + count_gte: 4
CLIENT-AUTH-001 Client replaces cached public card with extended cardRunner SHOULD verify that after fetching an extended Agent Card, the client uses the extended capabilities for the authenticated session.
operation: get_agent_card + wire_payload: + name: Example Agent + version: 1.0.0 + capabilities: + streaming: false + extendedAgentCard: true + supportedInterfaces: + - url: https://example.com/.well-known/agent-card.json + protocolBinding: REST + protocolVersion: 1.0
capabilities: + extendedAgentCard: true
operation: get_extended_agent_card + wire_payload: + name: Example Agent + version: 1.0.0 + capabilities: + streaming: true + extendedAgentCard: true + skills: + - id: extended-skill + name: Extended Skill + supportedInterfaces: + - url: https://example.com/extendedAgentCard + protocolBinding: REST + protocolVersion: 1.0
capabilities: + streaming: true + extendedAgentCard: true + skills: + count_gte: 1
CLIENT-CAP-001 Client checks Agent Card before using optional capabilitiesRunner SHOULD verify that the client checks Agent Card capabilities before calling optional operations.
operation: get_agent_card + wire_payload: + name: Capability Gated Agent + version: 1.0.0 + capabilities: + streaming: false + pushNotifications: false + supportedInterfaces: + - url: https://example.com/.well-known/agent-card.json + protocolBinding: REST + protocolVersion: 1.0
capabilities: + streaming: false + pushNotifications: false
SendMessage, GetTask, and CancelTask conformance coverage for core lifecycle flows.
CORE-SEND-001 SendMessage returns a completed taskVerifies that SendMessage can return a completed task for the complete-task TCK behavior.
message: + role: ROLE_USER + parts: + - text: tck-complete-task hello world
status: 200 + body: + task: + id: + type: string + status: + state: TASK_STATE_COMPLETED
taskId: task.id
CORE-SEND-002 SendMessage to a terminal task returns errorVerifies that sending a follow-up message to a terminal task returns the protocol error for unsupported operation.
message: + role: ROLE_USER + parts: + - text: tck-complete-task setup
status: 200 + body: + task: + id: + type: string + status: + state: TASK_STATE_COMPLETED
taskId: task.id
taskId: {{setup.taskId}} + message: + role: ROLE_USER + parts: + - text: tck-complete-task terminal follow-up
error_type: UnsupportedOperationError + message: + type: string
CORE-SEND-003 SendMessage returns a message response (no task)Verifies that SendMessage may return a direct agent message response without creating a task.
message: + role: ROLE_USER + parts: + - text: tck-message-response hello
status: 200 + body: + message: + role: ROLE_AGENT + task: + absent: true
CORE-GET-001 GetTask returns current state of existing taskVerifies that GetTask returns the current state for an existing completed task.
message: + role: ROLE_USER + parts: + - text: tck-complete-task for get
status: 200 + body: + task: + id: + type: string + status: + state: TASK_STATE_COMPLETED
taskId: task.id
id: {{send.taskId}}
status: 200 + body: + id: {{send.taskId}} + status: + state: TASK_STATE_COMPLETED
CORE-GET-002 GetTask with historyLength 0 omits historyVerifies that GetTask omits task history, or returns it as an empty array, when historyLength is zero.
message: + role: ROLE_USER + parts: + - text: tck-complete-task history zero
status: 200 + body: + task: + id: + type: string + status: + state: TASK_STATE_COMPLETED
taskId: task.id
id: {{send.taskId}} + historyLength: 0
status: 200 + body: + id: {{send.taskId}} + history: + any_of: + - absent: true + - type: array + count: 0
CORE-CANCEL-001 CancelTask returns updated stateVerifies that CancelTask returns the updated canceled task state for a task started in return-immediately mode.
message: + role: ROLE_USER + parts: + - text: tck-cancel start + configuration: + returnImmediately: true
status: 200 + body: + task: + id: + type: string + status: + state: + one_of: + - TASK_STATE_SUBMITTED + - TASK_STATE_WORKING
taskId: task.id
id: {{start.taskId}}
status: 200 + body: + id: {{start.taskId}} + status: + state: TASK_STATE_CANCELED
CORE-CANCEL-002 CancelTask on terminal task returns errorVerifies that CancelTask on a terminal task fails with TaskNotCancelableError.
message: + role: ROLE_USER + parts: + - text: tck-complete-task setup
status: 200 + body: + task: + id: + type: string + status: + state: TASK_STATE_COMPLETED
taskId: task.id
id: {{setup.taskId}}
error_type: TaskNotCancelableError + message: + type: string
CORE-FAIL-001 Task completes with failed stateVerifies that SendMessage can return a failed task with an explanatory status message.
message: + role: ROLE_USER + parts: + - text: tck-task-failure trigger error
status: 200 + body: + task: + id: + type: string + status: + state: TASK_STATE_FAILED + message: + exists: true
CORE-SEND-004 SendMessage rejects unsupported content typeVerifies that SendMessage fails with ContentTypeNotSupportedError when a message part uses an unsupported content type.
message: + role: ROLE_USER + parts: + - data: value: unsupported + metadata: contentType: application/x-unsupported-type-12345
code: ContentTypeNotSupportedError
CORE-LIST-001 ListTasks returns tasks for a contextVerifies that ListTasks can return at least one task for an existing context.
message: + role: ROLE_USER + parts: + - text: tck-complete-task for list test
status: 200 + body: + task: + id: + type: string + contextId: + type: string + status: + state: TASK_STATE_COMPLETED
taskId: task.id + contextId: task.contextId
contextId: {{send.contextId}}
status: 200 + body: + tasks: + type: array + count_gte: 1
CORE-LIST-002 ListTasks with includeArtifacts false omits artifactsVerifies that ListTasks omits artifacts, or returns them as null, when includeArtifacts is false.
message: + role: ROLE_USER + parts: + - text: tck-complete-task for list artifacts test
status: 200 + body: + task: + id: + type: string + contextId: + type: string + status: + state: TASK_STATE_COMPLETED
taskId: task.id + contextId: task.contextId
contextId: {{send.contextId}} + includeArtifacts: false
status: 200 + body: + tasks: + type: array + count_gte: 1 + items: + - id: {{send.taskId}} + contextId: {{send.contextId}} + artifacts: any_of: + - absent: true + - type: null
CORE-LIST-003 ListTasks response includes nextPageTokenVerifies that ListTasks responses always include nextPageToken, using an empty string for the final page.
message: + role: ROLE_USER + parts: + - text: tck-complete-task for list next page token test
status: 200 + body: + task: + id: + type: string + contextId: + type: string
taskId: task.id + contextId: task.contextId
contextId: {{send.contextId}}
status: 200 + body: + tasks: + type: array + count_gte: 1 + nextPageToken: + type: string
DM-ART-001 Text artifactSends a request that should produce at least one text artifact and verifies a returned artifact part includes a text field. +
message: + role: ROLE_USER + parts: + - text: tck-artifact-text hello
status: 200 + body: + task: + status: + state: TASK_STATE_COMPLETED + artifacts: + count_gte: 1
DM-ART-002 Data artifact (structured JSON)Sends a request that should produce a structured JSON artifact and verifies a returned artifact part includes an object-valued data field. +
message: + role: ROLE_USER + parts: + - text: tck-artifact-data structured
status: 200 + body: + task: + status: + state: TASK_STATE_COMPLETED + artifacts: + count_gte: 1
DM-ART-003 File artifact (inline)Sends a request that should produce an inline file artifact and verifies a returned artifact part includes file metadata. +
message: + role: ROLE_USER + parts: + - text: tck-artifact-file document
status: 200 + body: + task: + status: + state: TASK_STATE_COMPLETED + artifacts: + count_gte: 1
DM-ART-004 File URL artifactSends a request that should produce a file URL artifact and verifies a returned artifact part includes fileUrl metadata. +
message: + role: ROLE_USER + parts: + - text: tck-artifact-file-url document
status: 200 + body: + task: + status: + state: TASK_STATE_COMPLETED + artifacts: + count_gte: 1
DM-SERIAL-001 Timestamps are ISO 8601 UTCmessage: + role: ROLE_USER + parts: + - text: tck-complete-task timestamp
status: 200 + body: + task: + status: + state: TASK_STATE_COMPLETED + timestamp: + matches: ^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}
DM-SERIAL-002 Response validates against A2A schemaRunner SHOULD validate full response against A2A JSON Schema.
message: + role: ROLE_USER + parts: + - text: tck-complete-task schema
status: 200 + body: + task: + id: + type: string + status: + state: + type: string
DM-EXTRA-001 Extra fields accepted (tolerance)method: POST + path: / + headers: + Content-Type: application/json + A2A-Version: 1.0 + body: + jsonrpc: 2.0 + id: 1 + method: SendMessage + params: + message: + role: ROLE_USER + parts: + - text: tck-complete-task extra field + x_custom_field: test
status: 200 + body: + result: + exists: true
CARD-DISC-001 Agent card is discoverableAgent card is discoverable at the well-known URL and exposes core metadata.
status: 200 + body: + name: + exists: true + version: + exists: true + description: + exists: true
CARD-DISC-002 Agent card contains supported interfacesAgent card lists one or more supported interfaces with binding and version metadata.
status: 200 + body: + supportedInterfaces: + type: array + count_gte: 1 + items: + url: + type: string + protocolBinding: + one_of: + - JSONRPC + - GRPC + - REST + protocolVersion: + type: string
CARD-DISC-003 Agent card contains capabilitiesAgent card exposes capabilities as an object.
status: 200 + body: + capabilities: + exists: true + type: object
CARD-DISC-004 Agent card contains skillsAgent card includes skills with identifiers and names.
status: 200 + body: + skills: + type: array + items: + id: + exists: true + name: + exists: true
CARD-DISC-005 Agent card contains default input and output modesAgent card includes default input and output mode arrays.
status: 200 + body: + defaultInputModes: + type: array + defaultOutputModes: + type: array
CARD-DISC-006 Agent card protocolVersion matches spec versionThe first supported interface advertises an A2A 1.x protocol version.
status: 200 + body: + supportedInterfaces: + type: array + count_gte: 1 + items: + - protocolVersion: starts_with: 1.
CARD-CACHE-001 Agent card caching headersRunner SHOULD verify Cache-Control or ETag headers are present.
status: 200 + body: + name: + exists: true
CARD-SCHEMA-001 Agent card validates against schemaRunner MUST validate response against A2A AgentCard JSON Schema.
status: 200 + body: + name: + exists: true + capabilities: + type: object
CARD-EXT-001 Extended agent cardRetrieves the extended agent card when the capability is advertised.
capabilities: + extendedAgentCard: true
extended: true
status: 200 + body: + skills: + type: array + count_gte: 1 + description: + matches: .+
CARD-DISC-007 Agent card declares all supported protocolsVerifies that the public Agent Card declares at least one protocol endpoint through supportedInterfaces or a direct url field.
status: 200 + body: + any_of: + - supportedInterfaces: type: array + count_gte: 1 + - url: type: string
CORE-ERR-001 GetTask with non-existent ID returns TaskNotFoundErrorid: 00000000-0000-0000-0000-000000000000
code: TaskNotFoundError + message: + type: string
CORE-ERR-002 CancelTask on non-existent task returns errorid: 00000000-0000-0000-0000-000000000000
code: + one_of: + - TaskNotFoundError + - TaskNotCancelableError
CORE-ERR-003 CancelTask on completed task returns TaskNotCancelableErrormessage: + role: ROLE_USER + parts: + - text: tck-complete-task setup
status: 200 + body: + task: + id: + type: string + status: + state: TASK_STATE_COMPLETED
taskId: task.id
id: {{setup-completed-task.taskId}}
code: TaskNotCancelableError
CORE-ERR-004 SendMessage to terminal task returns UnsupportedOperationErrormessage: + role: ROLE_USER + parts: + - text: tck-complete-task first
status: 200 + body: + task: + id: + type: string + status: + state: TASK_STATE_COMPLETED
taskId: task.id
message: + role: ROLE_USER + taskId: {{create-terminal-task.taskId}} + parts: + - text: tck-complete-task second
code: UnsupportedOperationError
JSONRPC-ERR-001 Unknown method returns MethodNotFoundErrormethod: POST + path: / + headers: + Content-Type: application/json + A2A-Version: 1.0 + body: + jsonrpc: 2.0 + id: 1 + method: DoSomethingUnsupported + params: +{}
status: 200 + body: + error: + code: -32601 + message: + type: string
JSONRPC-ERR-002 Invalid JSON returns ParseErrormethod: POST + path: / + headers: + Content-Type: application/json + A2A-Version: 1.0 + body_raw: {this is not valid json
status: 200 + body: + error: + code: -32700
CORE-ERR-005 Error responses include actionable messageid: 00000000-0000-0000-0000-000000000000
code: TaskNotFoundError + message: + all_of: + - type: string + - matches: .{12,} + - any_of: - contains: task + - contains: Task + - contains: not found + - contains: does not exist
CORE-ERR-006 Malformed request returns InvalidRequestErrormethod: POST + path: / + headers: + Content-Type: application/json + A2A-Version: 1.0 + body: + jsonrpc: 2.0 + id: 1 + params: +{}
status: 200 + body: + error: + code: + one_of: + - -32600 + - -32602
CORE-CAP-001 Push not supported returns UnsupportedOperationErrorOverlaps with PUSH-CFG-004 but verifies the capability error at the error-handling suite level.
capabilities: + pushNotifications: false
message: + role: ROLE_USER + parts: + - text: tck-complete-task for push
status: 200 + body: + task: + id: + type: string
taskId: task.id
taskId: {{create-task.taskId}} + pushNotificationConfig: + url: https://example.com/webhooks/a2a-tests
code: UnsupportedOperationError
CORE-CAP-002 Streaming not supported returns errorcapabilities: + streaming: false
message: + role: ROLE_USER + parts: + - text: tck-complete-task streaming unsupported
code: UnsupportedOperationError
CORE-ERR-007 Error data contains structured error infoid: 00000000-0000-0000-0000-000000000000
code: TaskNotFoundError + data: + type: object
CORE-ERR-008 Error details include @type fieldVerifies that JSON-RPC error details include a google.rpc Any type discriminator.
method: POST + path: / + headers: + Content-Type: application/json + A2A-Version: 1.0 + body: + jsonrpc: 2.0 + id: core-err-008 + method: SendMessage + params: + taskId: 00000000-0000-0000-0000-000000000000 + message: + role: ROLE_USER + parts: + - text: missing task should return error details
status: 200 + body: + error: + message: + type: string + data: + type: array + count_gte: 1 + items: + - @type: type: string
CORE-ERR-009 Error response should not distinguish missing vs unauthorizedRunner SHOULD verify that the error response for a missing resource is indistinguishable from one for an unauthorized resource. This requires auth infrastructure.
id: 00000000-0000-0000-0000-000000000000
message: + type: string
JSONRPC-ERR-003 JSON-RPC error details include google.rpc.ErrorInfoVerifies that A2A-specific JSON-RPC errors include google.rpc.ErrorInfo in error.data.
method: POST + path: / + headers: + Content-Type: application/json + A2A-Version: 1.0 + body: + jsonrpc: 2.0 + id: jsonrpc-err-003 + method: GetTask + params: + id: 00000000-0000-0000-0000-000000000000
status: 200 + body: + error: + message: + type: string + data: + type: array + count_gte: 1
Coverage for GetTask and SendMessage history handling.
CORE-HIST-001 GetTask historyLength=0 returns no historyVerifies that GetTask omits history, or returns it as an empty array, when historyLength is zero.
message: + role: ROLE_USER + parts: + - text: tck-complete-task history zero
status: 200 + body: + task: + id: + type: string + status: + state: TASK_STATE_COMPLETED
taskId: task.id
id: {{send.taskId}} + historyLength: 0
status: 200 + body: + id: {{send.taskId}} + history: + any_of: + - absent: true + - type: array + count: 0
CORE-HIST-002 History count does not exceed historyLength limitVerifies that GetTask does not return more history entries than requested.
message: + role: ROLE_USER + parts: + - text: tck-multi-turn history limit first
status: 200 + body: + task: + id: + type: string + status: + state: TASK_STATE_INPUT_REQUIRED
taskId: task.id + contextId: task.contextId
taskId: {{turn1.taskId}} + contextId: {{turn1.contextId}} + message: + role: ROLE_USER + parts: + - text: tck-multi-turn history limit second
status: 200 + body: + task: + id: {{turn1.taskId}} + status: + state: TASK_STATE_INPUT_REQUIRED
taskId: {{turn1.taskId}} + contextId: {{turn1.contextId}} + message: + role: ROLE_USER + parts: + - text: done
status: 200 + body: + task: + id: {{turn1.taskId}} + status: + state: TASK_STATE_COMPLETED
id: {{turn1.taskId}} + historyLength: 2
status: 200 + body: + id: {{turn1.taskId}} + history: + any_of: + - absent: true + - type: array + count_lte: 2
CORE-HIST-003 SendMessage historyLength=0 returns no historyVerifies that SendMessage omits task history when configuration.historyLength is zero.
message: + role: ROLE_USER + parts: + - text: tck-complete-task send history zero + configuration: + historyLength: 0
status: 200 + body: + task: + id: + type: string + status: + state: TASK_STATE_COMPLETED + history: + absent: true
CORE-HIST-004 GetTask may return persisted historyVerifies that GetTask may omit history entirely, but if it returns history the field is an array.
message: + role: ROLE_USER + parts: + - text: tck-complete-task persisted history
status: 200 + body: + task: + id: + type: string + status: + state: TASK_STATE_COMPLETED
taskId: task.id
id: {{send.taskId}}
status: 200 + body: + id: {{send.taskId}} + history: + any_of: + - absent: true + - type: array
CORE-HIST-005 History messages are returned in chronological orderVerifies that persisted history preserves the order of the conversation turns.
message: + role: ROLE_USER + parts: + - text: tck-multi-turn chronological first
status: 200 + body: + task: + id: + type: string + status: + state: TASK_STATE_INPUT_REQUIRED
taskId: task.id + contextId: task.contextId
taskId: {{turn1.taskId}} + contextId: {{turn1.contextId}} + message: + role: ROLE_USER + parts: + - text: tck-multi-turn chronological second
status: 200 + body: + task: + id: {{turn1.taskId}} + status: + state: TASK_STATE_INPUT_REQUIRED
taskId: {{turn1.taskId}} + contextId: {{turn1.contextId}} + message: + role: ROLE_USER + parts: + - text: done
status: 200 + body: + task: + id: {{turn1.taskId}} + status: + state: TASK_STATE_COMPLETED
id: {{turn1.taskId}}
status: 200 + body: + id: {{turn1.taskId}} + history: + type: array + count_gte: 3
CORE-HIST-006 History content matches sent messagesVerifies that persisted history includes the messages sent during a multi-turn conversation.
message: + role: ROLE_USER + parts: + - text: tck-multi-turn first msg
status: 200 + body: + task: + id: + type: string + status: + state: TASK_STATE_INPUT_REQUIRED
taskId: task.id + contextId: task.contextId
taskId: {{turn1.taskId}} + contextId: {{turn1.contextId}} + message: + role: ROLE_USER + parts: + - text: tck-multi-turn follow up msg
status: 200 + body: + task: + id: {{turn1.taskId}} + status: + state: + one_of: + - TASK_STATE_INPUT_REQUIRED + - TASK_STATE_COMPLETED
taskId: {{turn1.taskId}} + contextId: {{turn1.contextId}} + message: + role: ROLE_USER + parts: + - text: done
status: 200 + body: + task: + id: {{turn1.taskId}} + status: + state: TASK_STATE_COMPLETED
id: {{turn1.taskId}}
status: 200 + body: + id: {{turn1.taskId}} + history: + type: array + count_gte: 2
CORE-MULTI-001 Multi-turn with INPUT_REQUIREDCovers TCK CORE-MULTI-001, CSIT scenario-parity input-required, and agentbin spec-multi-turn behavior.
message: + role: ROLE_USER + parts: + - text: tck-multi-turn start conversation
status: 200 + body: + task: + id: + type: string + status: + state: TASK_STATE_INPUT_REQUIRED
taskId: task.id + contextId: task.contextId
taskId: {{turn1.taskId}} + contextId: {{turn1.contextId}} + message: + role: ROLE_USER + parts: + - text: here is more input
status: 200 + body: + task: + id: {{turn1.taskId}} + status: + state: TASK_STATE_INPUT_REQUIRED
taskId: {{turn1.taskId}} + contextId: {{turn1.contextId}} + message: + role: ROLE_USER + parts: + - text: done
status: 200 + body: + task: + id: {{turn1.taskId}} + status: + state: TASK_STATE_COMPLETED
CORE-MULTI-005 SendMessage with only taskId infers contextIdVerifies follow-up SendMessage can omit contextId and still remain on the original task context.
message: + role: ROLE_USER + parts: + - text: tck-multi-turn start
status: 200 + body: + task: + id: + type: string + contextId: + type: string + status: + state: TASK_STATE_INPUT_REQUIRED
taskId: task.id + contextId: task.contextId
taskId: {{turn1.taskId}} + message: + role: ROLE_USER + parts: + - text: done
status: 200 + body: + task: + id: {{turn1.taskId}} + contextId: {{turn1.contextId}} + status: + state: TASK_STATE_COMPLETED
CORE-MULTI-006 SendMessage with taskId and wrong contextId returns errorVerifies mismatched contextId is rejected for a follow-up turn.
message: + role: ROLE_USER + parts: + - text: tck-multi-turn start
status: 200 + body: + task: + id: + type: string + status: + state: TASK_STATE_INPUT_REQUIRED
taskId: task.id
taskId: {{turn1.taskId}} + contextId: wrong-context-id-12345 + message: + role: ROLE_USER + parts: + - text: should fail
status: error + error: + exists: true
CORE-MULTI-003 Mismatched contextId and taskId is rejectedVerifies that SendMessage rejects a taskId and contextId pair from different conversations.
message: + role: ROLE_USER + parts: + - text: tck-complete-task first
status: 200 + body: + task: + id: + type: string + contextId: + type: string + status: + state: TASK_STATE_COMPLETED
taskId1: task.id + contextId1: task.contextId
message: + role: ROLE_USER + parts: + - text: tck-complete-task second
status: 200 + body: + task: + id: + type: string + contextId: + type: string + status: + state: TASK_STATE_COMPLETED
taskId2: task.id + contextId2: task.contextId
taskId: {{first.taskId1}} + contextId: {{second.contextId2}} + message: + role: ROLE_USER + parts: + - text: mismatched context and task
message: + type: string
CORE-CTX-001 Rejected client contextId returns an errorRunner SHOULD use a client-generated contextId that the server rejects and verify the server errors instead of minting a new contextId.
contextId: client-generated-context-that-should-be-rejected + message: + role: ROLE_USER + parts: + - text: tck-complete-task reject client context id
message: + type: string
CORE-EXEC-001 Long-running task with returnImmediately and pollingSends a long-running request with returnImmediately enabled, polls until the task reaches a terminal state, and verifies the task completes with at least one artifact. +
message: + role: ROLE_USER + parts: + - text: tck-long-running start process + configuration: + returnImmediately: true
status: 200 + body: + task: + id: + type: string + status: + state: + one_of: + - TASK_STATE_SUBMITTED + - TASK_STATE_WORKING
taskId: task.id
id: {{start.taskId}}
status: 200 + body: + status: + state: + type: string
until: status.state in [TASK_STATE_COMPLETED, TASK_STATE_FAILED] + max_attempts: 15 + delay_ms: 2000
id: {{start.taskId}}
status: 200 + body: + id: {{start.taskId}} + status: + state: TASK_STATE_COMPLETED + artifacts: + type: array + count_gte: 1
CORE-EXEC-002 Polling shows progress through working stateSends a long-running request with returnImmediately enabled, verifies polling observes TASK_STATE_WORKING during execution, and then confirms the task reaches TASK_STATE_COMPLETED. +
message: + role: ROLE_USER + parts: + - text: tck-long-running start process + configuration: + returnImmediately: true
status: 200 + body: + task: + status: + state: + one_of: + - TASK_STATE_SUBMITTED + - TASK_STATE_WORKING
taskId: task.id
id: {{start.taskId}}
status: 200 + body: + status: + state: + type: string
until: status.state == TASK_STATE_WORKING + max_attempts: 10 + delay_ms: 1000
id: {{start.taskId}}
status: 200 + body: + status: + state: + type: string
until: status.state in [TASK_STATE_COMPLETED, TASK_STATE_FAILED] + max_attempts: 15 + delay_ms: 2000
id: {{start.taskId}}
status: 200 + body: + id: {{start.taskId}} + status: + state: TASK_STATE_COMPLETED
PUSH-CFG-001 Set push notification configCreates a task, configures push notifications for it, and verifies the returned configuration uses the requested webhook URL. +
capabilities: + pushNotifications: true
message: + role: ROLE_USER + parts: + - text: tck-complete-task for push
status: 200 + body: + task: + id: + type: string
taskId: task.id
taskId: {{create.taskId}} + pushNotificationConfig: + url: {{webhookUrl}}
status: 200 + body: + id: + type: string + url: {{webhookUrl}}
configId: id
PUSH-CFG-002 Get push notification configCreates a task, stores a push notification configuration, retrieves it, and verifies the previously set configuration is returned. +
capabilities: + pushNotifications: true
message: + role: ROLE_USER + parts: + - text: tck-complete-task for push
status: 200 + body: + task: + id: + type: string
taskId: task.id
taskId: {{create.taskId}} + pushNotificationConfig: + url: {{webhookUrl}}
status: 200 + body: + id: + type: string
configId: id
taskId: {{create.taskId}} + id: {{set-config.configId}}
status: 200 + body: + id: {{set-config.configId}} + url: {{webhookUrl}}
PUSH-CFG-003 Delete push notification configCreates a task, stores a push notification configuration, deletes it, and expects a successful deletion response. +
capabilities: + pushNotifications: true
message: + role: ROLE_USER + parts: + - text: tck-complete-task for push
status: 200 + body: + task: + id: + type: string
taskId: task.id
taskId: {{create.taskId}} + pushNotificationConfig: + url: {{webhookUrl}}
status: 200 + body: + id: + type: string
configId: id
taskId: {{create.taskId}} + id: {{set-config.configId}}
status: 200
PUSH-CFG-004 Push config on unsupported server returns errorCreates a task on a server that does not advertise push notification support, then verifies setting a push notification configuration fails. +
capabilities: + pushNotifications: false
message: + role: ROLE_USER + parts: + - text: tck-complete-task for push
status: 200 + body: + task: + id: + type: string
taskId: task.id
taskId: {{create.taskId}} + pushNotificationConfig: + url: {{webhookUrl}}
code: UnsupportedOperationError
PUSH-LIST-001 List push configscapabilities: + pushNotifications: true
message: + role: ROLE_USER + parts: + - text: tck-complete-task for push
status: 200 + body: + task: + id: + type: string
taskId: task.id
taskId: {{create.taskId}} + pushNotificationConfig: + url: {{webhookUrl}}
status: 200 + body: + id: + type: string
configId: id
taskId: {{create.taskId}}
status: 200 + body: + configs: + type: array + count_gte: 1
PUSH-ERR-001 Get nonexistent push config returns errorcapabilities: + pushNotifications: true
message: + role: ROLE_USER + parts: + - text: tck-complete-task for push
status: 200 + body: + task: + id: + type: string
taskId: task.id
taskId: {{create.taskId}} + id: 00000000-0000-0000-0000-000000000000
code: TaskNotFoundError
PUSH-IDEM-001 Delete push config is idempotentcapabilities: + pushNotifications: true
message: + role: ROLE_USER + parts: + - text: tck-complete-task for push
status: 200 + body: + task: + id: + type: string
taskId: task.id
taskId: {{create.taskId}} + pushNotificationConfig: + url: {{webhookUrl}}
status: 200 + body: + id: + type: string
configId: id
taskId: {{create.taskId}} + id: {{set-config.configId}}
status: 200
taskId: {{create.taskId}} + id: {{set-config.configId}}
status: 200
PUSH-DELIV-001 Push delivery includes authRunner MUST set up a webhook endpoint and verify auth credentials are included.
capabilities: + pushNotifications: true
message: + role: ROLE_USER + parts: + - text: tck-long-running start + configuration: + returnImmediately: true
status: 200 + body: + task: + id: + type: string
taskId: task.id
taskId: {{create.taskId}} + pushNotificationConfig: + url: {{webhookUrl}} + authentication: + scheme: Bearer + credentials: test-token
status: 200 + body: + id: + type: string
PUSH-DELIV-002 Push delivery is at-least-onceRunner MUST set up a webhook endpoint and verify at-least-once delivery semantics.
capabilities: + pushNotifications: true
message: + role: ROLE_USER + parts: + - text: tck-long-running start + configuration: + returnImmediately: true
status: 200 + body: + task: + id: + type: string
taskId: task.id
taskId: {{create.taskId}} + pushNotificationConfig: + url: {{webhookUrl}}
status: 200 + body: + id: + type: string
PUSH-DELIV-003 Push payload format correctRunner MUST set up a webhook endpoint and verify the delivered payload format matches the A2A specification.
capabilities: + pushNotifications: true
message: + role: ROLE_USER + parts: + - text: tck-long-running start + configuration: + returnImmediately: true
status: 200 + body: + task: + id: + type: string
taskId: task.id
taskId: {{create.taskId}} + pushNotificationConfig: + url: {{webhookUrl}}
status: 200 + body: + id: + type: string
Covers send_streaming_message and subscribe_to_task behaviors.
STREAM-SSE-001 SendStreamingMessage produces events ending in terminal statemessage: + role: ROLE_USER + parts: + - text: tck-stream-basic generate output
min_count: 2 + ordering: monotonic_state + final_event: + status: + state: + one_of: + - TASK_STATE_COMPLETED + - TASK_STATE_FAILED
STREAM-SSE-002 Stream includes at least one artifact updatemessage: + role: ROLE_USER + parts: + - text: tck-stream-basic with artifact
events: + - description: At least one streamed event includes an artifact payload + match: any_position + artifact: exists: true + final_event: + status: + state: TASK_STATE_COMPLETED
STREAM-SSE-003 Chunked streaming delivers multiple artifact eventsmessage: + role: ROLE_USER + parts: + - text: tck-stream-chunked multi-part
min_count: 3 + ordering: monotonic_state
STREAM-SUB-001 SubscribeToTask receives updates for existing taskmessage: + role: ROLE_USER + parts: + - text: tck-long-running start + configuration: + returnImmediately: true
task: + id: + type: string + status: + state: + one_of: + - TASK_STATE_SUBMITTED + - TASK_STATE_WORKING
taskId: task.id
id: {{start.taskId}}
final_event: + status: + state: + one_of: + - TASK_STATE_COMPLETED + - TASK_STATE_FAILED + - TASK_STATE_CANCELED + - TASK_STATE_REJECTED
STREAM-SUB-002 Subscribe stream terminates at terminal stateThe stream must close after emitting the terminal state event.
message: + role: ROLE_USER + parts: + - text: tck-stream-basic test
final_event: + status: + state: + one_of: + - TASK_STATE_COMPLETED + - TASK_STATE_FAILED + - TASK_STATE_CANCELED
STREAM-SUB-003 Subscribe to terminal task returns errormessage: + role: ROLE_USER + parts: + - text: tck-complete-task setup
task: + id: + type: string + status: + state: + one_of: + - TASK_STATE_COMPLETED + - TASK_STATE_FAILED + - TASK_STATE_CANCELED + - TASK_STATE_REJECTED
taskId: task.id
id: {{setup.taskId}}
error: + exists: true
STREAM-SSE-004 First event on subscribe is current task statemessage: + role: ROLE_USER + parts: + - text: tck-long-running start + configuration: + returnImmediately: true
status: 200 + body: + task: + id: + type: string
taskId: task.id
id: {{start.taskId}}
events: + - description: First event represents the current task state + index: 0 + one_of: - task: status: + exists: true + - status_update: status: + exists: true
STREAM-MSG-001 Streaming message-only responsemessage: + role: ROLE_USER + parts: + - text: tck-message-response streaming
min_count: 1 + final_event: + message: + exists: true
STREAM-MULTI-001 Multiple concurrent streams receive same eventsRunner MUST open two concurrent streams and verify both receive the same events. This test may require special runner support.
message: + role: ROLE_USER + parts: + - text: tck-stream-basic generate output
min_count: 2
STREAM-MULTI-002 Closing one stream doesn't affect othersRunner MUST open two concurrent streams, close one of them mid-stream, and verify the other continues receiving events. This test may require special runner support.
message: + role: ROLE_USER + parts: + - text: tck-stream-basic generate output
min_count: 2
STREAM-RESUB-001 Resubscribe after disconnectRunner MUST disconnect from stream mid-flight and resubscribe. This test may require special runner support.
message: + role: ROLE_USER + parts: + - text: tck-long-running start + configuration: + returnImmediately: true
status: 200 + body: + task: + id: + type: string
taskId: task.id
id: {{start.taskId}}
min_count: 1
JSONRPC-ENV-001 Response has valid JSON-RPC 2.0 envelopemethod: POST + path: / + headers: + Content-Type: application/json + A2A-Version: 1.0 + body: + jsonrpc: 2.0 + id: jsonrpc-env-001 + method: SendMessage + params: + message: + role: ROLE_USER + parts: + - text: tck-complete-task verify jsonrpc envelope
status: 200 + body: + jsonrpc: 2.0 + id: jsonrpc-env-001 + result: + exists: true
JSONRPC-CT-001 Response Content-Type is application/jsonACTS cannot reliably assert response headers in this raw format, so the test uses a valid JSON-RPC body as a proxy for the expected application/json response.
method: POST + path: / + headers: + Content-Type: application/json + A2A-Version: 1.0 + body: + jsonrpc: 2.0 + id: jsonrpc-ct-001 + method: SendMessage + params: + message: + role: ROLE_USER + parts: + - text: tck-complete-task verify content type
status: 200 + body: + jsonrpc: 2.0 + id: jsonrpc-ct-001 + result: + exists: true
JSONRPC-SSE-001 SSE streaming events have JSON-RPC envelopemethod: POST + path: / + headers: + Content-Type: application/json + Accept: text/event-stream + A2A-Version: 1.0 + body: + jsonrpc: 2.0 + id: jsonrpc-sse-001 + method: SendStreamingMessage + params: + message: + role: ROLE_USER + parts: + - text: tck-stream-basic generate output
status: 200
min_count: 2 + each_event: + jsonrpc: 2.0
REST-STATUS-001 REST errors map to correct HTTP status codesmethod: GET + path: /tasks/nonexistent-id + headers: + Accept: application/json + A2A-Version: 1.0
status: 404
REST-PD-001 REST errors use problem details formatmethod: GET + path: /tasks/nonexistent-id + headers: + Accept: application/json + A2A-Version: 1.0
status: 404 + body: + type: + type: string + title: + type: string + status: + type: number
REST-CT-001 REST responses use application/a2a+json content typeRunner SHOULD verify the Content-Type response header is application/a2a+json for REST responses.
message: + role: ROLE_USER + parts: + - text: tck-complete-task verify rest content type
status: 200 + body: + task: + id: + type: string + status: + state: TASK_STATE_COMPLETED
GRPC-STATUS-001 gRPC errors map to correct status codesVerifies that missing-task errors surface through the gRPC binding with the expected status semantics (for example, NOT_FOUND) even though the ACTS assertion is expressed as an abstract TaskNotFoundError.
id: 00000000-0000-0000-0000-000000000000
code: TaskNotFoundError
GRPC-STREAM-001 gRPC streaming delivers proper message structuremessage: + role: ROLE_USER + parts: + - text: tck-stream-basic generate output
min_count: 2
GRPC-STREAM-002 gRPC streaming cancellation worksmessage: + role: ROLE_USER + parts: + - text: tck-cancel start + configuration: + returnImmediately: true
status: 200 + body: + task: + id: + type: string + status: + state: + one_of: + - TASK_STATE_SUBMITTED + - TASK_STATE_WORKING
taskId: task.id
id: {{start.taskId}}
status: 200 + body: + id: {{start.taskId}} + status: + state: TASK_STATE_CANCELED
Coverage for unsupported and omitted A2A-Version header handling.
VER-NEG-001 Unsupported A2A-Version returns VersionNotSupportedErrorVerifies that a JSON-RPC request with an unsupported A2A-Version header is rejected.
method: POST + path: / + headers: + Content-Type: application/json + A2A-Version: 99.0 + body: + jsonrpc: 2.0 + id: ver-neg-001 + method: SendMessage + params: + message: + role: ROLE_USER + parts: + - text: version negotiation unsupported
status: 200 + body: + error: + code: -32009 + message: + type: string
VER-NEG-002 Missing A2A-Version is treated as defaultVerifies that a JSON-RPC request without an A2A-Version header succeeds using the server's default version behavior.
method: POST + path: / + headers: + Content-Type: application/json + body: + jsonrpc: 2.0 + id: ver-neg-002 + method: SendMessage + params: + message: + role: ROLE_USER + parts: + - text: tck-complete-task version default
status: 200 + body: + result: + task: + id: + type: string
DM-FMT-001 Wire format uses camelCase field namesSends a raw JSON-RPC SendMessage request and verifies the wire-format response does not expose snake_case field names. +
method: POST + path: / + headers: + Content-Type: application/json + A2A-Version: 1.0 + body: + jsonrpc: 2.0 + id: wire-format-001 + method: SendMessage + params: + message: + role: ROLE_USER + parts: + - text: tck-complete-task verify wire format
status: 200 + body: + result: + task: + id: + type: string + context_id: + absent: true + message_id: + absent: true + task_id: + absent: true + artifact_id: + absent: true + status_update: + absent: true + artifact_update: + absent: true + protocol_version: + absent: true + media_type: + absent: true
DM-FMT-002 Enum values use prefixed formatVerifies enum values are returned using the prefixed wire-format names for message roles and task states. +
message: + role: ROLE_USER + parts: + - text: tck-message-response check role
status: 200 + body: + message: + role: ROLE_AGENT
message: + role: ROLE_USER + parts: + - text: tck-complete-task check state
status: 200 + body: + task: + status: + state: TASK_STATE_COMPLETED
DM-FMT-003 Default and empty values are omitted from wireVerifies message responses omit default taskId and contextId fields, or at minimum never serialize them as empty strings. +
message: + role: ROLE_USER + parts: + - text: tck-message-response test defaults
status: 200 + body: + message: + role: ROLE_AGENT + taskId: + absent: true + contextId: + absent: true