JMockit (or any mocking framework) will allow you to assert that the code that you call to hit the database actually gets called in your controller. Setting up the mocks and writing the test is going to depend on what you’re doing, but in general what you are going to want to do to test the controller is define expectations around the code you mentioned in your Application JAR that hits the database, and from your test you want to exercise your controller’s execute method. In my example I’m expecting the mockService to have its getModel method called and return a model object. You can set yours up simiarly. The controller also will be touching the HttpRequest which I have set up expectations for as well. Hope this helps!

I have a scenario where I have to write the TestCases using JMockit.
We are using JPF controllers for the portal applications.I have to write test cases for the JPF Controllers.Here the portal code is not allowed to hit any database directly instead we have to use the Application JAR in which there are methods which can hit the database.

I am in real confusion how to write jmockit test cases for this type of controllers..
Please help me

I looked for an easy way to automate the upload to a Maven repo a few weeks ago, but could not find one.
If someone knows how to do it without some huge effort, I would appreciate it.

Thanks

Your example test works fine, but two simplifications can be made.
First, the calls to “newEmptyProxy” are redundant, since JMockit already creates and assigns automatically an instance to each mock field.
Second, the call to “endRecording()” is no longer required in cases like this. JMockit will automatically switch from record to replay at the end of each Expectations initialization block.