Software Development Cross Solution - Index of - Free

making the most of a framework
Automate your tests with a testing framework
Let’s take a simple test case and automate it using JUnit. JUnit provides common
resources and behaviors you need for your tests, and then invokes each of your tests,
one at a time. JUnit gives you a nice GUI to see your tests run, as well, but that’s really
a small thing compared to the power of automating your tests.
Here’s a static
final of empty
checkboxes that can
be used in several
different tests.
JUnit calls setUp()
before each test is
run, so here’s where to
initialize variables used
in the test methods.
tearDown() is for
cleaning up. JUnit calls
this method when each
test is finished.
Here’s an actual
test. You annotate it
with @Test so JUnit
knows it’s a test
and can run it. The
method just sends a
test message and a
checkboxState.
250 Chapter 7
You’ve got to import the JUnit classes.
}
package headfirst.sd.chapter7;
import java.io.*;
import java.net.Socket;
import org.junit.*;
public class TestRemoteReader {
private Socket mTestSocket;
private ObjectOutputStream mOutStream;
private ObjectInputStream mInStream;
These are objects used in several
of the test cases.
public static final boolean[] EMPTY_CHECKBOXES = new boolean[256];
@Before
public void setUp() throws IOException {
mTestSocket = new Socket(“127.0.0.1”, 4242);
mOutStream =
new ObjectOutputStream(mTestSocket.getOutputStream());
mInStream =
new ObjectInputStream(mTestSocket.getInputStream());
}
@After
public void tearDown() throws IOException {
mTestSocket.close();
mOutStream = null;
mInStream = null;
mTestSocket = null;
}
Since these are
annotated with @Before
and @After, they’ll get
called by JUnit before
and after each test.
@Test
public void testNormalMessage()throws IOException {
boolean[] checkboxState = new boolean[256];
checkboxState[0] = true;
checkboxState[5] = true;
checkboxState[19] = true;
mOutStream.writeObject(“This is a test message!”);
mOutStream.writeObject(checkboxState);
}
You can use mOutStream because it
was set up in the setup() method
that JUnit will already have called.
Download at WoweBook.Com
JUnit also has a textbased
test runner
and plug-ins for most
popular IDEs.