I have a HTML list of about 500 items and a "filter" box above it. I started by using jQuery to filter the list when I typed a letter (timing code added later): $('#filter').keyup( function() { var jqStart = (new Date).getTime(); var search = $(this).val().toLowerCase(); var $list = $('ul.ablist > li'); $list.each( function() { if ( $(this).text().toLowerCase().indexOf(search) === -1 ) $(this).hide(); else $(this).show(); } ); console.log('Time: ' + ((new Date).getTime() - jqStart)); } ); However, there was a couple of seconds delay after typing each letter (particularly the first letter). So I thought it may be slightly quicker if I used plain Javascript (I read recently that jQuery's each function is particularly slow). Here's my JS equivalent: document.getElementById('filter').addEventListener( 'keyup', function () { var jsStart = (new Date).getTime()...
The old method (of Junit 3) was to mark the test-classes by extending junit.framework.TestCase. That inherited junit.framework.Assert itself and your test-class gained the ability to call the assert-methods this way.
ReplyDeleteSince version 4 of junit the framework uses Annotations for marking tests. So you no longer need to extend TestCase. But that means, the assert-methods aren't available. But you can make a static import of the new Assert-class. That's why all the assert-methods in the new class are static methods. So you can import it this way:
import static org.junit.Assert.*;
After this static import, you can use this methods without prefix.
At the redesign they also moved to the new package org.junit, that follows better the normal conventions for package-naming.
JUnit 3.X: junit.framework.Assert
ReplyDeleteJUnit 4.X: org.junit.Assert
Prefer the newest one, especially when running JDK5 and higher with annotation support.
I believe they are refactoring from junit.framework to org.junit and junit.framework.Assert is maintained for backwards compatibility.
ReplyDeleteThere is in fact a functional change: org.junit.Assert will complain if you use the two-argument assertEquals() with float or double, while junit.framework.Assert will silently autobox it.
ReplyDeleteI did a rough source code compare and there are no serious changes.
ReplyDeleteLot of comments were added in org.junit.Assert and some refactorings are done.
The only change is the comparison with Arrays. There are some code clean ups, but there's (imho) no functional change.
There are other functional change today.
ReplyDeleteorg.junit.Assert.assertEquals(float expected, float actual, float delta) is exist no longer.
It still exists in junit.framework.
Not easy to compare floats in these conditions... I must cast them in object and then use assertEquals(Object expected, Object actual).
Anyone has a more fluent solution (without reusing the old api, of course) ?