Tooling for Javas
Java tooling means the build and test tools around the language: Maven or Gradle for dependencies and builds, and JUnit with Mockito for automated testing. It belongs to the Build and Test stage and turns loose source files into a reproducible project that compiles, tests and packages the same way on every machine.
Stage: Build and Test · Part of the Java roadmap · Last reviewed 19 November 2026
What to learn in Tooling
- Declare dependencies in a pom.xml or build.gradle file and resolve them
- Run the Maven lifecycle phases compile, test and package
- Write a JUnit 5 test with assertions and a parameterised case
- Mock a collaborator with Mockito to test a class in isolation
- Explain dependency scopes such as compile, test and runtime
Tooling interview questions
What is the difference between Maven and Gradle?
Both manage dependencies and builds. Maven uses declarative XML and a fixed lifecycle of phases, which makes projects uniform. Gradle uses a Groovy or Kotlin script, is more flexible, and supports incremental builds and caching, often making large builds faster.
When should you use a mock in a unit test?
Use a mock to replace a collaborator that is slow, nondeterministic or external, such as a database or HTTP client, so the test checks only your class. Avoid mocking simple value objects or the class under test, since over-mocking makes tests brittle.
Where Tooling fits in the Java roadmap
Tooling belongs to the Build and Test stage (advanced level), which takes about 32 hours. Ship Java.