Home/ Questions/Q 7417935
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-29T07:47:35+00:00

I have a web application built using Spring which contains some jobs. A typical

  • 0

I have a web application built using Spring which contains some jobs.

A typical job is to run through the database, get a list of modified customers, generate a file and FTP it. My question is, how to go about unit testing in this job?

Should I only write unit tests for each “step” of the job, like:

  • Test for the method which fetches the modified customers.
  • Test for file generation code.
  • Test for FTP’ing the code.

But in this case, I will miss the “integration” test case for the above job. Also, Emma reports there is untested code in form of the job.

Any thoughts appreciated.

Thanks!

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Unit testing is actually testing only one class at a time. That means you have to mock the dependencies. Spring is great for that.

    I would advice Mockito to do the mocking. It is a marvellous tool, and you will learn TDD which is also a way to write beautiful code.

    Integration test is another topic and requires another strategy.

    Testing against the database is done by extending AbstractTransactionalJUnit4SpringContextTests. You will find examples on the net. In general you also use an in memory db to make those tests (h2 is good for that). It can be done in the unit test phase.

    Generating the file can be done as unit test. You generate files and verify the proper content. Or errors…

    For the FTP part, I would say it’s more part of an integration test, unless you can spawn an FTP server from your build script.

    • 0