Skip to main content

Mock unit testing with Mockito and Spring (Ejb and Rest service)

In this tutorial we are going to learn about mock unit testing. We are using here Mockito with Spring to write unit tests. We will also see how to mock an EJB session bean inside mocked service without constructor/setters injection.

What is mocking

Mocking is a technique to replace the actual implementation with some dummy or provided code chunk during unit testing. For example if we need to unit test some service which persist data to database then we can mock that persist method to add it to some in-memory collection. Also we can mock data retrieval to get the data from same collection or so. Mockito provide various class and features to implement the mocking seamlessly.

Maven dependency

We are using Spring (XML base configuration) and mockito for mock testing. Below dependencies are required.

Spring configuration XML

Below is our configuration for spring where we enable annotation based processing. Also we are creating a bean for EJB session bean.
  1. Spring namespace and schema declaration

  2. <beans xmlns=""
  3. Configure annotation processing

  4.     <context:component-scan base-package=""/>
        <context:component-scan base-package="com.ttj.misc"/>
  5. Bean declaration for EJB Session Bean

  6.     <jee-local-slsb id="ejbSessionBean" jndi-name="ejb/MyEjbSessionBean"
            business-interface="com.ttj.ejb.MyBusinessInterface" />

Rest Service

Below is the Rest service where we inject the ejb session bean using business interface. We invoke the method on EJB bean and then return the same response as a service call response.
public class MyController{
    private MyBusinessInterface ejbSessionBean;

    @RequestMapping(value="/message", method=RequestMethod.GET,
    public String getUserMessageFromEjb(){
        return ejbSessionBean.getUserMessage();

Unit Test using Mockito

Now we will create out unit test using mockito where we will mock the EJB session bean which will be injected in Rest service. Then this rest service will use mocked ejb bean to provide the response.
  1. Required annotations

  2. Here we are using @RunWith annotation to enable the Spring's dependency injection and @ContextConfiguration to makes Spring to scan mentioned classes. Please note that Spring will not load context configuration XML from WEB-INF by default, so we need to configure the scanning of required classes.
    @ContextConfiguration(class={MyController.class, MyControllerTest.class})
    public class MyControllerTest{
  3. Mocking EJB bean

  4. In below code we are creating a mocked bean which will automatically bind with controller class as controller class binds it using the bean ID.
        public MyBusinessInterface ejbSessionBean(){
            MyBusinessInterface bean = Mockito.mock(MyBusinessInterface.class);
            Mockito.when(bean.getUserMessage()).thenReturn("Dummy message");
            return bean;
  5. Writing Test case

  6. In below code we autowire the controller class and then uses it to write the unit test.
        private MyController controller;
        public void getUserMessageFromEjbTest(){
            String exp = "Dummy message");
            Assert.assertEquals(exp, controller.getUserMessageFromEjb());
Now you can execute the maven build to run the test.


  1. It's very useful blog post with informative and insightful content and i had good experience with this information.I have gone through CRS Info Solutions Home which really nice. Learn more details About Us of CRS info solutions. Here you can see the Courses CRS Info Solutions full list. Find Student Registration page and register now. Go through Blog post of crs info solutions. I just read these Reviews of crs really great. You can now Contact Us of crs info solutions. You enroll for Pega Training at crs info solutions.

  2. Thanks for delivering a good stuff, Explanation is good, Nice Article.
    software testing training in chennai

  3. Thanks for delivering a good stuff, Explanation is good, Nice Article.
    software testing training in chennai


Post a Comment

Popular Posts

Setting up kerberos in Mac OS X

Kerberos in MAC OS X Kerberos authentication allows the computers in same domain network to authenticate certain services with prompting the user for credentials. MAC OS X comes with Heimdal Kerberos which is an alternate implementation of the kerberos and uses LDAP as identity management database. Here we are going to learn how to setup a kerberos on MAC OS X which we will configure latter in our application. Installing Kerberos In MAC we can use Homebrew for installing any software package. Homebrew makes it very easy to install the kerberos by just executing a simple command as given below. brew install krb5 Once installation is complete, we need to set the below export commands in user's profile which will make the kerberos utility commands and compiler available to execute from anywhere. Open user's bash profile: vi ~/.bash_profile Add below lines: export PATH=/usr/local/opt/krb5/bin:$PATH export PATH=/usr/local/opt/krb5/sbin:$PATH export LDFLAGS=&

SpringBoot - @ConditionalOnProperty example for conditional bean initialization

@ConditionalOnProperty annotation is used to check if specified property available in the environment or it matches some specific value so it can control the execution of some part of code like bean creation. It may be useful in many cases for example enable/disable service if specific property is available. Below are the attributes which can be used for property check. havingValue - Provide the value which need to check against specified property otherwise it will check that value should not be false. matchIfMissing - If true it will match the condition and execute the annotated code when property itself is not available in environment. name - Name of the property to be tested. If you want to test single property then you can directly put the property name as string like "" and if you have multiple properties to test then you can put the names like {"prop.name1","prop.name2"} prefix - It can be use when you want to apply some prefix to

Spring Batch tutorial with example

Spring batch is used to create and process the batch jobs. It provides various features like logging, job statistics, transaction management, restarting jobs. It is very helpful in processing of large dataset but with finite volume of data. In this tutorial we will learn how to create and execute the spring batch job. In our example we will create a job which will import all the words from a text file to database and then at last it will print the total number of words available in the database. Below is the project structure. Creating batch job Sample text file to import Below is the contents of text file which we use for importing the words. The list below gives you the 1000 most frequently used English words in alphabetical order. Once you've mastered the shorter vocabulary lists, this is the next step. It would take time to learn the entire list from scratch, but you are probably already familiar with some of these words. Feel free to copy this list into

Multiple data source with Spring boot, batch and cloud task

Here we will see how we can configure different datasource for application and batch. By default, Spring batch stores the job details and execution details in database. If separate data source is not configured for spring batch then it will use the available data source in your application if configured and create batch related tables there. Which may be the unwanted burden on application database and we would like to configure separate database for spring batch. To overcome this situation we will configure the different datasource for spring batch using in-memory database, since we don't want to store batch job details permanently. Other thing is the configuration of  spring cloud task in case of multiple datasource and it must point to the same data source which is pointed by spring batch. In below sections, we will se how to configure application, batch and cloud task related data sources. Application Data Source Define the data source in application properties or yml con