Test naming conventions deep dive in JUnit - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to name the test method following the common JUnit convention.

JUnit

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

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

ArunTest

BTest1

CshouldReturnTrueWhenInputIsValid

Dcheck

Attempts:

3 left

💡 Hint

Common Mistakes

Using vague names like 'Test1' or 'check' that don't explain the test purpose.

The method name shouldReturnTrueWhenInputIsValid clearly describes what the test checks, following good JUnit naming conventions.

2fill in blank

medium

Complete the code to follow the 'given_when_then' test naming style.

JUnit

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

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

AgivenValidUser_whenLogin_thenSuccess

BtestLogin

CloginTestCase

DcheckLogin

Attempts:

3 left

💡 Hint

Common Mistakes

Using short or generic names that don't describe the test steps.

The name givenValidUser_whenLogin_thenSuccess follows the 'given_when_then' style, making the test purpose clear.

3fill in blank

hard

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

JUnit

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

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

AshouldThrowExceptionWhenInputIsNull

B123testMethod

CtestMethod!

DTest Method

Attempts:

3 left

💡 Hint

Common Mistakes

Starting method names with numbers or including spaces/special characters.

Method names must be valid Java identifiers. shouldThrowExceptionWhenInputIsNull is valid and descriptive.

4fill in blank

hard

Fill both blanks to create a test method name that follows the 'should_when' pattern and uses camelCase.

JUnit

@Test
public void [1]_[2]() {
    // test code here
}

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

AshouldReturnTrue

BwhenInputIsValid

CWhenInputIsNull

Dshould_return_false

Attempts:

3 left

💡 Hint

Common Mistakes

Using underscores inside camelCase words or capitalizing the second part incorrectly.

The combination shouldReturnTrue_whenInputIsValid follows the 'should_when' pattern and camelCase style.

5fill in blank

hard

Fill all three blanks to create a descriptive test method name using the 'given_when_then' style with camelCase.

JUnit

@Test
public void [1]_[2]_[3]() {
    // test code here
}

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

AgivenUserIsLoggedIn

BwhenUserClicksLogout

CthenSessionEnds

DGivenUserIsLoggedIn

Attempts:

3 left

💡 Hint

Common Mistakes

Capitalizing words incorrectly or mixing styles.

The name givenUserIsLoggedIn_whenUserClicksLogout_thenSessionEnds clearly describes the test scenario in camelCase.

Practice

1. Which of the following test method names best follows good JUnit test naming conventions?

easy

A. shouldReturnTrueWhenInputIsValid

B. test1

C. runTest

D. check

Solution

1. Step 1: Understand the purpose of test naming

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

2. Step 2: Evaluate each option

   shouldReturnTrueWhenInputIsValid uses a descriptive style 'shouldReturnTrueWhenInputIsValid' which explains behavior and condition. Options B, C, and D are vague and do not describe the test purpose.

3. Final Answer:

   shouldReturnTrueWhenInputIsValid -> Option A

4. Quick Check:

   Descriptive test names = shouldReturnTrueWhenInputIsValid [OK]

Hint: Pick the name that clearly states condition and expected result [OK]

Common Mistakes:

• Using generic names like 'test1' or 'runTest'
• Not describing expected behavior
• Using too short or unclear names

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

easy

A. void shouldReturnFalseWhenInputIsNull

B. test shouldReturnFalseWhenInputIsNull()

C. void shouldReturnFalseWhenInputIsNull()

D. void shouldReturnFalseWhenInputIsNull[]

Solution

1. Step 1: Recall JUnit 5 test method syntax

   JUnit 5 test methods must be void, have no parameters, and be annotated with @Test (annotation not shown here but method signature matters).

2. Step 2: Check method declarations

   void shouldReturnFalseWhenInputIsNull() is a valid Java method signature. test shouldReturnFalseWhenInputIsNull() has invalid syntax with 'test' keyword. void shouldReturnFalseWhenInputIsNull misses parentheses. void shouldReturnFalseWhenInputIsNull[] uses invalid brackets.

3. Final Answer:

   void shouldReturnFalseWhenInputIsNull() -> Option C

4. Quick Check:

   Valid Java method syntax = void shouldReturnFalseWhenInputIsNull() [OK]

Hint: Look for valid Java method syntax with parentheses [OK]

Common Mistakes:

• Omitting parentheses in method declaration
• Adding invalid keywords before method name
• Using brackets instead of parentheses

3. Given the test method name whenUserIsAdmin_thenAccessGranted(), what does this naming style indicate?

medium

A. The test checks that access is granted when the user is an admin

B. The test verifies that the user is an admin

C. The test denies access to admin users

D. The test runs only for admin users

Solution

1. Step 1: Analyze the naming pattern

   The name uses 'whenCondition_thenResult' style, describing the condition and expected outcome.

2. Step 2: Interpret the meaning

   'whenUserIsAdmin' is the condition, 'thenAccessGranted' is the expected result. So the test checks access granted for admin users.

3. Final Answer:

   The test checks that access is granted when the user is an admin -> Option A

4. Quick Check:

   whenCondition_thenResult = The test checks that access is granted when the user is an admin [OK]

Hint: Match 'when' condition with 'then' expected result [OK]

Common Mistakes:

• Confusing condition with expected result
• Assuming test denies access instead of granting
• Thinking test runs only for admin without checking outcome

4. Identify the problem in this test method name: testUserLoginSuccess

medium

A. It does not start with 'should'

B. It uses underscores which are not allowed

C. It is too long and complex

D. It lacks a clear description of the expected behavior

Solution

1. Step 1: Examine the test name clarity

   'testUserLoginSuccess' is vague; it does not explain what success means or under what condition.

2. Step 2: Check naming conventions

   Good names describe behavior and expected result clearly, e.g., 'shouldLoginSuccessfullyWithValidCredentials'. The given name lacks this clarity.

3. Final Answer:

   It lacks a clear description of the expected behavior -> Option D

4. Quick Check:

   Clear expected behavior needed = It lacks a clear description of the expected behavior [OK]

Hint: Look for missing expected outcome in test name [OK]

Common Mistakes:

• Assuming underscores are disallowed (they are allowed)
• Thinking length alone is a problem
• Believing 'should' prefix is mandatory

5. You want to write a test name for a method that verifies a payment fails when the credit card number is invalid. Which of these names best follows deep naming conventions?

hard

A. testPaymentInvalidCard

B. shouldFailPaymentForInvalidCardNumber

C. paymentFails

D. checkInvalidCardPayment

Solution

1. Step 1: Identify key elements in the test scenario

   The test checks payment failure due to invalid credit card number.

2. Step 2: Evaluate each option for clarity and completeness

   shouldFailPaymentForInvalidCardNumber clearly states expected behavior and condition. Options A, C, and D are less descriptive or ambiguous.

3. Final Answer:

   shouldFailPaymentForInvalidCardNumber -> Option B

4. Quick Check:

   Clear condition and expected result = shouldFailPaymentForInvalidCardNumber [OK]

Hint: Include condition and expected result in test name [OK]

Common Mistakes:

• Using vague or incomplete names
• Omitting the condition or expected outcome
• Using generic prefixes without details