{"id":873,"date":"2025-07-13T13:14:36","date_gmt":"2025-07-13T20:14:36","guid":{"rendered":"https:\/\/www.alerainfotech.com\/?p=873"},"modified":"2025-07-13T13:23:19","modified_gmt":"2025-07-13T20:23:19","slug":"the-ultimate-guide-to-mock-injectmocks-and-mockbean-in-spring-boot-testing","status":"publish","type":"post","link":"https:\/\/www.alerainfotech.com\/home\/2025\/07\/13\/the-ultimate-guide-to-mock-injectmocks-and-mockbean-in-spring-boot-testing\/","title":{"rendered":"The Ultimate Guide to\u00a0@Mock,\u00a0@InjectMocks\u00a0and\u00a0@MockBean\u00a0in Spring Boot Testing"},"content":{"rendered":"

\ud83c\udfaf The Ultimate Guide to @Mock<\/code>, @InjectMocks<\/code> and @MockBean<\/code> in Spring Boot Testing<\/h2>\n

\u2705 By the end, you\u2019ll know exactly when to use each, how they work under the hood, and what you\u2019re truly testing.<\/p>\n

\ud83d\ude80 Why do we need mocks?<\/h3>\n

When writing unit tests<\/strong>, you want to test your business logic in isolation<\/strong>, without hitting:<\/p>\n

    \n
  • real databases<\/li>\n
  • HTTP calls<\/li>\n
  • or heavy Spring context.<\/li>\n<\/ul>\n

    Mocks allow us to fake out dependencies<\/strong>, so we focus purely on what the class itself does.<\/p>\n

    \u2699 The three key annotations<\/h3>\n\n\n\n\n\n\n\n
    Annotation<\/th>\nWhere to use it<\/th>\nWhat it does<\/th>\n<\/tr>\n<\/thead>\n
    @Mock<\/code><\/td>\nIn pure unit tests<\/td>\nCreates a fake (mock) object of your dependency.<\/td>\n<\/tr>\n
    @InjectMocks<\/code><\/td>\nIn pure unit tests<\/td>\nCreates an instance of your class under test and injects the mocks<\/strong> automatically.<\/td>\n<\/tr>\n
    @MockBean<\/code><\/td>\nIn Spring Boot tests (@SpringBootTest<\/code>)<\/td>\nReplaces a Spring Bean in the application context<\/strong> with a mock.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

    \ud83d\udd0d The difference, with a story<\/h3>\n

    \ud83d\udc47 Example scenario<\/h4>\n

    Imagine we have:<\/p>\n

      \n
    • OrderService<\/code> that depends on OrderRepository<\/code>.<\/li>\n
    • OrderController<\/code> that depends on OrderService<\/code>.<\/li>\n<\/ul>\n

      OrderController \u2192 OrderService \u2192 OrderRepository<\/strong><\/p>\n

      \ud83e\uddea Unit testing OrderService<\/code><\/h3>\n

      We want to test just the logic inside OrderService<\/code><\/strong>, no Spring, no HTTP.<\/p>\n

      \n@ExtendWith(MockitoExtension.class)\nclass OrderServiceTest {\n\n    @Mock\n    private OrderRepository orderRepository; \/\/ creates a fake object\n\n    @InjectMocks\n    private OrderService orderService; \/\/ real service, gets mock injected\n\n    @Test\n    void testGetOrder() {\n        when(orderRepository.findById(1))\n            .thenReturn(Optional.of(new Order(1, \"Laptop\")));\n\n        Order result = orderService.getOrder(1);\n\n        assertEquals(\"Laptop\", result.getName());\n        verify(orderRepository).findById(1);\n    }\n}\n<\/code><\/pre>\n
      \u2705 What exactly are we testing?<\/strong><\/p>\n
        \n
      • That OrderService<\/code> correctly calls orderRepository.findById()<\/code><\/li>\n
      • Returns the right order<\/li>\n
      • Nothing to do with Spring or HTTP.<\/li>\n<\/ul>\n
        \ud83d\ude80 Spring Boot test with @MockBean<\/code><\/h3>\n
        Now we want to test that Spring wiring works<\/strong>, i.e.<\/p>\n
          \n
        • OrderController<\/code> calls OrderService<\/code><\/li>\n
        • OrderService<\/code> calls OrderRepository<\/code><\/li>\n
          but we still don\u2019t want to hit a real DB.<\/p>\n
          \n@SpringBootTest\nclass OrderControllerTest {\n\n    @Autowired\n    private OrderController orderController; \/\/ real bean from Spring\n\n    @MockBean\n    private OrderRepository orderRepository; \/\/ replaces real bean with mock\n\n    @Test\n    void testGetOrder() {\n        when(orderRepository.findById(1))\n            .thenReturn(Optional.of(new Order(1, \"Laptop\")));\n\n        Order result = orderController.getOrder(1);\n\n        assertEquals(\"Laptop\", result.getName());\n        verify(orderRepository).findById(1);\n    }\n}\n<\/code><\/pre>\n
          \u2705 What exactly are we testing?<\/strong><\/p>\n
            \n
          • That Spring autowires everything properly.<\/li>\n
          • That controller \u2192 service \u2192 repository chain works.<\/li>\n<\/ul>\n
            \ud83c\udf10 Testing the HTTP endpoint<\/h3>\n
            Finally, test the actual HTTP API<\/strong>, still with mocked repository.<\/p>\n
            \n@SpringBootTest(webEnvironment = SpringBootTest.WebEnvironment.RANDOM_PORT)\n@AutoConfigureMockMvc\nclass OrderControllerHttpTest {\n\n    @Autowired\n    private MockMvc mockMvc;\n\n    @MockBean\n    private OrderRepository orderRepository;\n\n    @Test\n    void testGetOrderHttp() throws Exception {\n        when(orderRepository.findById(1))\n            .thenReturn(Optional.of(new Order(1, \"Laptop\")));\n\n        mockMvc.perform(get(\"\/orders\/1\"))\n               .andExpect(status().isOk())\n               .andExpect(jsonPath(\"$.name\").value(\"Laptop\"));\n    }\n}\n<\/code><\/pre>\n
            \u2705 Now we\u2019re testing:<\/strong><\/p>\n
              \n
            • The entire Spring Boot stack<\/li>\n
            • JSON serialization<\/li>\n
            • Correct HTTP status codes.<\/li>\n<\/ul>\n
              \ud83d\udcdd So when do I use what?<\/h3>\n\n\n\n\n\n\n\n
              You want to test…<\/th>\nUse this<\/th>\nWhy<\/th>\n<\/tr>\n<\/thead>\n
              Only class logic, very fast, no Spring<\/td>\n@Mock<\/code> + @InjectMocks<\/code><\/td>\nLet Mockito build your class & inject fakes<\/td>\n<\/tr>\n
              Wiring inside Spring context, no HTTP<\/td>\n@SpringBootTest<\/code> + @MockBean<\/code><\/td>\nSpring loads beans & you replace dependencies<\/td>\n<\/tr>\n
              The full HTTP REST endpoint<\/td>\n@SpringBootTest<\/code> + @AutoConfigureMockMvc<\/code> + @MockBean<\/code><\/td>\nTest full HTTP layer with JSON<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
              \ud83d\udd0d Under the hood: how does @InjectMocks<\/code> work?<\/h3>\n
              \n@InjectMocks\nprivate OrderService orderService;\n\n@Mock\nprivate OrderRepository orderRepository;\n<\/code><\/pre>\n
              Mockito sees that OrderService<\/code> needs OrderRepository<\/code> and automatically injects it, either via constructor or field. \u2705<\/p>\n
              \ud83e\udd47 Key takeaways<\/h3>\n
                \n
              • \u2705 Use @Mock<\/code> + @InjectMocks<\/code> for fast, isolated Java logic tests<\/strong>, no Spring needed.<\/li>\n
              • \u2705 Use @MockBean<\/code> to replace beans in Spring context<\/strong> when testing controllers or services inside a Spring Boot app.<\/li>\n
              • \u2705 Always clearly decide: \u201cAm I testing pure logic or Spring wiring or HTTP layer?\u201d<\/strong><\/li>\n<\/ul>\n
                \ud83c\udf89 Hope this clears it up once and for all.<\/h3>\n
                If you liked it, drop a \u2b50 or share it with your team \u2014 so everyone stops being confused by @Mock<\/code>, @InjectMocks<\/code>, and @MockBean<\/code> forever!<\/p>\n","protected":false},"excerpt":{"rendered":"
                \ud83c\udfaf The Ultimate Guide to @Mock, @InjectMocks and @MockBean in Spring Boot Testing \u2705 By the end, you\u2019ll know exactly when to use each, how they work under the hood, and what you\u2019re truly testing. \ud83d\ude80 Why do we need mocks? When writing unit tests, you want to test your business logic in isolation, without […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[9],"tags":[],"class_list":["post-873","post","type-post","status-publish","format-standard","hentry","category-java"],"_links":{"self":[{"href":"https:\/\/www.alerainfotech.com\/home\/wp-json\/wp\/v2\/posts\/873","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.alerainfotech.com\/home\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.alerainfotech.com\/home\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.alerainfotech.com\/home\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.alerainfotech.com\/home\/wp-json\/wp\/v2\/comments?post=873"}],"version-history":[{"count":4,"href":"https:\/\/www.alerainfotech.com\/home\/wp-json\/wp\/v2\/posts\/873\/revisions"}],"predecessor-version":[{"id":878,"href":"https:\/\/www.alerainfotech.com\/home\/wp-json\/wp\/v2\/posts\/873\/revisions\/878"}],"wp:attachment":[{"href":"https:\/\/www.alerainfotech.com\/home\/wp-json\/wp\/v2\/media?parent=873"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.alerainfotech.com\/home\/wp-json\/wp\/v2\/categories?post=873"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.alerainfotech.com\/home\/wp-json\/wp\/v2\/tags?post=873"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}