You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Kristian Waagan (JIRA)" <de...@db.apache.org> on 2006/07/04 13:44:29 UTC
[jira] Created: (DERBY-1474) Add assertEquals overloads for Blob
and Clob
Add assertEquals overloads for Blob and Clob
--------------------------------------------
Key: DERBY-1474
URL: http://issues.apache.org/jira/browse/DERBY-1474
Project: Derby
Type: Sub-task
Reporter: Kristian Waagan
Assigned to: Kristian Waagan
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-1474) Add assertEquals overloads for Blob
and Clob
Posted by "Kristian Waagan (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1474?page=all ]
Kristian Waagan updated DERBY-1474:
-----------------------------------
Component: Test
Description:
Add assertEquals(Blob,Blob) and assertEquals(Clob,Clob) to BaseJDBCTestCase.
The naming follows the JUnit scheme, and the methods throws an AssertionFailedError if the objects passed in are not equal.
Version: 10.2.0.0
10.3.0.0
> Add assertEquals overloads for Blob and Clob
> --------------------------------------------
>
> Key: DERBY-1474
> URL: http://issues.apache.org/jira/browse/DERBY-1474
> Project: Derby
> Type: Sub-task
> Components: Test
> Versions: 10.2.0.0, 10.3.0.0
> Reporter: Kristian Waagan
> Assignee: Kristian Waagan
>
> Add assertEquals(Blob,Blob) and assertEquals(Clob,Clob) to BaseJDBCTestCase.
> The naming follows the JUnit scheme, and the methods throws an AssertionFailedError if the objects passed in are not equal.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Resolved: (DERBY-1474) Add assertEquals overloads for Blob
and Clob
Posted by "Knut Anders Hatlen (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1474?page=all ]
Knut Anders Hatlen resolved DERBY-1474:
---------------------------------------
Fix Version: 10.2.0.0
Resolution: Fixed
Derby Info: (was: [Patch Available])
Committed derby-1474-1c.diff into trunk with revision 419542.
> Add assertEquals overloads for Blob and Clob
> --------------------------------------------
>
> Key: DERBY-1474
> URL: http://issues.apache.org/jira/browse/DERBY-1474
> Project: Derby
> Type: Sub-task
> Components: Test
> Versions: 10.2.0.0, 10.3.0.0
> Reporter: Kristian Waagan
> Assignee: Kristian Waagan
> Fix For: 10.2.0.0
> Attachments: derby-1474-1a.diff, derby-1474-1a.stat, derby-1474-1b.diff, derby-1474-1c.diff
>
> Add assertEquals(Blob,Blob) and assertEquals(Clob,Clob) to BaseJDBCTestCase.
> The naming follows the JUnit scheme, and the methods throws an AssertionFailedError if the objects passed in are not equal.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-1474) Add assertEquals overloads for Blob
and Clob
Posted by "Knut Anders Hatlen (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1474?page=comments#action_12419669 ]
Knut Anders Hatlen commented on DERBY-1474:
-------------------------------------------
Committed derby-1474-2b.diff into trunk with revision 419848.
> Add assertEquals overloads for Blob and Clob
> --------------------------------------------
>
> Key: DERBY-1474
> URL: http://issues.apache.org/jira/browse/DERBY-1474
> Project: Derby
> Type: Sub-task
> Components: Test
> Versions: 10.2.0.0, 10.3.0.0
> Reporter: Kristian Waagan
> Assignee: Kristian Waagan
> Fix For: 10.2.0.0
> Attachments: derby-1474-1a.diff, derby-1474-1a.stat, derby-1474-1b.diff, derby-1474-1c.diff, derby-1474-2a.diff, derby-1474-2a.stat, derby-1474-2b.diff, error-output.txt
>
> Add assertEquals(Blob,Blob) and assertEquals(Clob,Clob) to BaseJDBCTestCase.
> The naming follows the JUnit scheme, and the methods throws an AssertionFailedError if the objects passed in are not equal.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-1474) Add assertEquals overloads for Blob
and Clob
Posted by "Knut Anders Hatlen (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1474?page=comments#action_12419589 ]
Knut Anders Hatlen commented on DERBY-1474:
-------------------------------------------
Hi Kristian,
I think your approach is good. I have a couple of comments about your
BaseTestCase.generateError() method. All of them are minor and just a
matter of taste. Please ignore them if you disagree.
1) I think I would have called it throwAssertionError() and let it
throw the error, not return it. That would make it analogous to
SanityManager.THROWASSERT().
2) You don't need reflection to generate the
junit.framework.AssertionFailedError (junit.jar is in the
classpath).
3) You could also avoid the use of reflection to generate the
java.lang.AssertionError as well. To do this, you need to modify
build.xml in the same directory as BaseTestCase.java. In the second
javac clause, make this change:
- <pathelement path="${compile.classpath}"/>
+ <pathelement path="${java14compile.classpath}"/>
Then the classes will be compiled against the 1.4 libraries, but
since source="1.3" and target="1.3", they will run on 1.3 too. With
this change, generateError() could be written as simple as this:
Error error = null;
if (JVMInfo.JDK_ID <= JVMInfo.J2SE_13) {
error = new AssertionFailedError(msg + " : " + cause.getMessage());
cause.printStackTrace();
} else {
error = new AssertionError(msg);
error.initCause(cause);
}
return error;
This approach is also used in the client driver.
> Add assertEquals overloads for Blob and Clob
> --------------------------------------------
>
> Key: DERBY-1474
> URL: http://issues.apache.org/jira/browse/DERBY-1474
> Project: Derby
> Type: Sub-task
> Components: Test
> Versions: 10.2.0.0, 10.3.0.0
> Reporter: Kristian Waagan
> Assignee: Kristian Waagan
> Fix For: 10.2.0.0
> Attachments: derby-1474-1a.diff, derby-1474-1a.stat, derby-1474-1b.diff, derby-1474-1c.diff, derby-1474-2a.diff, derby-1474-2a.stat, error-output.txt
>
> Add assertEquals(Blob,Blob) and assertEquals(Clob,Clob) to BaseJDBCTestCase.
> The naming follows the JUnit scheme, and the methods throws an AssertionFailedError if the objects passed in are not equal.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-1474) Add assertEquals overloads for Blob
and Clob
Posted by "Kristian Waagan (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1474?page=all ]
Kristian Waagan updated DERBY-1474:
-----------------------------------
Derby Info: [Patch Available]
> Add assertEquals overloads for Blob and Clob
> --------------------------------------------
>
> Key: DERBY-1474
> URL: http://issues.apache.org/jira/browse/DERBY-1474
> Project: Derby
> Type: Sub-task
> Components: Test
> Versions: 10.2.0.0, 10.3.0.0
> Reporter: Kristian Waagan
> Assignee: Kristian Waagan
> Attachments: derby-1474-1a.diff, derby-1474-1a.stat
>
> Add assertEquals(Blob,Blob) and assertEquals(Clob,Clob) to BaseJDBCTestCase.
> The naming follows the JUnit scheme, and the methods throws an AssertionFailedError if the objects passed in are not equal.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-1474) Add assertEquals overloads for Blob
and Clob
Posted by "Andreas Korneliussen (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1474?page=comments#action_12419526 ]
Andreas Korneliussen commented on DERBY-1474:
---------------------------------------------
Just some minor comments (sorry I did not catch this earlier), however I guess these comments can be addressed in an additional patch:
In this while loops, the code will do a String-concatenation for each byte in the Blob:
+ int by1 = is1.read();
+ int by2 = is2.read();
+ do {
+ assertEquals("Blobs differ at index " + index,
+ by1, by2);
+ index++;
+ by1 = is1.read();
+ by2 = is2.read();
+ } while ( by1 != -1 || by2 != -1);
Maybe in this case, it is better to do a quick comparison before doing the call to assertEquals.
The other comment, is about exception handling. I find it useful to get the stack trace of SQLException and IOException.
I would propose to either print the stacktrace (using printStackTrace()), or let the method throw these exceptions.
+ } catch (IOException ioe) {
+ fail("IOException while asserting Blob equality: " +
+ ioe.getMessage());
+ }
+ } catch (SQLException sqle) {
+ fail("SQLException while asserting Clob equality: " +
+ sqle.getMessage());
+ }
> Add assertEquals overloads for Blob and Clob
> --------------------------------------------
>
> Key: DERBY-1474
> URL: http://issues.apache.org/jira/browse/DERBY-1474
> Project: Derby
> Type: Sub-task
> Components: Test
> Versions: 10.2.0.0, 10.3.0.0
> Reporter: Kristian Waagan
> Assignee: Kristian Waagan
> Fix For: 10.2.0.0
> Attachments: derby-1474-1a.diff, derby-1474-1a.stat, derby-1474-1b.diff, derby-1474-1c.diff
>
> Add assertEquals(Blob,Blob) and assertEquals(Clob,Clob) to BaseJDBCTestCase.
> The naming follows the JUnit scheme, and the methods throws an AssertionFailedError if the objects passed in are not equal.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Closed: (DERBY-1474) Add assertEquals overloads for Blob and
Clob
Posted by "Kristian Waagan (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1474?page=all ]
Kristian Waagan closed DERBY-1474:
----------------------------------
> Add assertEquals overloads for Blob and Clob
> --------------------------------------------
>
> Key: DERBY-1474
> URL: http://issues.apache.org/jira/browse/DERBY-1474
> Project: Derby
> Type: Sub-task
> Components: Test
> Versions: 10.2.0.0, 10.3.0.0
> Reporter: Kristian Waagan
> Assignee: Kristian Waagan
> Fix For: 10.2.0.0
> Attachments: derby-1474-1a.diff, derby-1474-1a.stat, derby-1474-1b.diff, derby-1474-1c.diff, derby-1474-2a.diff, derby-1474-2a.stat, derby-1474-2b.diff, error-output.txt
>
> Add assertEquals(Blob,Blob) and assertEquals(Clob,Clob) to BaseJDBCTestCase.
> The naming follows the JUnit scheme, and the methods throws an AssertionFailedError if the objects passed in are not equal.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-1474) Add assertEquals overloads for Blob
and Clob
Posted by "Andreas Korneliussen (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1474?page=comments#action_12419596 ]
Andreas Korneliussen commented on DERBY-1474:
---------------------------------------------
I do not think it is a problem to let the assertBlob(..) method throw checked exceptions. It is an assert method which is going to compare two Blobs, and I think it is reasonable that it is allowed to throw SQLException and IOException if that happens when accessing the Blobs.
> Add assertEquals overloads for Blob and Clob
> --------------------------------------------
>
> Key: DERBY-1474
> URL: http://issues.apache.org/jira/browse/DERBY-1474
> Project: Derby
> Type: Sub-task
> Components: Test
> Versions: 10.2.0.0, 10.3.0.0
> Reporter: Kristian Waagan
> Assignee: Kristian Waagan
> Fix For: 10.2.0.0
> Attachments: derby-1474-1a.diff, derby-1474-1a.stat, derby-1474-1b.diff, derby-1474-1c.diff, derby-1474-2a.diff, derby-1474-2a.stat, error-output.txt
>
> Add assertEquals(Blob,Blob) and assertEquals(Clob,Clob) to BaseJDBCTestCase.
> The naming follows the JUnit scheme, and the methods throws an AssertionFailedError if the objects passed in are not equal.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-1474) Add assertEquals overloads for Blob
and Clob
Posted by "Knut Anders Hatlen (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1474?page=all ]
Knut Anders Hatlen updated DERBY-1474:
--------------------------------------
Attachment: derby-1474-1c.diff
I have reviewed the patch. The methods look very useful. I found one issue: assertEquals(Blob,Blob) has assertNull() on b1/b2 where the assert should be on is1/is2. Attached is an updated patch with that one fixed. Also, I fixed a spelling error in a comment and made the methods static. I will commit the new patch. Thank you, Kristian.
> Add assertEquals overloads for Blob and Clob
> --------------------------------------------
>
> Key: DERBY-1474
> URL: http://issues.apache.org/jira/browse/DERBY-1474
> Project: Derby
> Type: Sub-task
> Components: Test
> Versions: 10.2.0.0, 10.3.0.0
> Reporter: Kristian Waagan
> Assignee: Kristian Waagan
> Attachments: derby-1474-1a.diff, derby-1474-1a.stat, derby-1474-1b.diff, derby-1474-1c.diff
>
> Add assertEquals(Blob,Blob) and assertEquals(Clob,Clob) to BaseJDBCTestCase.
> The naming follows the JUnit scheme, and the methods throws an AssertionFailedError if the objects passed in are not equal.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-1474) Add assertEquals overloads for Blob
and Clob
Posted by "Kristian Waagan (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1474?page=all ]
Kristian Waagan updated DERBY-1474:
-----------------------------------
Attachment: derby-1474-1a.diff
derby-1474-1a.stat
'derby-1474-1a.diff' implements the two methods assertEquals(Blob,Blob) and assertEquals(Clob,Clob) in BaseJDBCTestCase.
Patch is ready for review/comments.
> Add assertEquals overloads for Blob and Clob
> --------------------------------------------
>
> Key: DERBY-1474
> URL: http://issues.apache.org/jira/browse/DERBY-1474
> Project: Derby
> Type: Sub-task
> Components: Test
> Versions: 10.2.0.0, 10.3.0.0
> Reporter: Kristian Waagan
> Assignee: Kristian Waagan
> Attachments: derby-1474-1a.diff, derby-1474-1a.stat
>
> Add assertEquals(Blob,Blob) and assertEquals(Clob,Clob) to BaseJDBCTestCase.
> The naming follows the JUnit scheme, and the methods throws an AssertionFailedError if the objects passed in are not equal.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-1474) Add assertEquals overloads for Blob
and Clob
Posted by "Andreas Korneliussen (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1474?page=comments#action_12419657 ]
Andreas Korneliussen commented on DERBY-1474:
---------------------------------------------
I think the new patch ('derby-1474-2b.diff') is fine and can be committed.
> Add assertEquals overloads for Blob and Clob
> --------------------------------------------
>
> Key: DERBY-1474
> URL: http://issues.apache.org/jira/browse/DERBY-1474
> Project: Derby
> Type: Sub-task
> Components: Test
> Versions: 10.2.0.0, 10.3.0.0
> Reporter: Kristian Waagan
> Assignee: Kristian Waagan
> Fix For: 10.2.0.0
> Attachments: derby-1474-1a.diff, derby-1474-1a.stat, derby-1474-1b.diff, derby-1474-1c.diff, derby-1474-2a.diff, derby-1474-2a.stat, derby-1474-2b.diff, error-output.txt
>
> Add assertEquals(Blob,Blob) and assertEquals(Clob,Clob) to BaseJDBCTestCase.
> The naming follows the JUnit scheme, and the methods throws an AssertionFailedError if the objects passed in are not equal.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-1474) Add assertEquals overloads for Blob
and Clob
Posted by "Kristian Waagan (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1474?page=all ]
Kristian Waagan updated DERBY-1474:
-----------------------------------
Attachment: derby-1474-2b.diff
'derby-1474-2b.diff' addresses the two last comments, from Knut Anders and Andreas.
Originally I didn't want to have the assertEquals-methods throw checked exceptions. This can cause some inconveniences* in test-methods throwing other IOExceptions, and it doesn't match the behavior of the rest of the JUnit assertEquals-methods. However, after having read up on the differences between failures and errors, and the feedback I got, I have decided to go for checked exceptions anyway. Makes the code simple. Thanks to Andreas for making me reconsider this.
The solution makes the very good suggestions from Knut Anders non-applicable. Too bad :)
Patch changes:
* addition of throws clause
* removal of try - catch
* reindentation of the new code (sorry, made the patch a bit meaty)
* moved the declaration of InputStream/Reader variables
Ready for another review/commit round.
*) For errors you usually want the full stack trace. If your test-method calls methods that you expect to throw IOExceptions, and/or you have a throws IOException clause, you should try to use as small try-catch blocks as possible to allow the IOException from assertEquals to be caught by the JUnit framework instead of your own catch block.
> Add assertEquals overloads for Blob and Clob
> --------------------------------------------
>
> Key: DERBY-1474
> URL: http://issues.apache.org/jira/browse/DERBY-1474
> Project: Derby
> Type: Sub-task
> Components: Test
> Versions: 10.2.0.0, 10.3.0.0
> Reporter: Kristian Waagan
> Assignee: Kristian Waagan
> Fix For: 10.2.0.0
> Attachments: derby-1474-1a.diff, derby-1474-1a.stat, derby-1474-1b.diff, derby-1474-1c.diff, derby-1474-2a.diff, derby-1474-2a.stat, derby-1474-2b.diff, error-output.txt
>
> Add assertEquals(Blob,Blob) and assertEquals(Clob,Clob) to BaseJDBCTestCase.
> The naming follows the JUnit scheme, and the methods throws an AssertionFailedError if the objects passed in are not equal.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-1474) Add assertEquals overloads for Blob
and Clob
Posted by "Kristian Waagan (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1474?page=all ]
Kristian Waagan updated DERBY-1474:
-----------------------------------
Attachment: derby-1474-1b.diff
'derby-1474-1b.diff' replaces version 1a. Found two typos, causing the blob references to be compared instead of the blob bytes. The new patch only replaces two variable names in one location.
Unless someone plans to review, I think a committer can have a look at the patch.
> Add assertEquals overloads for Blob and Clob
> --------------------------------------------
>
> Key: DERBY-1474
> URL: http://issues.apache.org/jira/browse/DERBY-1474
> Project: Derby
> Type: Sub-task
> Components: Test
> Versions: 10.2.0.0, 10.3.0.0
> Reporter: Kristian Waagan
> Assignee: Kristian Waagan
> Attachments: derby-1474-1a.diff, derby-1474-1a.stat, derby-1474-1b.diff
>
> Add assertEquals(Blob,Blob) and assertEquals(Clob,Clob) to BaseJDBCTestCase.
> The naming follows the JUnit scheme, and the methods throws an AssertionFailedError if the objects passed in are not equal.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-1474) Add assertEquals overloads for Blob
and Clob
Posted by "Kristian Waagan (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1474?page=all ]
Kristian Waagan updated DERBY-1474:
-----------------------------------
Attachment: derby-1474-2a.diff
derby-1474-2a.stat
error-output.txt
Thanks for the comments Andreas.
I have changed the following in the *additional* patch 'derby-1474-2a.diff':
1) Closed stream on successful execution through the assert methods. I don't see much need to close when an error happens (within the assert method), including when the LOB contents differ.
2) Avoided string concatenation for every byte/char.
3) Added a method to wrap an exception in an Error-object. I ask people to have a look at this issue, as there are many ways to do this.
I had to use reflection in the 'generateError'-method in BaseTestCase, because it is compiled with 1.3. Also, the way you want to throw the exception depends on the Java version.
If people think this is too much bloat, the exception stack traces can just be dumped to console.
I'm open to other approaches, but I would like to avoid having assertEquals throwing checked exceptions.
I included the output from a simple test I wrote in 'error-output.txt', for people to see what the output and stack traces will look like with the current implementation. The test simply reads from a closed stream.
Awaiting feedback :)
> Add assertEquals overloads for Blob and Clob
> --------------------------------------------
>
> Key: DERBY-1474
> URL: http://issues.apache.org/jira/browse/DERBY-1474
> Project: Derby
> Type: Sub-task
> Components: Test
> Versions: 10.2.0.0, 10.3.0.0
> Reporter: Kristian Waagan
> Assignee: Kristian Waagan
> Fix For: 10.2.0.0
> Attachments: derby-1474-1a.diff, derby-1474-1a.stat, derby-1474-1b.diff, derby-1474-1c.diff, derby-1474-2a.diff, derby-1474-2a.stat, error-output.txt
>
> Add assertEquals(Blob,Blob) and assertEquals(Clob,Clob) to BaseJDBCTestCase.
> The naming follows the JUnit scheme, and the methods throws an AssertionFailedError if the objects passed in are not equal.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira