Repository navigation
docs: say that --strict fails only on a call that missed its recorded mock - #929
Draft
slayerjain wants to merge 1 commit into
Draft
slayerjain wants to merge 1 commit into
slayerjain wants to merge 1 commit into
Conversation
… mock keploy mock replay --strict now fails a run only on a miss that counts against a test. A DNS lookup no recorded mock matched, which Keploy's proxy answers itself, does not fail it on its own. Neither does a connection whose client sent nothing, such as a dependency's TCP health check. The mock page still said --strict fails the run "if any recorded mock was missed". It now says what --strict counts. Signed-off-by: slayerjain <shubhamkjain@outlook.com>
slayerjain
force-pushed
the
docs/strict-counts-calls-only
branch
from
October 16, 2026 08:28
11c3e7e to
41ace0e
Compare
This branch has not been deployed
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.
What has changed?
keploy mock replay --strictnow fails a run only when a call missed its recorded mock. A DNS lookup Keploy could not answer does not fail it on its own, because the proxy answers that lookup itself. A connection whose client sent nothing (for example, a dependency's TCP health check) does not fail it either. The "Mock your tests" page still said--strictfails the run "if any recorded mock was missed". This PR updates that sentence to say what--strictcounts.This follows the keploy change that has
--strictusemodels.UnmatchedCall.CountsAgainstTest(keploy branchtrain/fix/mock-strict-counts). Merge it once that change is released.Type of change
How Has This Been Tested?
npx prettier@2.8.8 --checkpasses on the edited page. The change is one paragraph of prose, with no new frontmatter, links or components.Checklist: