@ValueSource for simple values in JUnit - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to provide integer values to the test method using @ValueSource.

JUnit

@ParameterizedTest
@ValueSource([1])
void testWithInts(int number) {
    assertTrue(number > 0);
}

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

Aints = {1, 2, 3}

Bints = {0, -1, 2}

Cstrings = {"a", "b"}

Dints = {1, 2, 3, 4}

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'strings' instead of 'ints' for integer values.

Including negative or zero values when the test expects positive numbers.

The correct syntax to provide integer values is @ValueSource(ints = {1, 2, 3, 4}). This passes the integers 1, 2, 3, and 4 to the test method.

2fill in blank

medium

Complete the code to provide string values to the test method using @ValueSource.

JUnit

@ParameterizedTest
@ValueSource([1])
void testWithStrings(String word) {
    assertNotNull(word);
}

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

Astrings = {"apple", "banana", "cherry"}

Bints = {1, 2, 3}

Cdoubles = {1.0, 2.0}

Dchars = {'a', 'b'}

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'ints' or other types instead of 'strings'.

Passing characters instead of strings.

To pass string values, use @ValueSource(strings = {"apple", "banana", "cherry"}). This sends the strings to the test method.

3fill in blank

hard

Fix the error in the @ValueSource annotation to correctly provide double values.

JUnit

@ParameterizedTest
@ValueSource([1])
void testWithDoubles(double value) {
    assertTrue(value > 0.0);
}

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

Aints = {1, 2, 3}

Bdouble = {1.0, 2.5, 3.3}

Cdoubles = {1.0, 2.5, 3.3}

Dfloats = {1.0f, 2.5f}

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'double' instead of 'doubles'.

Using 'floats' instead of 'doubles'.

The correct attribute for double values is 'doubles'. So use @ValueSource(doubles = {1.0, 2.5, 3.3}).

4fill in blank

hard

Fill both blanks to create a test that uses @ValueSource to pass characters and asserts they are letters.

JUnit

@ParameterizedTest
@ValueSource([1])
void testWithChars(char letter) {
    assertTrue(Character.[2](letter));
}

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

Achars = {'a', 'b', 'c'}

BisDigit

CisLetter

Dchars = {'1', '2', '3'}

Attempts:

3 left

💡 Hint

Common Mistakes

Passing digits instead of letters in chars.

Using 'isDigit' instead of 'isLetter' in the assertion.

Use @ValueSource(chars = {'a', 'b', 'c'}) to pass characters. The assertion uses Character.isLetter(letter) to check if the character is a letter.

5fill in blank

hard

Fill all three blanks to create a test using @ValueSource with strings and assert their length is greater than zero.

JUnit

@ParameterizedTest
@ValueSource([1])
void testStringLength([2] word) {
    assertTrue(word.[3]() > 0);
}

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

Astrings = {"test", "java", "junit"}

BString

Clength

Dints = {1, 2, 3}

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'ints' instead of 'strings' in @ValueSource.

Using wrong parameter type like 'int' instead of 'String'.

Calling a non-existent method instead of 'length()'.

Use @ValueSource(strings = {"test", "java", "junit"}) to pass strings. The method parameter type is String. The assertion calls word.length() to check the string length.

Practice

1. What is the main purpose of using @ValueSource in JUnit tests?

easy

A. To run the same test multiple times with different simple input values

B. To create a new test class automatically

C. To skip tests based on conditions

D. To generate random test data during runtime

Solution

1. Step 1: Understand the role of @ValueSource

   @ValueSource provides a list of simple values to run a test repeatedly with each value.

2. Step 2: Compare options with this role

   Only To run the same test multiple times with different simple input values correctly describes running the same test multiple times with different inputs.

3. Final Answer:

   To run the same test multiple times with different simple input values -> Option A

4. Quick Check:

   @ValueSource = run test multiple times [OK]

Hint: Remember: @ValueSource repeats tests with simple inputs [OK]

Common Mistakes:

• Thinking @ValueSource creates new test classes
• Confusing @ValueSource with conditional test skipping
• Assuming it generates random data

2. Which of the following is the correct syntax to use @ValueSource with integers in JUnit 5?

easy

A. @ValueSource(numbers = {1, 2, 3})

B. @ValueSource(values = {1, 2, 3})

C. @ValueSource(int = {1, 2, 3})

D. @ValueSource(ints = {1, 2, 3})

Solution

1. Step 1: Recall correct attribute name for integers

   The attribute for integer arrays in @ValueSource is ints.

2. Step 2: Check syntax correctness

   @ValueSource(ints = {1, 2, 3}) uses @ValueSource(ints = {1, 2, 3}), which is the correct syntax.

3. Final Answer:

   @ValueSource(ints = {1, 2, 3}) -> Option D

4. Quick Check:

   ints attribute = correct syntax [OK]

Hint: Use 'ints' attribute for integer arrays in @ValueSource [OK]

Common Mistakes:

• Using wrong attribute names like 'values' or 'numbers'
• Missing 's' in 'ints'
• Using singular 'int' instead of 'ints'

3. Given the following test method, what will be the output when run?

@ParameterizedTest
@ValueSource(strings = {"apple", "banana"})
void testLength(String fruit) {
    System.out.println(fruit.length());
}

medium

A. 5 and 6 printed on separate lines

B. 6 and 5 printed on separate lines

C. Only 5 printed once

D. Compilation error due to missing annotation

Solution

1. Step 1: Identify input values from @ValueSource

   The strings are "apple" (length 5) and "banana" (length 6).

2. Step 2: Understand test execution

   The test runs twice, printing the length of each string in order: 5 then 6.

3. Final Answer:

   5 and 6 printed on separate lines -> Option A

4. Quick Check:

   "apple"=5, "banana"=6 [OK]

Hint: Check string lengths in order given by @ValueSource [OK]

Common Mistakes:

• Mixing order of outputs
• Assuming only one run instead of multiple
• Forgetting @ParameterizedTest annotation

4. Identify the error in this JUnit 5 test using @ValueSource:

@ParameterizedTest
@ValueSource(strings = {"test", null})
void testNotNull(String input) {
    assertNotNull(input);
}

medium

A. Missing @Test annotation

B. assertNotNull is not a valid assertion

C. Using null in @ValueSource causes a runtime error

D. Strings array must not contain more than one value

Solution

1. Step 1: Check @ValueSource limitations

   @ValueSource does not support null values; including null causes errors.

2. Step 2: Verify other parts

   assertNotNull is valid, @ParameterizedTest is present, and multiple strings are allowed.

3. Final Answer:

   Using null in @ValueSource causes a runtime error -> Option C

4. Quick Check:

   null not allowed in @ValueSource [OK]

Hint: Never put null in @ValueSource arrays [OK]

Common Mistakes:

• Thinking null is allowed in @ValueSource
• Confusing @ParameterizedTest with @Test
• Believing assertNotNull is invalid

5. How can you use @ValueSource to test a method that accepts both int and long values?

hard

A. Use @ValueSource with ints only and cast to long inside the test

B. Use two separate test methods each with @ValueSource for ints and longs

C. Use @ValueSource with longs only and cast to int inside the test

D. Use @ValueSource with mixed int and long arrays in one method

Solution

1. Step 1: Understand @ValueSource type restrictions

   @ValueSource attributes accept only one primitive type array per annotation (ints or longs, not mixed).

2. Step 2: Choose approach to test both types

   To test both int and long inputs, create two test methods each with its own @ValueSource for the correct type.

3. Final Answer:

   Use two separate test methods each with @ValueSource for ints and longs -> Option B

4. Quick Check:

   Separate methods for int and long [OK]

Hint: Use separate tests for different primitive types [OK]

Common Mistakes:

• Trying to mix int and long in one @ValueSource
• Casting inside test instead of separate methods
• Assuming @ValueSource supports mixed types