Skip to content

LITE-33583: Refresh OpenAPI spec fixture to v37.0#87

Open
pcaro wants to merge 1 commit into
masterfrom
cr/LITE-33583-update-spec
Open

LITE-33583: Refresh OpenAPI spec fixture to v37.0#87
pcaro wants to merge 1 commit into
masterfrom
cr/LITE-33583-update-spec

Conversation

@pcaro

@pcaro pcaro commented Jul 1, 2026

Copy link
Copy Markdown
Contributor

What

Replace the bundled OpenAPI spec test fixture (tests/data/specs.yml) — a v22.0 snapshot from 2021 — with the current live spec v37.0 from https://apispec.connect.cloudblue.com/connect-openapi30.yml, and update the affected introspection assertions in tests/client/test_openapi.py.

Why

The fixture drove the OpenAPISpecs introspection tests against a 4-year-old API structure. Refreshing it makes those tests validate against the API's real, current shape. No client code changes: the client is spec-agnostic (generic fluent interface) and only loads the spec for optional help/validation.

Assertion changes

  • get_namespaces: 11 → 21 (new: billing, catalog, custom, devops, embed, leads, localization, modules, offers-ns, pim, statistics)
  • get_collections: 18 → 29 (acl, brand(s), conversations, domains, folders, idps, metrics, news, portal, sla, sli, …)
  • get_actions('products/PRD-000'): now includes the taxonomies sub-paths (existing parser behavior, just more data in the spec)
  • get_nested_collections('products/PRD-000'): agreements dropped; guidelines, item-groups, messages, taxonomies added

Verification

uv run pytest → 407 passed.

🤖 Generated with Claude Code

The bundled OpenAPI spec fixture (tests/data/specs.yml) was a v22.0
snapshot from 2021. Replace it with the current live spec (v37.0) from
https://apispec.connect.cloudblue.com/connect-openapi30.yml so the
introspection tests validate against the API's real, current structure.

Update the exact-match assertions in test_openapi.py whose expected
values changed with the new spec: get_namespaces (11 -> 21),
get_collections (18 -> 29), get_actions and get_nested_collections for
products. No client code changes: the client is spec-agnostic and only
loads the spec for optional help/validation.
@sonarqubecloud

sonarqubecloud Bot commented Jul 1, 2026

Copy link
Copy Markdown

@pcaro pcaro requested a review from akodelia July 1, 2026 11:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant