Skip to content

Commit 2857a07

Browse files
authored
chore: Use strict TCK mode (a2aproject#457)
The possibility to do this was introduced in a2aproject/a2a-tck#92. Without this, we would get TCK runs reported as passing, despite failures in the capabilities/features tests.
1 parent f8f792d commit 2857a07

1 file changed

Lines changed: 5 additions & 1 deletion

File tree

.github/workflows/run-tck.yml

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,8 +14,12 @@ on:
1414

1515
env:
1616
# TODO this is currently running the TCK off the main branch which included changes needed for 0.4.0
17-
# Tag of the TCK
17+
# Tag/branch of the TCK
1818
TCK_VERSION: main
19+
# Tell the TCK runner to report failure if the quality tests fail
20+
A2A_TCK_FAIL_ON_QUALITY: 1
21+
# Tell the TCK runner to report failure if the features tests fail
22+
A2A_TCK_FAIL_ON_FEATURES: 1
1923
# Tells uv to not need a venv, and instead use system
2024
UV_SYSTEM_PYTHON: 1
2125
# SUT_JSONRPC_URL to use for the TCK and the server agent

0 commit comments

Comments
 (0)