[
https://issues.apache.org/jira/browse/KAFKA-19097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18019539#comment-18019539
]
HongYi Chen commented on KAFKA-19097:
-------------------------------------
[~mjsax]
Sorry for the confusion. I’d like to clarify that although the JIRA was
initially assigned to me, another contributor opened a PR shortly afterwards.
To avoid duplication, I didn’t continue with my own implementation.
Unfortunately, that PR has since stalled, which delayed progress. I’d be happy
to help review once [~ksolves.kafka] picks this up. :)
> 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)
