Java Test Automation and JUnit Intern

A test suite that takes twenty two minutes to run is a test suite people quietly start skipping. Ours takes twenty two minutes.

Your assignment

Across this two month internship in Hyderabad you will attack that number from both ends. You will replace the heavyweight Spring context in roughly forty unit tests with plain constructor injection and Mockito, move the genuinely integration-level cases onto Testcontainers so they stop fighting over one shared MySQL instance, and tag the slow suite so it runs nightly instead of on every push. You will also add coverage where it actually matters, starting with the billing calculator nobody wants to touch.

The trade we are offering

This internship is unpaid and we would rather be direct about that than bury it. What you get in return is two months reading production Java 17 written by people who have maintained it for years, a mentor who reviews every pull request you raise, and a portfolio result you can state precisely in an interview: a build that went from twenty two minutes to under five.

Who should apply

Final-year students and recent graduates. You should have written JUnit tests for your own projects and be able to explain what a mock actually replaces.