-
-
Notifications
You must be signed in to change notification settings - Fork 158
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.
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
Fail fast if invocation matches never expectation #679
Open
floehopper
wants to merge
1
commit into
main
Choose a base branch
from
expectation-with-never-cardinality-should-fail-fast-if-invoked
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Fail fast if invocation matches never expectation #679
floehopper
wants to merge
1
commit into
main
from
expectation-with-never-cardinality-should-fail-fast-if-invoked
Conversation
This file contains 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
floehopper
force-pushed
the
expectation-with-never-cardinality-should-fail-fast-if-invoked
branch
from
November 7, 2024 15:39
7caf33f
to
5a214c0
Compare
floehopper
force-pushed
the
expectation-with-never-cardinality-should-fail-fast-if-invoked
branch
from
November 9, 2024 11:10
5a214c0
to
fc5898a
Compare
floehopper
added a commit
that referenced
this pull request
Nov 9, 2024
Currently when an invocation matches an expectation which does not allow invocations (i.e. `Expectation#never` has been called on it), but the invocation also matches another expectation which does allow invocations, then the test does not fail with an unexpected invocation error. In #679 I'm planning to change this behaviour so the test fails fast with an unexpected invocation error. This commit displays a deprecation warning instead to give users a chance to update their code before the actual change is made.
floehopper
force-pushed
the
expectation-with-never-cardinality-should-fail-fast-if-invoked
branch
from
November 9, 2024 14:32
fc5898a
to
ca5bf20
Compare
floehopper
added a commit
that referenced
this pull request
Nov 13, 2024
Currently when an invocation matches an expectation which does not allow invocations (i.e. `Expectation#never` has been called on it), but the invocation also matches another expectation which does allow invocations, then the test does not fail with an unexpected invocation error. In #679 I'm planning to change this behaviour so the test fails fast with an unexpected invocation error. This commit displays a deprecation warning instead to give users a chance to update their code before the actual change is made.
floehopper
force-pushed
the
expectation-with-never-cardinality-should-fail-fast-if-invoked
branch
from
November 13, 2024 14:05
ca5bf20
to
73c4ea6
Compare
floehopper
added a commit
that referenced
this pull request
Nov 24, 2024
Currently when an invocation matches an expectation which does not allow invocations (i.e. `Expectation#never` has been called on it), but the invocation also matches another expectation which does allow invocations, then the test does not fail with an unexpected invocation error. In #679 I'm planning to change this behaviour so the test fails fast with an unexpected invocation error. This commit displays a deprecation warning instead to give users a chance to update their code before the actual change is made. The new behaviour will bring the behaviour into line with what is already the case for mocks where `Mock#stub_everything` has been called as per this acceptance test [1] that was introduced in this commit [2]. [1]: https://github.com/freerange/mocha/blob/f2fa99197f35e2d2ce9554db63f6964057e29ce0/test/acceptance/expected_invocation_count_test.rb#L202-L214 [2]: d358377
floehopper
force-pushed
the
expectation-with-never-cardinality-should-fail-fast-if-invoked
branch
2 times, most recently
from
November 24, 2024 10:44
f832c55
to
b98a6dc
Compare
Previously when an invocation matched an expectation which did not allow invocations (i.e. `Expectation#never` had been called on it), but the invocation also matched another expectation which did allow invocations, then the test would not fail with an unexpected invocation error. After #681 a deprecation warning was displayed in this scenario, but now an unexpected invocation error is reported. This behaviour was confusing and had led to a number of issues being raised over the years: #44, #131, #490 & most recently #678. Previously I had thought this was a symptom of the JMock v1 dispatch behaviour (which _might_ still be true) and thus would be best addressed by adopting the JMock v2 dispatch behaviour (#173). However, having considered this specific scenario involving a "never" expectation, I've decided to try to fix it with the changes in this commit. Also the new behaviour will bring the behaviour into line with what is already the case for mocks where `Mock#stub_everything` has been called as per this acceptance test [1] that was introduced in this commit [2]. Now a test like this will fail with an unexpected invocation error: mock = mock('mock') mock.stubs(:method) mock.expects(:method).never mock.method unexpected invocation: #<Mock:mock>.method() unsatisfied expectations: - expected never, invoked once: #<Mock:mock>.method(any_parameters) satisfied expectations: - allowed any number of times, invoked never: #<Mock:mock>.method(any_parameters) Closes #678. Also addresses #490, #131 & #44. [1]: https://github.com/freerange/mocha/blob/f2fa99197f35e2d2ce9554db63f6964057e29ce0/test/acceptance/expected_invocation_count_test.rb#L202-L214 [2]: d358377
floehopper
force-pushed
the
expectation-with-never-cardinality-should-fail-fast-if-invoked
branch
from
November 24, 2024 11:17
b98a6dc
to
15985bc
Compare
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.
TODO
Mock
, and docs for any relevant methods.mocha/test/acceptance/expected_invocation_count_test.rb
Lines 202 to 214 in f899c03
Previously when an invocation matched an expectation which did not allow invocations (i.e.
Expectation#never
had been called on it), but the invocation also matched another expectation which did allow invocations, then the test would not fail with an unexpected invocation error.This was happening because neither the
if
condition wastrue
, because the "never" expectation was not returned byExpectationList#match_allowing_invocation
, but the other expectation allowing expectations was returned. ThusExpectation#invoke
was called on the latter andMock#raise_unexpected_invocation_error
was not called.This behaviour was confusing and had led to a number of issues being raised over the years: #44, #131, #490 & most recently #678. Previously I had thought this was a symptom of the JMock v1 dispatch behaviour (which might still be true) and thus would be best addressed by adopting the JMock v2 dispatch behaviour (#173). However, having considered this specific scenario involving a "never" expectation more carefully, I've decided to try to fix it with the changes in this PR.
Now a test like this will fail with an unexpected invocation error:
Closes #678. Also addresses #490, #131 & #44.