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

Allow parameters in custom test functions #64

Conversation

lordjabez
Copy link
Contributor

This is to address issue #63.

assert query({'val': 5})
assert not query({'val': 0})
assert not query({'val': 11})
assert not query({'val': '44'})
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You're using a string for 44, not an int. This breaks the tests for Python3 and PyPy3 (see https://travis-ci.org/msiemens/tinydb/builds/68895961).

@msiemens
Copy link
Owner

There's a tiny mistake in a test, but otherwise it looks good!

@lordjabez
Copy link
Contributor Author

Should I just remove that test? I only included the string comparison because there was a similar one for the previous test case.

@lordjabez
Copy link
Contributor Author

Ahh, I see the issue now. I'll simply remove the test.

@lordjabez lordjabez force-pushed the feature/arbitrary-parameters-for-custom-test branch from 235902d to 9f55011 Compare June 30, 2015 16:52
msiemens added a commit that referenced this pull request Jul 4, 2015
…r-custom-test

Allow parameters in custom test functions
@msiemens msiemens merged commit 10a93cd into msiemens:master Jul 4, 2015
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