@CsvFileSource for external CSV in JUnit - Build an Automation Script

Automate parameterized test using @CsvFileSource with external CSV file

Preconditions (3)

Step 1: Create a parameterized test method annotated with @ParameterizedTest

Step 2: Use @CsvFileSource to load data from 'test-data.csv'

Step 3: For each row, receive the input string and expected length as parameters

Step 4: Assert that the length of the input string equals the expected length

✅ Expected Result: The test runs once per CSV row and passes if all string lengths match the expected values

Automation Requirements - JUnit 5

Assertions Needed:

Assert that input string length equals expected length

Best Practices:

Use @ParameterizedTest with @CsvFileSource for clean data-driven tests

Place CSV file in 'src/test/resources' for easy classpath access

Use meaningful assertion messages

Keep test method simple and focused

Automated Solution

JUnit

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

public class CsvFileSourceTest {

    @ParameterizedTest
    @CsvFileSource(resources = "/test-data.csv", numLinesToSkip = 1)
    void testStringLength(String input, int expectedLength) {
        assertEquals(expectedLength, input.length(),
            () -> "Expected length " + expectedLength + " but got " + input.length() + " for input: '" + input + "'");
    }
}

The test class CsvFileSourceTest uses JUnit 5's @ParameterizedTest to run the test method multiple times with different inputs.

The @CsvFileSource annotation loads data from the external CSV file test-data.csv located in src/test/resources. The resources path starts with a slash to indicate classpath root.

numLinesToSkip = 1 skips the header row in the CSV file.

The test method testStringLength receives two parameters: the input string and the expected length from each CSV row.

Inside the method, assertEquals checks if the actual string length matches the expected length, with a clear message to help debug if it fails.

This approach keeps tests clean, readable, and easy to maintain.

Common Mistakes - 4 Pitfalls

{'mistake': 'Placing the CSV file outside the classpath or wrong folder', 'why_bad': 'JUnit cannot find the CSV file, causing test failures or errors', 'correct_approach': "Place the CSV file inside 'src/test/resources' so it is on the classpath"}

{'mistake': 'Not skipping the header line in the CSV file', 'why_bad': 'The header row is treated as test data, causing parsing errors or wrong test inputs', 'correct_approach': "Use 'numLinesToSkip = 1' in @CsvFileSource to skip the header"}

Mismatch between CSV columns and test method parameters

{'mistake': 'Using relative file paths instead of classpath resource paths', 'why_bad': 'JUnit cannot locate the file if path is incorrect', 'correct_approach': "Use resource path starting with '/' to load from classpath"}

Bonus Challenge

Extend the test to also verify that the input string is not empty for each CSV row

Show Hint

Practice

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

easy

A. To run the same test multiple times with different data from a CSV file

B. To write data into a CSV file during test execution

C. To generate random test data automatically

D. To skip tests based on CSV file content

Solution

1. Step 1: Understand the role of @CsvFileSource

   @CsvFileSource provides external CSV data to parameterized tests, allowing multiple runs with different inputs.

2. Step 2: Compare options with this role

   Only To run the same test multiple times with different data from a CSV file correctly describes running tests multiple times with CSV data. Others describe unrelated actions.

3. Final Answer:

   To run the same test multiple times with different data from a CSV file -> Option A

4. Quick Check:

   @CsvFileSource runs tests with CSV data = B [OK]

Hint: Remember: @CsvFileSource feeds test data, not writes or skips [OK]

Common Mistakes:

• Thinking @CsvFileSource writes data instead of reading
• Confusing it with random data generation
• Assuming it controls test skipping

2. Which of the following is the correct syntax to skip the header line in a CSV file when using @CsvFileSource?

easy

A. @CsvFileSource(resources = "/data.csv", skipLines = 1)

B. @CsvFileSource(resources = "/data.csv", skipHeader = true)

C. @CsvFileSource(resources = "/data.csv", ignoreFirstLine = true)

D. @CsvFileSource(resources = "/data.csv", numLinesToSkip = 1)

Solution

1. Step 1: Recall the correct attribute for skipping lines

   The correct attribute to skip lines in @CsvFileSource is numLinesToSkip.

2. Step 2: Match options with correct attribute

   Only @CsvFileSource(resources = "/data.csv", numLinesToSkip = 1) uses numLinesToSkip = 1 which skips the first line (header).

3. Final Answer:

   @CsvFileSource(resources = "/data.csv", numLinesToSkip = 1) -> Option D

4. Quick Check:

   Skip header line = numLinesToSkip = 1 [OK]

Hint: Use numLinesToSkip to skip headers, not skipHeader or ignoreFirstLine [OK]

Common Mistakes:

• Using non-existent attributes like skipHeader or ignoreFirstLine
• Confusing skipLines with numLinesToSkip
• Forgetting to skip header causing test failures

3. Given the CSV file data.csv with content:

name,age
Alice,30
Bob,25

and the test method:

@ParameterizedTest
@CsvFileSource(resources = "/data.csv", numLinesToSkip = 1)
void testUser(String name, int age) {
    System.out.println(name + "-" + age);
}

What will be the printed output when the test runs?

medium

A. name-age
Alice-30
Bob-25

B. Alice-30
Bob-25

C. Alice-30

D. Test fails due to header line

Solution

1. Step 1: Understand numLinesToSkip effect

   numLinesToSkip=1 skips the header line "name,age" so only data lines remain.

2. Step 2: Identify printed lines

   Test runs twice, printing "Alice-30" and "Bob-25" each on separate lines.

3. Final Answer:

   Alice-30 Bob-25 -> Option B

4. Quick Check:

   Header skipped, prints data lines only = D [OK]

Hint: Skip header to avoid printing it as data [OK]

Common Mistakes:

• Not skipping header causing it to print as data
• Expecting header line to print
• Confusing output format with CSV file content

4. Consider this test snippet:

@ParameterizedTest
@CsvFileSource(resources = "/users.csv")
void testUser(String name, int age) {
    assertTrue(age > 0);
}

The CSV file users.csv has a header line. What is the likely problem when running this test?

medium

A. Test will fail because header line is treated as data causing NumberFormatException

B. Test will pass because header is ignored automatically

C. Test will fail due to missing @Test annotation

D. Test will skip all lines and run zero times

Solution

1. Step 1: Check if header is skipped

   No numLinesToSkip is set, so header line is treated as data.

2. Step 2: Understand impact on parsing

   Trying to convert header "age" to int causes NumberFormatException, failing the test.

3. Final Answer:

   Test will fail because header line is treated as data causing NumberFormatException -> Option A

4. Quick Check:

   Header not skipped causes parse error = A [OK]

Hint: Always skip header lines to avoid parsing errors [OK]

Common Mistakes:

• Assuming header is skipped automatically
• Forgetting to add numLinesToSkip=1
• Confusing @ParameterizedTest with @Test

5. You want to test a method that calculates discounts using data from a CSV file with columns: product,price,discountRate. The CSV has a header line. Which is the best way to write the parameterized test method signature and annotation to correctly read and use this data?

hard

A. @ParameterizedTest
@CsvFileSource(resources = "/discounts.csv", numLinesToSkip = 1)
void testDiscount(String product, String price, String discountRate) { ... }

B. @ParameterizedTest
@CsvFileSource(resources = "/discounts.csv")
void testDiscount(String product, int price, int discountRate) { ... }

C. @ParameterizedTest
@CsvFileSource(resources = "/discounts.csv", numLinesToSkip = 1)
void testDiscount(String product, double price, double discountRate) { ... }

D. @ParameterizedTest
@CsvFileSource(resources = "/discounts.csv", skipHeader = true)
void testDiscount(String product, double price, double discountRate) { ... }

Solution

1. Step 1: Identify header skipping attribute

   Use numLinesToSkip = 1 to skip the CSV header line.

2. Step 2: Match method parameters to CSV columns and types

   Product is String, price and discountRate are decimal numbers, so use double for price and discountRate.

3. Step 3: Check options for correctness

   @ParameterizedTest @CsvFileSource(resources = "/discounts.csv", numLinesToSkip = 1) void testDiscount(String product, double price, double discountRate) { ... } correctly uses numLinesToSkip=1 and matching parameter types. @ParameterizedTest @CsvFileSource(resources = "/discounts.csv") void testDiscount(String product, int price, int discountRate) { ... } misses skipping header and uses int instead of double. @ParameterizedTest @CsvFileSource(resources = "/discounts.csv", numLinesToSkip = 1) void testDiscount(String product, String price, String discountRate) { ... } uses String for numeric fields. @ParameterizedTest @CsvFileSource(resources = "/discounts.csv", skipHeader = true) void testDiscount(String product, double price, double discountRate) { ... } uses invalid attribute skipHeader.

4. Final Answer:

   @ParameterizedTest @CsvFileSource(resources = "/discounts.csv", numLinesToSkip = 1) void testDiscount(String product, double price, double discountRate) { ... } -> Option C

5. Quick Check:

   Skip header with numLinesToSkip=1 and match types = C [OK]

Hint: Use numLinesToSkip=1 and match parameter types to CSV columns [OK]

Common Mistakes:

• Using skipHeader instead of numLinesToSkip
• Not skipping header causing parse errors
• Mismatching parameter types with CSV data