-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Modernize database tests and cleanup #579
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
Conversation
Moved TestUtils into correct directory for its package. Removed redundant tests. Reformatted some code and renamed methods for clarity.
# Conflicts: # database/src/main/java/com/firebase/ui/database/FirebaseArray.java
Signed-off-by: Alex Saveau <[email protected]> Cleanup and merge Signed-off-by: Alex Saveau <[email protected]> Cleanup Signed-off-by: Alex Saveau <[email protected]> Cleanup Signed-off-by: Alex Saveau <[email protected]>
} | ||
|
||
@Test | ||
public void testPushIncreasesSize() throws Exception { | ||
assertEquals(3, mArray.getCount()); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Was dropping this line intentional?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@CodingDoug removed it in his PR. @samtstern If you'd like I'll add it back (I'm not sure why he removed it).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It does seem a little strange to assert that the count after is "4" but not assert that it was "3" before. 4 is only correct if it's one more than the initial count.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@CodingDoug thanks for the explanation!
@CodingDoug any issues with merging in your test changes now since we all agree they are good? You can then rebase your PR and it will only contain the |
@samtstern Yeah, that's fine. I promise I'll get back to the rest of this PR some time! |
@samtstern Since it looks like #481 isn't going to be merged anytime soon, this PR gives @CodingDoug credit for his work while allowing us to move forward with modernized tests.