Repository navigation
feat: add shared request record contracts - #1
Merged
Merged
Conversation
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
1 participant
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.
Request measurements currently use framework-specific dictionaries. Add a dependency-free RequestRecord v1 schema, JSON conversion and isolated RunContext storage so functional, load and synthetic results can share a contract.
Snapshots are detached, run identities validate before execution, identical retries deduplicate and conflicting JSON payloads fail. The schema and validator agree on assertion outcomes and HTTP method tokens; opaque objects, non-finite measurements and unrepresentable integers report field locations.
Validation: 184 full-suite tests passed (3 optional schema tests skipped in the core-only environment); 66 focused record/context tests passed with jsonschema available. Three README languages and cross-project architecture contracts are updated.
This is the core prerequisite for the APITestka and LoadDensity feature branches. Consumer recording is opt-in until the real core release is available; no version was changed manually.