Add integration tests for exp module#168
Merged
Merged
Conversation
aisk
force-pushed
the
exp-integration-tests
branch
from
July 19, 2026 03:15
8202f99 to
b66f886
Compare
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.
The exp clients were only covered by unit tests against a scripted in-process server; add integration tests running against a real memcached.
tests/test_exp.rs: set/get/delete, store modes, CAS flow (includingunless_cas), arithmetic with vivify, item metadata, binary keys (base64 path),run_batch, the full lease flow andmedebug, plus an async roundtrip behind thetokiofeaturert+macros) for#[tokio::test]--all-features, covering the tokio tests in the same step