-
Notifications
You must be signed in to change notification settings - Fork 130
Conversation
- introduce `MonitorableKeyValueStorage` - factorise code - remove metrics instanciation in `RocksDbKeyValueStorage` and `ColumnarRocksDbKeyValueStorage`
- use final modifiers when appropriate to comply with Pantheon global policy - use `assertj` assertions in tests - don't use local variables when not necessary - check exception message for `upCheck` method
integrationTestImplementation 'junit:junit' | ||
integrationTestImplementation 'org.assertj:assertj-core' |
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.
what is the reason for using assertj over junit?
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.
Readability of the code mainly, it looks more a human natural semantic. Easier to read for non tech people for example. Also we try to use it in the rest of the code when possible. So also for harmonization.
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
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
PR description
assertj
assertions in testsupCheck
methodFixed Issue(s)