-
Notifications
You must be signed in to change notification settings - Fork 2
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
split to subprojects, core and test utils #28
Conversation
sim-test-utils/src/main/kotlin/com/exactpro/th2/sim/template/rule/test/api/TestRuleContext.kt
Show resolved
Hide resolved
import java.util.concurrent.ScheduledExecutorService | ||
import java.util.concurrent.TimeUnit | ||
|
||
class TestRuleContext : IRuleContext { |
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.
Could we use the mockito library instead?
|
||
fun assertEqualsMessages(expected: Message, actual: Message, lazyMessage: () -> String? = {null}) { | ||
val assertExpected = expected.toBuilder().apply { | ||
metadataBuilder.timestampBuilder.resetTimestamp() |
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.
Maybe set the Timestamp.getDefaultInstance() instead of custom method to resetTimestamp
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.
isn't result of this will be same, default timestamp gonna set time of creation point and we just gonna set both messages to same link of timestamp. Current realization seting both of them to same point too but zeroes.
No description provided.