This content has been marked as final.
Show 2 replies
-
1. Re: Expected behavior of FQN?
jaikiran Jul 7, 2006 9:17 AM (in response to jaikiran)Had a look at the test cases and the FqnTest.java does not have a test case for this specific scenario. I added the following test case to the same:
/** * @testDesc Tests the {@link Fqn#equals(Object)} method. Two Fqn will be created, one * will use the {@link Fqn#Fqn(Object)} and the other will use {@link Fqn#fromString(String)}. * These two objects will then be checked for equality */ public void testEquals4() { String fqnPath = "a/b/c"; Fqn fqnUsingFromStringMethod = Fqn.fromString(fqnPath); Fqn fqnPassingStringToConstructor = new Fqn(fqnPath); assertTrue("Fqn created using fromString() is NOT equal to Fqn create using Fqn(Object obj) constructor", fqnUsingFromStringMethod.equals(fqnPassingStringToConstructor)); }
This test case shows that the equals() method is failing in this scenario. -
2. Re: Expected behavior of FQN?
jaikiran Jul 10, 2006 2:27 AM (in response to jaikiran)Is this behavior of Fqn correct? If yes, shouldnt this be documented through the javadocs?