Skip to content
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

Correct meaning of "actual" and "expected" #4

Merged
merged 4 commits into from
Sep 4, 2017
Merged

Correct meaning of "actual" and "expected" #4

merged 4 commits into from
Sep 4, 2017

Conversation

iamvery
Copy link
Owner

@iamvery iamvery commented Sep 4, 2017

This is so hard to keep straight in my head... 😅

There's actually a bug in the matcher implementation. These names along
with some additional information should bring it to light...
This serves to highlight the bug mentioned in the previous commit. Fakes
should be able to have _additional_ behavior, however this test now
fails. That is because I got the order of things reversed in the matcher
implementation.
It's been really hard to get my head around this.. the "actual" is the
_VALUE BEING TESTED_. The "expected" is the _VALUE BE TESTED AGAINST_. I
suppose it's hard to grok, because the "actual" is the value given to
`expect()`...
@iamvery iamvery changed the title Correct meaning of "actual" and Correct meaning of "actual" and "expected" Sep 4, 2017
@iamvery iamvery merged commit c2d6a52 into master Sep 4, 2017
@iamvery iamvery deleted the fix branch September 4, 2017 14:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant