Test method naming conventions in JUnit - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to name the test method following JUnit conventions.

JUnit

public class CalculatorTest {
    @Test
    public void [1]() {
        // test code here
    }
}

Drag options to blanks, or click blank then click option'

AtestAddition

BAdditionTest

CaddTestMethod

DcalculateAdd

Attempts:

3 left

💡 Hint

Common Mistakes

Using method names that do not start with 'test' or are unclear about the tested feature.

The method name testAddition clearly indicates it is a test for addition, following common JUnit naming conventions.

2fill in blank

medium

Complete the test method name to describe the expected behavior.

JUnit

public class UserServiceTest {
    @Test
    public void [1]() {
        // test code here
    }
}

Drag options to blanks, or click blank then click option'

AtestUserCreationFailsWhenNameIsNull

BuserCreationTest

CcreateUserTestMethod

DtestCreateUser

Attempts:

3 left

💡 Hint

Common Mistakes

Using vague or generic test method names that do not describe the test purpose.

The method name testUserCreationFailsWhenNameIsNull clearly describes the expected behavior and condition being tested.

3fill in blank

hard

Fix the error in the test method name to follow JUnit naming conventions.

JUnit

public class OrderServiceTest {
    @Test
    public void [1]() {
        // test code here
    }
}

Drag options to blanks, or click blank then click option'

AprocessOrderTestMethod

BtestProcessOrderSuccessfully

CorderProcess

DProcessOrderTest

Attempts:

3 left

💡 Hint

Common Mistakes

Using names that look like class names or omit the 'test' prefix.

The method name testProcessOrderSuccessfully follows the convention of starting with 'test' and describes the expected successful process.

4fill in blank

hard

Fill both blanks to complete a descriptive test method name and annotation.

JUnit

public class PaymentTest {
    [1]
    public void [2]() {
        // test code here
    }
}

Drag options to blanks, or click blank then click option'

A@Test

BtestPaymentFailsWithInsufficientFunds

C@Before

DpaymentTest

Attempts:

3 left

💡 Hint

Common Mistakes

Forgetting the @Test annotation or using unclear method names.

The annotation @Test marks the method as a test, and the method name testPaymentFailsWithInsufficientFunds clearly describes the test purpose.

5fill in blank

hard

Fill all three blanks to write a proper JUnit test method with annotation and descriptive name.

JUnit

public class LoginTest {
    [1]
    public void [2]() {
        // Arrange
        User user = new User("admin", "password");
        // Act
        boolean result = authService.login(user); 
        // Assert
        assertTrue([3]);
    }
}

Drag options to blanks, or click blank then click option'

A@Test

BtestLoginSucceedsWithValidCredentials

Cresult

DassertFalse

Attempts:

3 left

💡 Hint

Common Mistakes

Missing @Test annotation, unclear method names, or wrong assertion methods.

The @Test annotation marks the method as a test. The method name testLoginSucceedsWithValidCredentials describes the test. The assertion assertTrue(result) checks the login result is true.

Practice

1. Which of the following is the best practice for naming a JUnit test method?

easy

A. test1

B. check

C. shouldReturnTrueWhenInputIsValid

D. runTest

Solution

1. Step 1: Understand naming clarity

   Good test method names clearly describe what is tested and the expected behavior.

2. Step 2: Evaluate options

   shouldReturnTrueWhenInputIsValid uses camelCase and starts with 'should', describing expected behavior. Others are vague or generic.

3. Final Answer:

   shouldReturnTrueWhenInputIsValid -> Option C

4. Quick Check:

   Clear descriptive names = shouldReturnTrueWhenInputIsValid [OK]

Hint: Start test names with 'should' and describe behavior [OK]

Common Mistakes:

• Using vague names like 'test1' or 'check'
• Starting names with 'run' without context
• Not using camelCase for readability

2. Which of the following is a syntactically correct JUnit 5 test method name?

easy

A. 2ShouldReturnFalseWhenInputIsNull

B. shouldReturnFalseWhenInputIsNull

C. should return false when input is null

D. should-return_false_when_input_is_null

Solution

1. Step 1: Recall Java identifier rules for method names

   Java method names must be valid identifiers: start with letter/$_ , no spaces, hyphens, or starting digits; conventionally camelCase.

2. Step 2: Check each option

   shouldReturnFalseWhenInputIsNull uses valid camelCase. The option starting with '2' can't start with digit. The option with hyphen '-' is invalid. The option with spaces is invalid.

3. Final Answer:

   shouldReturnFalseWhenInputIsNull -> Option B

4. Quick Check:

   CamelCase method names = shouldReturnFalseWhenInputIsNull [OK]

Hint: Use camelCase valid Java identifiers, no spaces/hyphens/digit starts [OK]

Common Mistakes:

• Starting method names with digits
• Using hyphens or spaces in method names
• Ignoring Java identifier syntax rules

3. Given the following test method name, what behavior is it most likely testing?
shouldThrowExceptionWhenInputIsNegative

medium

A. The method tests that negative input is accepted without error

B. The method tests that negative input returns false

C. The method tests that input is positive

D. The method tests that an exception is thrown for negative input

Solution

1. Step 1: Analyze the method name parts

   The name starts with 'shouldThrowException' indicating expected exception behavior.

2. Step 2: Understand the condition

   'WhenInputIsNegative' means the test triggers when input is negative.

3. Final Answer:

   The method tests that an exception is thrown for negative input -> Option D

4. Quick Check:

   Method name meaning = exception thrown on negative input [OK]

Hint: Look for 'should' + action + condition in test names [OK]

Common Mistakes:

• Ignoring 'ThrowException' meaning
• Confusing exception with return values
• Misreading the condition part of the name

4. Identify the problem in this JUnit test method name:
testshouldReturnTrueWhenValid

medium

A. It mixes 'test' prefix with 'should' which is redundant

B. It uses invalid characters

C. It is too short

D. It does not start with a verb

Solution

1. Step 1: Understand naming redundancy

   Using both 'test' prefix and 'should' is redundant and not recommended.

2. Step 2: Check other options

   No invalid characters are present, length is sufficient, and 'should' implies verb usage.

3. Final Answer:

   It mixes 'test' prefix with 'should' which is redundant -> Option A

4. Quick Check:

   Redundant prefixes = test + should [OK]

Hint: Avoid combining 'test' prefix with 'should' in names [OK]

Common Mistakes:

• Using both 'test' and 'should' together
• Assuming length affects correctness
• Ignoring naming conventions for verbs

5. You want to write a JUnit test method name that clearly shows it tests if a user login fails when the password is empty. Which is the best name?

hard

A. shouldFailLoginWhenPasswordIsEmpty

B. testLoginFailEmptyPassword

C. loginFailsEmptyPassword

D. failLoginEmptyPasswordTest

Solution

1. Step 1: Check clarity and style

   shouldFailLoginWhenPasswordIsEmpty uses 'should' + verb + condition, making it clear and readable.

2. Step 2: Evaluate other options

   Options B, C, and D are less clear or mix styles, making them harder to understand quickly.

3. Final Answer:

   shouldFailLoginWhenPasswordIsEmpty -> Option A

4. Quick Check:

   Clear, descriptive, camelCase with 'should' = shouldFailLoginWhenPasswordIsEmpty [OK]

Hint: Use 'should' + action + condition for clear test names [OK]

Common Mistakes:

• Using unclear or mixed naming styles
• Omitting 'should' for behavior clarity
• Using underscores or inconsistent casing