How to test a controller with constructor injection by MockMvc

Question

I have a controller with constructor injection

@RestController
@RequestMapping("/user")
public class MainController {

    private final UserMapper userMapper; // autowired by constructor below

    public MainController(UserMapper userMapper) {
        this.userMapper = userMapper;
    }

    @RequestMapping("/getChannels")
    public String index() {
        LoginUser user = userMapper.getUserByName("admin");
        return "Channels: " + user.getChannels();
    }
}

It's a simple class which is working fine. However when I tried to run a JUnit testing with below class I got an error.

@RunWith(SpringJUnit4ClassRunner.class)
@WebAppConfiguration
public class MainControllerTest {

    private MockMvc mvc;
    private final UserMapper userMapper;

    public MainControllerTest(UserMapper userMapper) {
        this.userMapper = userMapper;
    }

    @Before
    public void setUp() throws Exception {
        mvc = MockMvcBuilders.standaloneSetup(new MainController(userMapper)).build();
    }

    ......

The error is:

java.lang.Exception: Test class should have exactly one public zero-argument constructor

I was confused by above error message that how could I inject the userMapper with a zero-argument constructor? I know it's possible to add the @Autowired for userMapper in MainController however the field injection is not recommended. Please could anybody guide me a suitable way for both constructor injection and MockMvc testing. Thanks.

Answer 1

Other answers talk about using annotations, but here your problem doesn't have any relation to using annotations. keep in mind as spring 4.3+ you don't need to annotate constructor for dependencies, see more here.

In fact You don't need to try to simulate constructor injection in your Test class (MainControllerTest). All you need is to declaring UserMapper as spring component in your application context and in your test class it will be auto injected in your controller as your running application.

Whats your error mean: All of Junit Test classes as error message says should have exactly one public zero-argument constructor that's because Junit Test suites in cases like your scenario doesn't know how to instantiate Test class.