[
https://issues.apache.org/jira/browse/KAFKA-19097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18041160#comment-18041160
]
Ibuki Kaji commented on KAFKA-19097:
------------------------------------
Hi [~ksolves.kafka]
Following up on my previous message — I went ahead and opened a PR to address
the remaining parts related to this issue.
You can find it here: [https://github.com/apache/kafka/pull/21012]
If it’s difficult for you to take care of the remaining items, I’m totally
happy to handle them on my side, so please feel free to let me know.
> Fix order of arguments to assertEquals
> --------------------------------------
>
> Key: KAFKA-19097
> URL: https://issues.apache.org/jira/browse/KAFKA-19097
> Project: Kafka
> Issue Type: Improvement
> Components: streams, unit tests
> Reporter: Lorcan
> Assignee: Ksolves India Limited
> Priority: Minor
> Labels: beginner-friendly, newbie,
>
> There are examples of tests using assertEquals where the arguments are in the
> wrong order.
> Example from InternalStreamsBuilderTest:
> assertEquals(count.get(), 3);
> The expected value should be the first argument.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
