Add baseline test harness and CI - #44
Draft
jsachs wants to merge 1 commit into
Draft
Conversation
jsachs
force-pushed
the
codex/test-harness
branch
from
August 5, 2026 00:30
66ce456 to
851556b
Compare
jsachs
marked this pull request as draft
August 5, 2026 12:27
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR adds the first automated test foundation for the Python client:
unittestcases covering configuration, the password-token happy path, request construction, JSON/text responses, and Pydantic alias serialization;The tests invoke the real
Config,_update_auth, and_callimplementations. Only the external HTTP session is replaced, so the suite is deterministic and requires no credentials or network access. A mutation check confirmed that incorrect refresh-token storage and an incorrect Bearer header are both detected.Scope and limitations
This is intentionally a baseline harness, not a complete OpenAPI compliance suite. It does not yet cover every endpoint, client-credentials and refresh flows, MFA, error handling, generated NERIS models, response schemas, or live API behavior. Those cases can be added safely after the focused fixes below land; OpenAPI drift and model-generation checks are planned as follow-up work.
Bugs identified during the test audit
The audit exposed several existing production issues, kept out of this foundation PR so each fix remains independently reviewable:
Verification