-
Type:
Test
-
Status: Open
-
Priority:
Trivial
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
The first arg of org.JUnit.Assert.assertEquals() should be an expected value, and the second one should be an actual value.
void assertEquals(T expected, T actual);
http://junit.org/apidocs/org/junit/Assert.html#assertEquals(java.lang.Object, java.lang.Object)
However, there are so many violations in Hadoop, which can make a misleading message like this:
AssertionError: expected:<actual> but was:<expected>
.
Please refer to just-rough-approx.txt.
- is a parent of
-
HDFS-14897 [hadoop-hdfs] Fix order of actual and expected expression in assert statements
-
- Open
-
- is related to
-
HADOOP-16508 [hadoop-yarn-project] Fix order of actual and expected expression in assert statements
-
- Resolved
-
-
HADOOP-16509 [hadoop-mapreduce-project] Fix order of actual and expected expression in assert statements
-
- Resolved
-
-
HDFS-14897 [hadoop-hdfs] Fix order of actual and expected expression in assert statements
-
- Open
-
-
MAPREDUCE-6508 TestNetworkedJob fails consistently due to delegation token changes on RM.
-
- Resolved
-
- relates to
-
YARN-4543 TestNodeStatusUpdater.testStopReentrant fails + JUnit misusage
-
- Resolved
-