IDE Tutorials CSE 219 Fall 2005

	TOC: AkA Tactical Operations Center
Table of Contents: NetBeans Eclipse Basics Tutorial NetBeans Eclipse Debugging Tutorial NetBeans Eclipse JUnit Testing Tutorial NetBeans Eclipse CVS Tutorial NetBeans Eclipse JAR Files Tutorial NetBeans Eclipse

JUnit Testing

The basic premise behind JUnit testing is to be able to test each component of our program independently from the rest of our program.

In the design phase of our project we specified what every method is supposed to do and have also come up with a set of tests to make
sure that our method is functioning properly.JUnit provides us with a frame work to take each one of the methods and perform individual
tests to ensure we are getting proper values.

http://junit.sourceforge.net/javadoc/index.html contains the API for the JUnit framework, the specification for Assert, JUnit, TestCase and many more classes can be found there.

	The Opening
This is our familiar eclipse environment. We will start the tutorial here by opening up a project we wish to write a test suite for. Also start by selecting a file in your resources window that you wish to create a test for

	Adding a new Test
The next step is to add our new testcase. Since we have selected a file in our resource browser we can just goto file new JUnit Test Case. This will help us by filling in some information for us. It will also create a file for us the is named identicly to our class exept that "Test" is appended to the name of the class.

	Test Creation 1
We are now presented with a New Junit Test Case window. The source folder is where we are going to place our new test file, while the package is the package it will be created in. We can rename the test if we like and choose a different superclass. For our purposes all of the information provided for us is correct. You will notice 4 check boxes. If the methods that you are trying to test are not static meaning that they need an instance of the object to be called then you will probably want to specify a setUp method for the test case. This will be where you can instantiate your object before running the tests. Also if your tests allocate any special resources you may want to select tearDown so you can properly dispose of the resources. After we are done with this you may click the next button.

	Test Creation 2
In this next window we are allowed to specify which methods we wish to test. By selecting methods in this window eclipse will create a method in our test file named the same exact thing as the methods we select but with "Test" added in front of them. If you want you can select "Create tasks for generated test methods" this will place //TODO markers in the code so you know where to add code by searching for //TODO.

	Blank Tests?
At this point we now have our new test file opened in our editor. you look in the resource browser you will see a new file with "Test" at the end. This is the source file for our tests for that particular class. Since we are testing for a reason lets fill in some test cases.

	The Difficult Job Of making Tests
The JUnit framework provides us with several ways to judge if a test has succeeded or failed. Our TestCase object that we have extends Assert which provides the following functionality for testing. assertEquals: This provides a series of overloads that allows you to test if an actual value matches the expected one. assertFalse: Use this if you know the function will always return false (fails if it receives true) assertNotNull: If your method return null in the event of failure use this to check to see if it succeeds assertNotSame: If your method is supposed to return an element from a list you can use this to check if the element returned is the one from the actual list assertNull: If your method return null in the event of failure use this to check to see if it fails fail: Will fail the test, use this in conjunction with conditionals failNotEquals: Essentially the same as assertEquals but will fail the test if they arent equal instead of causing an error failNotSame: Essentially the same as assertNotSame except instead of causing an error it will cause a failure

	Time to take the Test
We now want to run the test that we just created to do this we have several options. We can either create a test suite from the file new other menu or we can select the test we want to run and then goto run, run as, JUnit test.

	The Results are Back: 1 Passed 2 Failed
You will notice that eclipse has opened a JUnit window on the left side of your browser. This will display the results of your testing. If you have complex tests which call other tests you can see the trace of the failure at the bottom. You are also presented with which tests failed under the failures tab.

Happy Testing