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

Enable true validation of :actual values in kerodon.unit.test #29

Merged
merged 1 commit into from
Dec 14, 2014
Merged

Conversation

jayp
Copy link
Contributor

@jayp jayp commented Dec 14, 2014

When test cases did not result in :error, the :actual values were not being
validated due to a misplaced parenthesis! Can you spot the error? Ha ha!

As part of this changeset, also fixed minor issues in expected :actual values.
I suppose no one caught these as they were not actually being executed?

Lastly, refactored check-report's map parameter to expect :valiator-fn key to
provide a function to validate the :actual value for :error cases. Overloading
the :actual key for both a function (in :error cases) and a value (otherwise)
was a bit confusing.

When test cases did not result in :error, the :actual values were not being
validated due to a misplaced parenthesis! Can you spot the error? Ha ha!

As part of this changeset, also fixed minor issues in expected :actual values.
I suppose no one caught these as they were not actually being executed?

Lastly, refactored check-report's map parameter to expect :valiator-fn key to
provide a function to validate the :actual value for :error cases. Overloading
the :actual key for both a function (in :error cases) and a value (otherwise)
was a bit confusing.
@glenjamin
Copy link
Collaborator

Oh wow, good spot!

glenjamin added a commit that referenced this pull request Dec 14, 2014
Enable true validation of :actual values in kerodon.unit.test
@glenjamin glenjamin merged commit 71fd25d into xeqi:master Dec 14, 2014
@jayp
Copy link
Contributor Author

jayp commented Dec 14, 2014

Thanks @glenjamin. Noticed this issue when an in-development test I wrote for PR #30 passed, when it shouldn't have!

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.

2 participants