-
Notifications
You must be signed in to change notification settings - Fork 26
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
feat: Add unit tests for entity\history classes #244
Conversation
Signed-off-by: Oleg Kopysov <[email protected]>
assertFalse(entity1.equals(entity2)); | ||
assertFalse(entity2.equals(entity1)); | ||
} | ||
} |
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.
Please add empty line
assertFalse(history1.equals(history2)); | ||
assertFalse(history2.equals(history1)); | ||
} | ||
} |
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.
same here
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.
Thanks for increasing coverage. Approved
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.
LGTM
Signed-off-by: Oleg Kopysov <[email protected]>
Description
We have to cover more classes by unit tests to improve code coverage.
In this PR
entity\history
classes are covered by additional unit tests.Type of change
Please delete options that are not relevant.
Checklist: