Multiple parameter types in JUnit

Introduction

Using multiple parameter types lets you test a method with different kinds of inputs in one test. This helps find bugs faster and saves time.

You want to test a method that takes more than one input value.

You want to check how a method behaves with different combinations of inputs.

You want to avoid writing many similar test methods for different input types.

You want to improve test coverage by testing various input scenarios.

You want to keep your test code clean and organized.

Syntax

JUnit

import org.junit.jupiter.params.ParameterizedTest;
import org.junit.jupiter.params.provider.CsvSource;

class TestClass {
  @ParameterizedTest
  @CsvSource({
    "input1, 10",
    "input2, 20"
  })
  void testMethod(String param1, int param2) {
    // test code here
  }
}

@ParameterizedTest marks the test to run multiple times with different inputs.

@CsvSource provides pairs of values separated by commas for each test run.

Examples

This test checks the length of different fruit names using a String and an int parameter.

JUnit

import org.junit.jupiter.params.ParameterizedTest;
import org.junit.jupiter.params.provider.CsvSource;
import static org.junit.jupiter.api.Assertions.assertEquals;

class FruitTest {
  @ParameterizedTest
  @CsvSource({
    "apple, 5",
    "banana, 6"
  })
  void testFruitLength(String fruit, int length) {
    assertEquals(length, fruit.length());
  }
}

This test checks if the sum of two integers matches the expected result.

JUnit

import org.junit.jupiter.params.ParameterizedTest;
import org.junit.jupiter.params.provider.CsvSource;
import static org.junit.jupiter.api.Assertions.assertEquals;

class SumTest {
  @ParameterizedTest
  @CsvSource({
    "10, 20, 30",
    "5, 15, 20"
  })
  void testSum(int a, int b, int expectedSum) {
    assertEquals(expectedSum, a + b);
  }
}

Sample Program

This test runs the add method with three sets of integer inputs and checks if the sum is correct each time.

JUnit

import static org.junit.jupiter.api.Assertions.assertEquals;
import org.junit.jupiter.params.ParameterizedTest;
import org.junit.jupiter.params.provider.CsvSource;

public class CalculatorTest {

  @ParameterizedTest
  @CsvSource({
    "2, 3, 5",
    "10, 20, 30",
    "5, 7, 12"
  })
  void testAdd(int a, int b, int expected) {
    Calculator calc = new Calculator();
    assertEquals(expected, calc.add(a, b));
  }
}

class Calculator {
  int add(int x, int y) {
    return x + y;
  }
}

Important Notes

Use @CsvSource for simple multiple parameters separated by commas.

Ensure parameter types in the test method match the types in the CsvSource.

Each line in @CsvSource represents one test run with its parameters.

Summary

Multiple parameter types let you test methods with different inputs easily.

@ParameterizedTest with @CsvSource is a simple way to provide multiple inputs.

This approach saves time and improves test coverage.

Practice

1. What is the main benefit of using @ParameterizedTest with multiple parameter types in JUnit?

easy

A. It makes tests run faster by skipping assertions.

B. It automatically fixes bugs in the tested code.

C. It allows running the same test method with different input values easily.

D. It generates test reports without writing any code.

Solution

1. Step 1: Understand the purpose of @ParameterizedTest

   @ParameterizedTest lets you run one test method multiple times with different inputs.

2. Step 2: Recognize the benefit of multiple parameter types

   Using multiple parameter types means you can test various input combinations easily, improving coverage.

3. Final Answer:

   It allows running the same test method with different input values easily. -> Option C

4. Quick Check:

   @ParameterizedTest runs tests with many inputs = A [OK]

Hint: Think: same test, many inputs, easy coverage [OK]

Common Mistakes:

• Confusing parameterized tests with automatic bug fixing
• Believing it skips assertions to run faster
• Assuming it generates reports without code

2. Which of the following is the correct syntax to provide multiple parameters of different types using @CsvSource in JUnit?

easy

A. @CsvSource({"1, 'test', true", "2, 'check', false"})

B. @CsvSource(1, 'test', true; 2, 'check', false)

C. @CsvSource([1, 'test', true], [2, 'check', false])

D. @CsvSource("1; 'test'; true", "2; 'check'; false")

Solution

1. Step 1: Recall the correct @CsvSource format

   @CsvSource expects an array of strings, each string with comma-separated values.

2. Step 2: Check each option's syntax

   @CsvSource({"1, 'test', true", "2, 'check', false"}) uses curly braces and comma-separated values inside quotes, which is correct syntax.

3. Final Answer:

   @CsvSource({"1, 'test', true", "2, 'check', false"}) -> Option A

4. Quick Check:

   @CsvSource uses braces and comma-separated strings = C [OK]

Hint: Look for braces and comma-separated quoted strings [OK]

Common Mistakes:

• Using semicolons instead of commas
• Not enclosing the whole list in braces
• Using square brackets instead of braces

3. Given the following JUnit test method, what will be the output when it runs?

@ParameterizedTest
@CsvSource({"2, 3, 5", "4, 5, 9", "1, 1, 3"})
void testSum(int a, int b, int expected) {
    assertEquals(expected, a + b);
}

medium

A. Syntax error prevents tests from running.

B. All tests pass.

C. All tests fail.

D. Two tests pass, one test fails.

Solution

1. Step 1: Check each test case's expected vs actual sum

   Test 1: 2+3=5 matches expected 5 (pass). Test 2: 4+5=9 matches expected 9 (pass). Test 3: 1+1=2 but expected 3 (fail).

2. Step 2: Determine overall test results

   Two tests pass, one test fails due to wrong expected value.

3. Final Answer:

   Two tests pass, one test fails. -> Option D

4. Quick Check:

   Sum matches expected except last = A [OK]

Hint: Add inputs and compare to expected for each case [OK]

Common Mistakes:

• Assuming all pass without checking expected values
• Ignoring the failing test case
• Thinking syntax error occurs due to quotes

4. Identify the error in this JUnit parameterized test using multiple parameter types:

@ParameterizedTest
@CsvSource({"10, 20", "30, 40"})
void testMultiply(int a, int b, int expected) {
    assertEquals(expected, a * b);
}

medium

A. The @CsvSource syntax is incorrect; it should use semicolons instead of commas.

B. The method expects three parameters but only two are provided in @CsvSource.

C. The assertEquals arguments are reversed.

D. The test method should not use @ParameterizedTest with @CsvSource.

Solution

1. Step 1: Compare method parameters with @CsvSource values

   The method expects three parameters (int a, int b, int expected), but each @CsvSource entry has only two values.

2. Step 2: Identify mismatch causing error

   Missing the third parameter in @CsvSource causes a runtime error due to parameter count mismatch.

3. Final Answer:

   The method expects three parameters but only two are provided in @CsvSource. -> Option B

4. Quick Check:

   Parameter count mismatch = B [OK]

Hint: Count parameters in method and CsvSource entries [OK]

Common Mistakes:

• Thinking commas are wrong separators
• Assuming assertEquals argument order causes error
• Believing @ParameterizedTest can't be used with @CsvSource

5. You want to test a method isValidUser(String username, int age, boolean active) using @ParameterizedTest with multiple parameter types. Which @CsvSource entry correctly represents a test case with username "alice", age 30, and active status true?

hard

A. "alice, 30, true"

B. "'alice', 30, true"

C. "alice; 30; true"

D. "alice, '30', 'true'"

Solution

1. Step 1: Understand @CsvSource value format

   Values are comma-separated strings; quotes around strings are optional unless spaces or commas inside.

2. Step 2: Evaluate each option

   "alice, 30, true" correctly uses commas without extra quotes. "'alice', 30, true" adds unnecessary quotes around username. "alice; 30; true" uses semicolons which is invalid. "alice, '30', 'true'" quotes numeric and boolean values unnecessarily.

3. Final Answer:

   "alice, 30, true" -> Option A

4. Quick Check:

   Comma-separated values without extra quotes = D [OK]

Hint: Use commas, quote strings only if needed [OK]

Common Mistakes:

• Using semicolons instead of commas
• Adding quotes around numbers or booleans
• Quoting strings unnecessarily