Add test to verify client consistency with None topic args #985
Conversation
dylanjw
force-pushed the
dylanjw:filter-param-check
branch
5 times, most recently
from
09e57b2
to
14dd2ec
tests/integration/parity/common.py
Outdated
| @@ -97,6 +97,10 @@ def test_eth_getTransactionReceipt_unmined(self, web3, unlocked_account): | |||
| assert receipt is not None | |||
| assert receipt['blockHash'] is None | |||
|
|
|||
| def test_eth_getLogs_with_logs_none_topic_args(self, web3): | |||
| with pytest.raises(AssertionError): | |||
carver
Aug 3, 2018
Collaborator
In all the other places I can think of, we do @pytest.mark.xfail instead of this approach. Nothing wrong with this that I can think of, it's just nice to have a little more stylistic consistency.
In all the other places I can think of, we do @pytest.mark.xfail instead of this approach. Nothing wrong with this that I can think of, it's just nice to have a little more stylistic consistency.
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.
What was wrong?
Want to verify client handling of None topic parameters yields consistent match results.
How was it fixed?
Extended the getLogs test to try retrieving log matches using None values for topics.
Cute Animal Picture