test: run the OVERRIDE spec test vectors against the full client stack#411
Draft
kinyoklion wants to merge 2 commits into
Draft
test: run the OVERRIDE spec test vectors against the full client stack#411kinyoklion wants to merge 2 commits into
kinyoklion wants to merge 2 commits into
Conversation
…655/override-spec-vectors
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.
Adds a runner for the eight test vectors published with the OVERRIDE spec, vendored verbatim under
testdata/override-vectors/with a schema-version assertion so drift in the source vectors fails loudly rather than silently changing coverage.Each vector exercises the full production stack — client gate, overlay store, evaluator, and events input — rather than a reimplementation: LaunchDarkly data is supplied by a test initializer as a full-transfer basis with a defined selector; the
initialized: falsevectors use a synchronizer that never delivers data (with no sources configured at all, the client would consider cached data available instead of applying its not-initialized handling, so an idle synchronizer is load-bearing); overrides come from the programmatic test source. Assertions follow the vectors' comparison rules: values by JSON equality, a null variation index as undefined, reasons compared only on the fields each vector specifies with the tri-stateisOverridecollapse, and the per-evaluation summary contribution checked against the captured event input.All eight vectors (precedence, uninitialized, passthrough ×2, full-evaluation, merged-view, marking, error-handling) pass.
Based on #410.
SDK-2655