Refactor test cases to improve unit test quality #3302
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Hello, first PR here.
This PR improves the readability of the assert statements in unit tests by using more expressive assert methods from Python's unittest module. These changes improve code quality (avoid test smells) by:
Making the assert statements more readable. For example, it's quicker to understand assertFalse(x) than assertEquals(x, False).
Simplifying code management. For example, instead of simply saying 0.2, use the parameter name(poll_response_timeout) so that developers could only update the value in one place.
Happy to update more related issues in the test code if needed.