Your First TableTest

Create the Class Under Test

First, create a simple calculator class:

public class Calculator {
    public int add(int a, int b) {
        return a + b;
    }
}

Create the Test Class

Create a JUnit test class and import the necessary classes:

import org.tabletest.junit.TableTest;
import static org.junit.jupiter.api.Assertions.assertEquals;

public class CalculatorTest {
    private final Calculator calculator = new Calculator();

    // Tests will go here
}

Write Your First TableTest

Add a test method with the @TableTest annotation:

@TableTest("""
    Scenario              | A  | B  | Sum?
    Two positive numbers  | 2  | 3  | 5
    Positive and negative | 5  | -3 | 2
    Two negative numbers  | -4 | -6 | -10
    Zero and positive     | 0  | 7  | 7
    """)
public void testAddition(int a, int b, int expectedSum) {
    int result = calculator.add(a, b);
    assertEquals(expectedSum, result);
}

Let’s break this down:

The Table Structure

Scenario              | A | B | Sum?
Two positive numbers  | 2 | 3 | 5

• First row: Column headers (pipe-separated)
• First column: Scenario descriptions (not passed as parameter)
• Remaining columns: Test data mapped to method parameters
• Subsequent rows: Test cases (one execution per row)

Method Parameters

public void testAddition(int a, int b, int expectedSum)

The method parameters match the table columns (except the scenario column) based on order. TableTest automatically converts string values to the parameter types.

The Assertion

int result = calculator.add(a, b);
assertEquals(expectedSum, result);

Standard JUnit assertions. The test logic executes once per table row.

Run the Test

Run the test using your IDE or build tool:

mvn test

./gradlew test

You should see four test executions – one for each row in the table. In your IDE’s test runner, they’ll appear as:

✓ CalculatorTest
  ✓ testAddition (int, int, int)
    ✓ [1] Two positive numbers
    ✓ [2] Positive and negative
    ✓ [3] Two negative numbers
    ✓ [4] Zero and positive

The scenario description becomes the display name, making it easy to identify which case passed or failed.