-
Notifications
You must be signed in to change notification settings - Fork 497
Conversation
Random could be randomly 0 which would fail the test.
Use these build variants for specific tests.
Until refactored, it's okay to recalculate this.
Add matching binary, signature and pubkey from pod.
Kudos, SonarCloud Quality Gate passed!
|
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. Noted one small code change but it's not a must.
@@ -54,18 +66,21 @@ class VerificationKeysTest { | |||
} | |||
|
|||
companion object { | |||
private const val PUB_KEY = |
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 do you think about moving the companion object to the beginning of the class? I personally like to see all consts/companions at first of the class so I know what consts are used in the code
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.
I like the opposite, I think the constants distract from the global variables and constructor arguments.
Our goal is to follow the Kotlin code conventions which recommend companion objects at the end:
https://kotlinlang.org/docs/reference/coding-conventions.html
Description
Few tests are unreliable.
Related to singletons and build flavors.
How to test