DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports Events Over 2 million developers have joined DZone. Join Today! Thanks for visiting DZone today,
Edit Profile Manage Email Subscriptions Moderation Admin Console How to Post to DZone Article Submission Guidelines
View Profile
Sign Out
Refcards
Trend Reports
Events
Zones
Culture and Methodologies Agile Career Development Methodologies Team Management
Data Engineering AI/ML Big Data Data Databases IoT
Software Design and Architecture Cloud Architecture Containers Integration Microservices Performance Security
Coding Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Culture and Methodologies
Agile Career Development Methodologies Team Management
Data Engineering
AI/ML Big Data Data Databases IoT
Software Design and Architecture
Cloud Architecture Containers Integration Microservices Performance Security
Coding
Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance
Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
  1. DZone
  2. Testing, Deployment, and Maintenance
  3. Testing, Tools, and Frameworks
  4. Using JUnit Theories with Spring and Mockito

Using JUnit Theories with Spring and Mockito

Lucas Godoy user avatar by
Lucas Godoy
·
Dec. 11, 12 · Interview
Like (1)
Save
Tweet
Share
16.20K Views

Join the DZone community and get the full member experience.

Join For Free

What is a Theory?

Functionally, a theory is an alternative to JUnit's parameterized tests. Semantically, a theory encapsulates the tester's understanding of an object's universal behavior. That is, whatever it is that a theory asserts, it is expected to be true for all data. Theories should be especially useful for finding bugs in edge cases.

Contrast this with a typical unit test, which asserts that a specific data point will have a specific outcome, and only asserts that. (For this reason, typical unit tests are sometimes called example-based tests to contrast them with theories.)

This is very nice in theory, but...

A @Theory needs a special JUnit runner (Theories.class). So if you want to use Spring and/or Mockito together with theories, you have a problem. All of these features need a different runner and you can only use one on each test class.

The solution

For Mockito is easy. Instead of using the @Mock annotiation, you can use the static createMock method. One problem solved.

For Spring is a little bit trickier. First of all, you have to use @ContextConfiguration to declare the XML with the bean definitions that you need. But the trickiest part is that you have to tell Spring how to do the autowiring without using its own runner. This can be accomplish adding this line to the @Before method:

new TestContextManager(getClass()).prepareTestInstance(this);

Basic Usage Example

package org.mackenzine.theories;

import static org.junit.Assert.assertEquals;
import static org.junit.Assert.assertNotNull;
import static org.mockito.Mockito.when;

import java.util.Date;

import org.junit.Before;
import org.junit.experimental.theories.DataPoints;
import org.junit.experimental.theories.Theories;
import org.junit.experimental.theories.Theory;
import org.junit.runner.RunWith;
import org.mockito.Mockito;
import org.springframework.beans.factory.annotation.Autowired;
import org.springframework.test.context.ContextConfiguration;
import org.springframework.test.context.TestContextManager;

@RunWith(Theories.class)
@ContextConfiguration("classpath:parser.xml")
public class QuoteTheoriesTest {

   private static String deleteMessage = "deleteMessage";
   private static String updateMessage = "updateMessage";

   private QuoteFactory factory;

   private final Event event = Mockito.mock(Event.class);
   private final Contract contract = Mockito.mock(Contract.class);
   private final Commodity commodity = Mockito.mock(Commodity.class);

   @Autowired
   private Parser parser;

   @Before
   public void setUp() throws Exception {
     factory = new QuoteFactory();
     new TestContextManager(getClass()).prepareTestInstance(this);
   }

   @DataPoints
   public static String[] getEventTypes() {
     return new String[] { updateMessage, deleteMessage };
   }

   @Theory
   public void shouldCreateQuote(final String message) throws Exception {
     Date now = new Date();

     when(event.getParsedMessage()).thenReturn(parser.parse(message));
     when(event.getContract()).thenReturn(contract);
     when(event.getTradeDate()).thenReturn(now);
     when(contract.getExternalCode()).thenReturn("externalCode");
     when(contract.getCommodity()).thenReturn(commodity);
     when(commodity.getCommodityCode()).thenReturn("code");

     Quote quote = factory.createQuote(event);

     assertNotNull(quote);

     assertEquals("code", quote.getCommodityCode());
     assertEquals(now, quote.getTradeDate());
   }
}
Sources

Definition of Theories:
https://blogs.oracle.com/jacobc/entry/junit_theories

Original Idea for Parameterized Tests:
http://stackoverflow.com/questions/8974977/spring-parameterized-theories-junit-tests

Thread on SpringSource:
http://forum.springsource.org/showthread.php?78929-Is-Theory-supported

Open Issue in SpringSource for Parameterized Tests (not for Theories):
https://jira.springsource.org/browse/SPR-5292

Spring Framework JUnit Mockito unit test

Opinions expressed by DZone contributors are their own.

Popular on DZone

  • Architectural Miscalculation and Hibernate Problem "Type UUID but Expression Is of Type Bytea"
  • Kubernetes vs Docker: Differences Explained
  • The Real Democratization of AI, and Why It Has to Be Closely Monitored
  • Uplevel Your Managers With Mini-M Support Groups

Comments

Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 600 Park Offices Drive
  • Suite 300
  • Durham, NC 27709
  • support@dzone.com
  • +1 (919) 678-0300

Let's be friends: