You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I had searched in the issues and found no similar issues.
Enhancement Request
Located at:
eventmesh-runtime/src/test/java/org/apache/eventmesh/runtime/boot/EventMeshServerTest.java line 63-87
analysis and explanation:
The standard assertions library methods such as org.junit.Assert.assertEquals, and org.junit.Assert.assertSame expect the first argument to be the expected value and the second argument to be the actual value. For AssertJ, it’s the other way around, the argument of org.assertj.core.api.Assertions.assertThat is the actual value, and the subsequent calls contain the expected values. Swap them, and your test will still have the same outcome (succeed/fail when it should) but the error messages will be confusing.
Describe the solution you'd like
Swap actual and expected values.
Are you willing to submit PR?
Yes I am willing to submit a PR!
The text was updated successfully, but these errors were encountered:
Alonexc
changed the title
[Enhancement] Swap these 2 arguments so they are in the correct order: expected value, actual value.[ EventMeshServerTest]
[Enhancement] Swap these 2 arguments so they are in the correct order: expected value, actual value.[EventMeshServerTest]
Mar 22, 2023
…: expected value, actual value.[EventMeshServerTest] (#4486)
* Swap these 2 arguments so they are in the correct order: expected value, actual value.[EventMeshServerTest]
* fix code style
Search before asking
Enhancement Request
Located at:
eventmesh-runtime/src/test/java/org/apache/eventmesh/runtime/boot/EventMeshServerTest.java line 63-87
analysis and explanation:
The standard assertions library methods such as org.junit.Assert.assertEquals, and org.junit.Assert.assertSame expect the first argument to be the expected value and the second argument to be the actual value. For AssertJ, it’s the other way around, the argument of org.assertj.core.api.Assertions.assertThat is the actual value, and the subsequent calls contain the expected values. Swap them, and your test will still have the same outcome (succeed/fail when it should) but the error messages will be confusing.
Describe the solution you'd like
Swap actual and expected values.
Are you willing to submit PR?
The text was updated successfully, but these errors were encountered: