Skip to content

[GrantFox][Medium] Enforce OpenAPI runtime contract tests #1150

Description

@greatest0fallt1me

Summary

Enforce OpenAPI runtime contract tests

Why this matters

The generated API specification can diverge from validation and serialization.

Scope

Validate documented requests and responses for auth, billing, webhook, and proxy routes in CI.

Acceptance criteria

  • Required fields and enum constraints are enforced.
  • Success and error responses validate against schemas.
  • Generated output is checked for drift.
  • Contract tests run on every CI build.

Validation

Add regression coverage for existing behavior, failure modes, authorization boundaries, and compatibility. The implementation must pass the repository CI checks.

Non-goals

  • Typo-only, formatting-only, or documentation-only changes.
  • Unrelated refactors or dependency upgrades.
  • Weakening existing security, authorization, CI, or production safeguards.

Contributor application

Before implementation, comment with relevant experience, a 1–4 bullet approach, and an estimate for opening the first draft PR. Wait for maintainer assignment before coding.

PR requirements

Use a feature branch, include Closes #<issue-number>, check every acceptance criterion, link criteria to code/tests, explain security and failure-mode considerations, and pass CI.

Reward-readiness

This is a substantive GrantFox campaign issue. Merge and CI success do not by themselves guarantee reward eligibility; final reward-readiness is determined by campaign review.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions