Why Does Poeple Import org.junit.Assert Statically

Q

Why Does Poeple Import org.junit.Assert Statically?

✍: Guest

A

Poeple use the static import statement on org.junit.Assert to save coding time on calling its assetion methods. With a normal import statement, assertion method names must qualified with the class name like this:

import org.junit.Assert; 
...
        Assert.assertEquals(12, message.length());

With a static import statement, assertion method names can be used directly like this:

import static org.junit.Assert.*;
...
        assertEquals(12, message.length());

2008-01-29, 4494👍, 0💬