Win a copy of Testing JavaScript Applications this week in the HTML Pages with CSS and JavaScript forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Bear Bibeault
  • Ron McLeod
  • Jeanne Boyarsky
  • Paul Clapham
  • Tim Cooke
  • Liutauras Vilda
  • Junilu Lacar
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • fred rosenberger
  • salvin francis
  • Piet Souris
  • Frits Walraven
  • Carey Brown

A Simple Test Framework using JUnit and Spring (Part 1)

Posts: 30
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

This is a small framework that allows you to do unit testing on your POJOs under Spring environment. It is quite useful especially if you're adapting a Test-Driven Development methodoloy. This is Part 1 for testing service objects.

I will post a separate article in Part 2 for testing web pages and Spring Controller objects.

Only the following files are involved:
1. - the main class to extend for testing
2. - executes all test classes
3. - the class to be tested
4. - the test class for LoginService, contains all test cases
5. - the test case object for LoginService, executes test cases
6. applicationContext.xml - Spring configuration file
7. applicationContext-test.xml - Spring configuration file for test-specific beans

The package structure:
1. - package for LoginService under /src folder
2. - package for test classes for LoginService under /src-test folder, must be the same as the implementation class
3. com.test.main - package for test framework classes

1. create a testcase object (LoginServiceTestCase) for a class to be tested (LoginService) by extending the TestCase.
2. create a test class (LoginServiceTest) which executes several test cases or scenarios - positive & negative test cases
3. modify AllTests class to include the LoginServiceTest class to be executed
4. modify applicationContext-test.xml to define the bean for LoginServiceTestCase
5. run the AllTests class as JUnit

Sample output:
Test Case: Validate Login with valid credentials
PASS: Validate Login with valid credentials
Test Case: Validate Login with empty credentials
PASS: Validate Login with empty credentials
Test Case: Validate Login with invalid credentials
PASS: Validate Login with invalid credentials

The jar files you need in your classpath:

You can use this framework to test for business logic objects, Data Access Objects, and other POJOs.

If you're connected to a database, it will write to a database and rollback the transaction after every test case.

You can use it to test for several classes at the same time by simply following the steps above for each class.

You can also invoke this from your build script to automatically do a test before deployment. It will give you an idea whether to proceed with deployment depending on which test cases have failed or succeeded.

It also serves as a documentation for your test cases. Just use javadoc to generate APIs and attach the execution output or the JUnit screen shot.

This is a nice tool for Agile development.

Source Code Listing:
package com.test.main;

import java.util.HashMap;
import java.util.Iterator;
import java.util.Map;

// This class represent the Test Case object in Unit testing
public abstract class TestCase {

private String testName = "";

protected Map<String, Object> testConditions = new HashMap<String, Object>();
private Map<String, Boolean> expectedResults = new HashMap<String, Boolean>();
private Map<String, Boolean> actualResults = new HashMap<String, Boolean>();

public TestCase() {

// main execution point of every test case
public boolean isTestPass() throws Exception {
System.out.println("Test Case: " + this.getTestName());


boolean isMatch = this.isResultsMatch();
System.out.println((isMatch ? "PASS: " : "FAIL: ") + this.getTestName());
return isMatch;

// execute the method to be tested, set the parameters or conditions before execute
protected abstract void executeTest() throws Exception;

// check actual results and store in appropriate results values, use the setActualResult() method
protected abstract void checkActualResults() throws Exception;

// check all expected results againts actual results
private boolean isResultsMatch() {
Iterator i = expectedResults.entrySet().iterator();
Map.Entry<String,Boolean> result;
while (i.hasNext()) {
result = (Map.Entry<String,Boolean>);
if (this.getExpectedResult(result.getKey()) != this.getActualResult(result.getKey())) return false;
return true;

// this to ensure that all result entries are compared
private void syncResults() {
int exp = expectedResults.size();
int act = actualResults.size();
if (exp == act) return;
Map.Entry<String,Boolean> result;
if (exp > act) {
Iterator i = expectedResults.entrySet().iterator();
while (i.hasNext()) {
result = (Map.Entry<String,Boolean>);
if (! actualResults.containsKey( result.getKey() ) ) {
actualResults.put(result.getKey(), false);
} else {
Iterator i = actualResults.entrySet().iterator();
while (i.hasNext()) {
result = (Map.Entry<String,Boolean>);
if (! expectedResults.containsKey( result.getKey() ) ) {
expectedResults.put(result.getKey(), false);

// reset all test conditions, and test results
public void initialize() {

// set conditions to specific value
public void setAllConditions(Object value) {
this.setMapValue(this.testConditions, value);

// set expected results to specific value
public void setAllExpectedResults(boolean value) {
this.setMapValue(this.expectedResults, value);

private void setMapValue(Map m, Object value) {
Iterator i = m.entrySet().iterator();
Map.Entry<String,Object> entry;
while (i.hasNext()) {
entry = (Map.Entry<String,Object>);
m.put(entry.getKey(), value);

// setters & getters
public void setTestCondition(String key, Object value)
{testConditions.put(key, value);}
public Object getTestCondition(String key)
{return testConditions.get(key);}
public void setExpectedResult(String key, Boolean value)
{expectedResults.put(key, value);}
public Boolean getExpectedResult(String key)
{return expectedResults.get(key);}
public void setActualResult(String key, Boolean value)
{actualResults.put(key, value);}
public Boolean getActualResult(String key)
{return actualResults.get(key);}
public String getTestName()
{return testName;}
public void setTestName(String testName)
{this.testName = testName;}

package com.test.main;

import org.junit.runner.RunWith;
import org.junit.runners.Suite;
import org.junit.runners.Suite.SuiteClasses;



@SuiteClasses({LoginServiceTest.class}) // add other test classes inside this annotation

public class AllTests {

public class LoginService {

public boolean isValid(String username, String password) {
// change the ff code with a call to DAO which digest password
if (username.equals("ludwin") && password.equals("xyz")) return true;
return false;

import static org.junit.Assert.*;

import org.junit.After;
import org.junit.Before;
import org.junit.Test;
import org.junit.runner.RunWith;
import org.springframework.beans.factory.annotation.Autowired;
import org.springframework.test.context.ContextConfiguration;
import org.springframework.test.context.junit4.SpringJUnit4ClassRunner;
import org.springframework.transaction.annotation.Transactional;

@ContextConfiguration(locations={"file:C:/MyProject/src/applicationContext.xml", "file:C:/MyProject/src- test/applicationContext-test.xml"})
//@Transactional // enable if you're updating database during testing

public class LoginServiceTest {

private LoginServiceTestCase loginTestCase;

public void setup() {

public void teardown() {

public void testLoginWithValidAccount() throws Exception {
loginTestCase.setTestName("Validate Login with valid credentials");
loginTestCase.setTestCondition(loginTestCase.CONDITION_USERNAME, "ludwin");
loginTestCase.setTestCondition(loginTestCase.CONDITION_PASSWORD, "xyz");
loginTestCase.setExpectedResult(loginTestCase.RESULT_IS_ERROR, false);
public void testLoginWithEmptyCredentials() throws Exception {
loginTestCase.setTestName("Validate Login with empty credentials");
loginTestCase.setTestCondition(loginTestCase.CONDITION_USERNAME, "");
loginTestCase.setTestCondition(loginTestCase.CONDITION_PASSWORD, "");
loginTestCase.setExpectedResult(loginTestCase.RESULT_IS_ERROR, true);
public void testLoginWithInvalidCredentials() throws Exception {
loginTestCase.setTestName("Validate Login with invalid credentials");
loginTestCase.setTestCondition(loginTestCase.CONDITION_USERNAME, "someuser");
loginTestCase.setTestCondition(loginTestCase.CONDITION_PASSWORD, "somepassword");
loginTestCase.setExpectedResult(loginTestCase.RESULT_IS_ERROR, true);

import org.springframework.beans.factory.annotation.Autowired;

import com.test.main.TestCase;

public class LoginServiceTestCase extends TestCase {

private LoginService loginService; // the class to be tested
// conditions
protected final String CONDITION_USERNAME = "userName";
protected final String CONDITION_PASSWORD = "password";

protected final String RESULT_IS_ERROR = "isError";

private boolean isError;

protected void checkActualResults() throws Exception {
setActualResult(RESULT_IS_ERROR, isError);

protected void executeTest() throws Exception {
try {
String userName = (String) getTestCondition(CONDITION_USERNAME);
String password = (String) getTestCondition(CONDITION_PASSWORD);
isError = ! loginService.isValid(userName, password); // call the method to be tested
} catch (Exception e) {
isError = true;


<?xml version="1.0" encoding="UTF-8"?>
<bean id="loginService" class="" />

<?xml version="1.0" encoding="UTF-8"?>


<!-- data source, enable if you're connecting to database for testing -->
<!-- <bean id="dataSource" class="org.springframework.jdbc.datasource.DriverManagerDataSource">-->
<!-- <property name="driverClassName" value="(fill-in)"/>-->
<!-- <property name="url" value="(fill-in)"/>-->
<!-- <property name="username" value="(fill-in)"/>-->
<!-- <property name="password" value="(fill-in)"/>-->
<!-- </bean>-->

<!-- transaction manager, enable to rollback database after testing -->
<!-- <bean id="transactionManager" class="org.springframework.jdbc.datasource.DataSourceTransactionManager">-->
<!-- <property name="dataSource" ref="dataSource"/>-->
<!-- </bean>-->

<!-- test beans -->

<bean id="loginServiceTestCase" class=""/>
Posts: 12617
IntelliJ IDE Ruby
  • Likes 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Please UseCodeTags when posting code or configuration. Unformatted code and configuration is very difficult to read. You can edit your post to include them by using the button.

This seems more appropriate for a blog post, really. And it's not clear to me what your "framework" is, since JUnit is already a unit testing framework. What's your goal here? What problem are you trying to solve?
The harder I work, the luckier I get. -Sam Goldwyn So tiny. - this ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop
    Bookmark Topic Watch Topic
  • New Topic