Files
cleveragents-core/features/tdd_a2a_sdk_dependency.feature
T
brent.edwards 6bad73bad7
CI / push-validation (pull_request) Successful in 48s
CI / helm (pull_request) Successful in 1m5s
CI / build (pull_request) Successful in 4m17s
CI / docker (pull_request) Has been skipped
CI / lint (pull_request) Successful in 4m5s
CI / typecheck (pull_request) Successful in 5m18s
CI / coverage (pull_request) Successful in 25m54s
CI / quality (pull_request) Successful in 4m19s
CI / security (pull_request) Successful in 5m10s
CI / e2e_tests (pull_request) Successful in 7m19s
CI / integration_tests (pull_request) Successful in 10m29s
CI / unit_tests (pull_request) Successful in 11m16s
CI / status-check (pull_request) Failing after 3s
fix(tests): update a2a SDK TDD test to use Client instead of A2AClient
The a2a-sdk floating constraint (>=0.3.0) in pyproject.toml allows nox's
uv pip install to resolve the latest SDK version from PyPI, bypassing
uv.lock. A newer a2a-sdk release removed the legacy A2AClient class,
causing the TDD test to fail on CI while master (which ran against an
older cached version) continued to pass.

The modern Client class (a2a.client.Client) exists in all SDK versions
including 0.3.25 (locked) and all subsequent releases. Updating the
test to check for Client instead of A2AClient makes it forward-compatible
and accurately reflects the SDK's current public API.

See follow-up issue for the architectural fix: nox should use
uv sync --frozen so that uv.lock is always respected for all packages.
2026-04-21 01:59:07 +00:00

24 lines
951 B
Gherkin

@tdd_issue @tdd_issue_2922 @tdd_issue_4178
Feature: A2A Python SDK is a declared project dependency
As a CleverAgents developer
I want the A2A Python SDK to be listed in pyproject.toml dependencies
So that the SDK is always installed and importable in any project environment
Background:
Given the pyproject.toml file exists at "pyproject.toml"
@tdd_issue @tdd_issue_4273
Scenario: a2a-sdk is listed in project dependencies
When I read the project dependencies from pyproject.toml
Then the dependency list should include a package that provides the "a2a" module
@tdd_issue @tdd_issue_4366
Scenario: a2a module is importable as a project dependency
When I attempt to import the "a2a" module
Then the import should succeed without errors
@tdd_issue @tdd_issue_4273
Scenario: a2a SDK provides the Client class
When I import "a2a.client" and access "Client"
Then the "Client" class should be available