pytest integration tests with response shape validation #3

Closed
opened 2026-03-01 04:45:55 +00:00 by forgejo_admin · 0 comments
Contributor

Plan

plan-2026-02-28-woodpecker-sdk-mcp — Phase 1 follow-up

Repo

woodpecker-sdk

User Story

As an SDK consumer
I need integration tests that validate response shapes from every endpoint
So that I can trust the SDK returns correct, typed data and catch API regressions early

Acceptance Criteria

When I run pytest tests/ against a live Woodpecker instance
Then every endpoint test validates required fields, field types, nested object structure, and list vs dict response shapes

Additional Information

Current tests are smoke-level (assert isinstance). Upgrade to validate response schemas from swagger.json — field presence, types, constraints. See pal-e-docs issue-woodpecker-sdk-integration-tests for full details and example patterns.

Checklist

  • PR opened with related notes
  • Tests cover the acceptance criteria
  • Docs updated if needed
  • claude-config — project
  • plan-2026-02-28-woodpecker-sdk-mcp — parent plan
  • issue-woodpecker-sdk-integration-tests — pal-e-docs issue
### Plan `plan-2026-02-28-woodpecker-sdk-mcp` — Phase 1 follow-up ### Repo `woodpecker-sdk` ### User Story As an SDK consumer I need integration tests that validate response shapes from every endpoint So that I can trust the SDK returns correct, typed data and catch API regressions early ### Acceptance Criteria When I run `pytest tests/` against a live Woodpecker instance Then every endpoint test validates required fields, field types, nested object structure, and list vs dict response shapes ### Additional Information Current tests are smoke-level (assert isinstance). Upgrade to validate response schemas from swagger.json — field presence, types, constraints. See pal-e-docs `issue-woodpecker-sdk-integration-tests` for full details and example patterns. ### Checklist - [ ] PR opened with related notes - [ ] Tests cover the acceptance criteria - [ ] Docs updated if needed ### Related - `claude-config` — project - `plan-2026-02-28-woodpecker-sdk-mcp` — parent plan - `issue-woodpecker-sdk-integration-tests` — pal-e-docs issue
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
ldraney/woodpecker-sdk#3
No description provided.