Skip to content

docs: say that --strict fails only on a call that missed its recorded mock #929

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
slayerjain wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

docs: say that --strict fails only on a call that missed its recorded mock #929

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions versioned_docs/version-4.0.0/running-keploy/mock-your-tests.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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)

Expand Down
Loading