CSC/ECE 517 Fall 2009/wiki1a 1 103

Writing Effective Junit Test Cases

This article introduces the best practice a developer should follow in writing JUnit test cases for Java programming.

Prerequisites

Readers are assumed to be familiar with the following terms/names and their concepts:

Unit Testing - A verification process run by a developer on the smallest testable parts of an application.

Test case - A process generates a set of conditions and variables by which a developer can tell if a piece of software works correctly.

JUnit - A unit testing framework for programming in Java.

Criteria For Effective Unit Testing

• Design - It's "Hard to design testable code". "However, testable code often is better designed" [1]
• Documentation - Good documentation could prevent oversight, increase transparency, and facilitate knowledge transfer in the future.[2]
• Good coverage,

What should be covered in each run of the test:

1. UI - All screen elements, spelling, fonts, and sizes of all the “labels” or text. May not be applicable to JUnit since automation may be improbable here.
2. Every line of code should at least be executed once.
3. Every condition in case of “conditional statements” should be met at least once.
4. Cyclomatic number, or the number of all possible paths should be through at least once.
5. Boundaries - The input parameters should be tested with conditions at the lower and/or upper limits such as too large or too small. Overflow condition should also be tested.
6. Every error message/exception handling should be tested
7. All validations are being performed, correctly.
8. All possible setup configurations should be tested.

• Avoid redundant tests which may give wrong impression of the scale of the bugs and fixes.
• Easy for automation, which should be implied by JUnit.

Cases Specific to JUnit Test Cases

In theory, there shouldn't be anything special regarding to effective unit testing in JUnit. A good resource for designing tests in JUnit is the JUnit FAQ.

• A simple test

Create a class:

    package myPackageToBeTested;
    import org.junit.*;
    import static org.junit.Assert.*;
    import java.util.*;
    public class SimpleTest {
      	  
        //a test method (annotated with @Test) using asserts:
        @Test
        public void test1plus1() {
            assertEquals("1+1=2", 2, 1+1);
        }
    }

• A test suite

Add a suite() method to the above simple test example to include all of your test methods:

        ...
        public static junit.framework.Test suite() {
            return new junit.framework.JUnit4TestAdapter(SimpleTest.class);
        }
        ...

• A test template

This sample test template contains setUp() and tearDown() methods to initialize and release the object(s) being tested

    import org.junit.*;
    import static org.junit.Assert.*;

    public class TemplateTest {
 
        // Sets up the test fixture. 
        @Before
        public void setUp() {

        }

        //Tears down the test fixture. 
        @After
        public void tearDown() {
        }
        
        //a test method (annotated with @Test) using asserts:
        @Test
        public void test1plus1() {
            assertEquals("1+1=2", 2, 1+1);
        }

        public static junit.framework.Test suite() {
            return new junit.framework.JUnit4TestAdapter(TemplateTest.class);
        }
    }

References

1. effective unit testing
2. Unit Testing: Why? What? & How?
3. JUnit FAQ