core: Reduce timeout in DiretorySearcherTest

Reduced timeout to 1 millisecond instead of 1 second.
The timeout here is meaningless since all the test are done against mock
servers anyway, and reducing the timeout allows the test to pass in in
environments where network connectivity is disabled.

Change-Id: I2cd5b543963a3c6c16b8cfe2a40e5433c5ac3422
Signed-off-by: Allon Mureinik <amureini@redhat.com>
core: Remove DirectorySearcherTest's @BeforeClass

This is a POJO test, there is no need to interact with JBoss' logging
folder.

Change-Id: I1b9c4df4b79dd061d941aa8d38715572fa0482b8
Signed-off-by: Allon Mureinik <amureini@redhat.com>
core: Fix testGetRootDSENoServers

Since urls is a zero length list, urls.get(0) throws an
IndexOutOfBoundsException.
This exception is caught, and thus the test passes, but it's kind of
meaningless - it does not execute any of the DirectorySearcher's code,
and essentially tests Java's ArrayList.get(int) implementation.

I guess it's safe to assume that it works correctly.

Change-Id: I295d9b10495efabf892107187de7ccd91334062f
Signed-off-by: Allon Mureinik <amureini@redhat.com>
core: DirectorySearcherTest proper failures

Used the proper JUnit 4 syntax for failures - @Test with the expected
parameter, instead of the ugly hack of catching an exception and
returning before the test reaches a fail() statement.

Change-Id: Icdc729f0aa78674f45ce11aab844cbf9751a6ac6
Signed-off-by: Allon Mureinik <amureini@redhat.com>