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

Increase test coverage for config #946

Merged

Conversation

weisheme
Copy link
Contributor

@weisheme weisheme commented Oct 31, 2017

Not sure if a PR like this is appreciated at all, but at least for me writing tests is a great way to get to know the codebase. I started with org.ethereum.config and org.ethereum.config.net

I only made changes to test code. Production code is untouched.

Potentially found 3 small bugs related to configuration:

  • NodeFilterTest's acceptNullIpPatternAsCatchAllForNodes and doNotAcceptNullIpPatternAsCatchAllForInetAddresses seem to indicate a discrepancy between InetAddress and Node acceptance. Smells like a potential bug.
  • NodeFilterTest's acceptInvalidNodeHostnameWhenUsingWildcard and doNotAcceptInvalidNodeHostnameWhenUsingPattern seem to indicate a discrepancy in acceptance logic. Smells like a potential bug.
  • SystemPropertiesTest's testExposeBugWhereNonHexEncodedIsAcceptedWithoutValidation seems to indicate that private key validation is not correct.

@coveralls
Copy link

Coverage Status

Coverage increased (+0.6%) to 59.825% when pulling 2d8b83c on weisheme:increase_test_coverage_for_config into 9d1fdaa on ethereum:develop.

@weisheme weisheme force-pushed the increase_test_coverage_for_config branch from 2d8b83c to eedc520 Compare October 31, 2017 20:26
@coveralls
Copy link

Coverage Status

Coverage increased (+0.8%) to 59.96% when pulling eedc520 on weisheme:increase_test_coverage_for_config into 9d1fdaa on ethereum:develop.

- NodeFilterTest's acceptNullIpPatternAsCatchAllForNodes and doNotAcceptNullIpPatternAsCatchAllForInetAddresses seem to indicate a discrepancy between InetAddress and Node acceptance. Smells like a potential bug.
- NodeFilterTest's acceptInvalidNodeHostnameWhenUsingWildcard and doNotAcceptInvalidNodeHostnameWhenUsingPattern seem to indicate a discrepancy in acceptance logic. Smells like a potential bug.
- SystemPropertiesTest's testExposeBugWhereNonHexEncodedIsAcceptedWithoutValidation seems to indicate that private key validation is not correct.
@weisheme weisheme force-pushed the increase_test_coverage_for_config branch from eedc520 to 09f7688 Compare November 2, 2017 13:21
@coveralls
Copy link

Coverage Status

Coverage increased (+0.8%) to 59.96% when pulling 09f7688 on weisheme:increase_test_coverage_for_config into 9d1fdaa on ethereum:develop.

@Nashatyrev
Copy link
Member

Cool! Many thanks! Additional tests are always welcome!
Created an issue on your foundings.
Please feel free to go on and take it for the fix ;)

@Nashatyrev Nashatyrev merged commit c0f44ce into ethereum:develop Dec 1, 2017
@weisheme weisheme deleted the increase_test_coverage_for_config branch December 3, 2017 19:31
mkalinin added a commit that referenced this pull request Jun 14, 2018
#946 - Fixes for small configuration bugs found by tests
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.

3 participants