Basic JUnit Interview Questions (Freshers)
1. What is JUnit and why is it used?
JUnit is a unit testing framework for Java that enables developers to write and run repeatable automated tests. It ensures code reliability by verifying that individual units of code work correctly and provides immediate feedback on failures.[1][5]
2. What are the main advantages of using JUnit?
JUnit automates testing, supports test-driven development (TDD), integrates with build tools, provides clear test progress visualization, and catches bugs early in the development process.[1][5][6]
3. Where do you find JUnit classes in a Java project?
JUnit classes are found in the org.junit package for JUnit 4 and org.junit.jupiter.api for JUnit 5, typically added as dependencies in build files.[2][4]
4. What is a unit test case in JUnit?
A unit test case is a piece of code that tests a specific method or functionality to ensure it produces expected results. JUnit provides the framework to organize and execute these tests efficiently.[3]
5. How do you run JUnit tests?
JUnit tests can be run from IDEs like Eclipse or IntelliJ, command line using java org.junit.runner.JUnitCore, or automatically through build tools during compilation.[1][2]
6. What is the purpose of assertions in JUnit?
Assertions compare expected and actual results in tests. Common methods include assertEquals(), assertTrue(), and assertNull() to validate test outcomes.[1][4]
@Test
public void testAddition() {
assertEquals(4, 2 + 2);
}7. Explain the @Test annotation in JUnit.
The @Test annotation marks a method as a test case. In JUnit 5, it supports parameters like expected exceptions, while JUnit 4 uses it simply to identify test methods.[4][5]
8. What does the green bar and red bar mean in JUnit?
A green bar indicates all tests passed successfully, while a red bar shows at least one test failure, providing visual feedback on test execution status.[3]
9. Can JUnit tests be organized into test suites?
Yes, JUnit supports test suites using @Suite annotation in JUnit 5 or SuiteClasses in JUnit 4 to group multiple test classes for execution together.[1]
10. What is JUnitCore?
JUnitCore is a facade class that provides a simple way to run tests and suites from the command line or main methods, returning a result summary.[2]
Intermediate JUnit Interview Questions (1-3 Years Experience)
11. What are the differences between JUnit 4 and JUnit 5?
JUnit 5 has a modular architecture with JUnit Platform, Jupiter, and Vintage; supports Java 8+ features; uses @BeforeEach/@AfterEach instead of @Before/@After; and offers @Nested and @TestFactory annotations not available in JUnit 4.[1][4][5]
12. Explain lifecycle methods in JUnit.
Lifecycle methods manage test setup and teardown: @BeforeAll/@AfterAll run once per class, @BeforeEach/@AfterEach run before/after each test method.[5][7]
@BeforeAll
static void initAll() { }
@BeforeEach
void init() { }
@Test
void testMethod() { }
@AfterEach
void tearDown() { }13. What is the difference between @Before and @BeforeEach?
@Before (JUnit 4) and @BeforeEach (JUnit 5) both run before each test method, but @BeforeEach requires static methods for class-level setup with @BeforeAll.[4][8]
14. How do you test for exceptions in JUnit 5?
Use assertThrows() to verify exceptions: assertThrows(IllegalArgumentException.class, () -> method()).[1][7]
@Test
void testException() {
assertThrows(NullPointerException.class, () -> {
methodThatThrowsNPE();
});
}15. What is the @Ignore annotation used for?
@Ignore (JUnit 4) or @Disabled (JUnit 5) skips test execution, useful for temporarily excluding flaky or unfinished tests.[2][6]
16. How do you use @DisplayName in JUnit?
@DisplayName provides a custom, readable name for tests in reports, improving test output clarity.[1]
@Test
@DisplayName("Test calculator addition")
void testAddition() { }17. What is the purpose of @RunWith in JUnit 4?
@RunWith specifies a custom test runner like Parameterized or SpringRunner to extend JUnit functionality.[6]
18. How does JUnit handle test failures?
JUnit reports only the first failure per test method to keep output focused, continuing execution of other tests.[4]
19. Write a JUnit test for a palindrome checker.
This test verifies a method checking if a string is a palindrome using assertions.[1]
@Test
public void testIsPalindrome() {
assertTrue(palindromeChecker.isPalindrome("radar"));
assertFalse(palindromeChecker.isPalindrome("hello"));
}20. What are test fixtures in JUnit?
Test fixtures are setup code using @BeforeEach/@AfterEach that prepares consistent test data and state for reliable testing.[2][7]
Advanced JUnit Interview Questions (3-6 Years Experience)
21. At Atlassian, how would you create nested test classes in JUnit 5?
Use @Nested annotation for logical grouping of related tests within a class, each with independent lifecycle.[1][5]
@Nested
class AdditionTests {
@Test void testAddPositive() { }
}22. Explain code coverage types relevant to JUnit testing.
Statement coverage tests every line; decision coverage tests true/false branches; path coverage tests all possible execution paths.[4]
23. How do you integrate JUnit with Maven?
Add JUnit dependency to pom.xml and configure Surefire plugin to automatically run tests during build: mvn test.[1]
24. Write a parameterized test in JUnit 5.
Use @ParameterizedTest with @ValueSource for multiple inputs in one test method.[5]
@ParameterizedTest
@ValueSource(strings = {"a", "aa", "aba"})
void testPalindrome(String input) {
assertTrue(palindromeChecker.isPalindrome(input));
}25. In a Salesforce scenario, how do you test repeated assertions?
Use multiple assert statements or assertAll() to group assertions, ensuring all are evaluated even if some fail.[1]
@Test
void multipleAssertions() {
assertAll("Math checks",
() -> assertEquals(2, 1+1),
() -> assertEquals(3, 2+1));
}26. What is @TestFactory in JUnit 5?
@TestFactory dynamically generates tests at runtime using DynamicTest.stream(), ideal for data-driven tests.[1][5]
27. How do you test private methods with JUnit?
Use Java reflection to access private methods or refactor code to test through public interfaces for better design.[5]
28. For Adobe projects, explain test timeout handling.
Use @Timeout annotation to fail tests exceeding duration: @Timeout(100) for milliseconds.[5]
@Test
@Timeout(10)
void testPerformance() { }29. How do you handle test dependencies in JUnit?
Use @TestMethodOrder with @Order annotation for execution sequence control, or design independent tests.[5]
30. In a Paytm-like scenario with database interaction, how do you mock dependencies?
Configure fixtures with mock objects in @BeforeEach to isolate unit tests from external dependencies like databases.[1][7]
@Mock
DatabaseService dbService;
@BeforeEach
void setup() {
MockitoAnnotations.openMocks(this);
}