test-openai-responses

Automate end-to-end testing of the OpenAI Responses-API ingress via the local AI Gateway.

21|3|Updated May 26, 2026
One-click install
npx skills add https://github.com/AlphaBitCore/nexus-gateway --skill test-openai-responses
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-openai-responses
Source: https://github.com/AlphaBitCore/nexus-gateway/tree/main/.claude/skills/test-openai-responses
Command: npx skills add https://github.com/AlphaBitCore/nexus-gateway --skill test-openai-responses

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This test harness automates end-to-end validation of the OpenAI Responses-API ingress by sending a suite of synthetic requests through the local Nexus Gateway and verifying the resulting traffic tracking and metrics.

Core Features & Use Cases

  • Validates non-stream and SSE response paths, function-call workflows, structured outputs, and reasoning signals across the /v1/responses surface.
  • Verifies traffic_event endpoint_type, token counts, and Prometheus counters to ensure correct instrumentation.
  • Supports optional cross-format routing guards to exercise non-OpenAI providers and S6 guard behavior.

Quick Start

Run the test harness against a locally running Nexus Gateway to generate and review the Markdown report.

Frequently Asked Questions about test-openai-responses

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate end-to-end testing for the OpenAI Responses API ingress?

Automate OpenAI Responses API ingress testing by sending five hand-rolled requests through the local AI Gateway and validating traffic_event rows and Prometheus counters to verify the /v1/responses surface.

What request types does the OpenAI Responses API test harness validate?

The OpenAI Responses API test harness validates non-stream, SSE, function-call SSE, structured outputs, and reasoning arms to ensure correct instrumentation and expected HTTP shapes.

How do I verify Prometheus counters and traffic events for OpenAI API responses?

Verify Prometheus counters and traffic events by running synthetic requests through the local Nexus Gateway and checking traffic_event endpoint_type and token counts against expected diagnostic reporting.

Can I test non-OpenAI provider routing with the OpenAI Responses API test suite?

Yes, you can test non-OpenAI provider routing by enabling the optional cross-format routing guard to exercise non-OpenAI providers and verify S6 guard behavior.

Does the OpenAI Responses API test harness support CI pipeline integration?

Yes, the OpenAI Responses API test harness is applicable during CI pipelines and QA to enforce consistent test inputs, expected HTTP shapes, token parity, and surface failures for remediation.

Why are my OpenAI Responses API token counts mismatching during ingress validation?

Token count mismatches during ingress validation occur when expected HTTP shapes and token parity are not enforced, requiring diagnostic reporting from the test harness to guide remediation.