From 41ace0ea9bf2e8c49be4c623ed5945ee06f72256 Mon Sep 17 00:00:00 2001 From: slayerjain Date: Fri, 16 Oct 2026 13:30:50 +0530 Subject: [PATCH] docs: say that --strict fails only on a call that missed its recorded 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 --- .../version-4.0.0/running-keploy/mock-your-tests.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/versioned_docs/version-4.0.0/running-keploy/mock-your-tests.md b/versioned_docs/version-4.0.0/running-keploy/mock-your-tests.md index 0199e2c47..e526e95f1 100644 --- a/versioned_docs/version-4.0.0/running-keploy/mock-your-tests.md +++ b/versioned_docs/version-4.0.0/running-keploy/mock-your-tests.md @@ -75,8 +75,10 @@ When an outgoing call matches no recorded mock, `--on-miss` decides what happens keploy mock replay -c "pytest" --on-miss record ``` -Add `--strict` to fail the run if any _recorded_ mock was **missed** (a dependency -contract drifted), even when the tests themselves passed. +Add `--strict` to fail the run if a call **missed** its recorded mock (a dependency +contract drifted), even when the tests themselves passed. A DNS lookup with no +recorded mock (Keploy answers it itself), or a connection whose client sent +nothing, does not fail it by itself. ## Per-test scoping (optional)