migrate-junit-source-to-tabletest

Remove @ParameterizedTest and @CsvSource, then map each row into a @TableTest String[] array using '|' as the delimiter. Add a header row with parameter names and a scenario column, aligning columns so pipes line up vertically.

Convert @MethodSource to @TableTest when argument values are primitives, strings, enums, booleans, nulls, or simple collection literals. Complex cases can stay in @MethodSource combined with @TableTest on the same @ParameterizedTest, with the provider method named <testMethodName>Arguments returning Stream<Arguments>.

Yes, @TableTest works on JDK 8 by using the String[] annotation array syntax instead of text blocks. Each table row is a separate string element in the annotation array, with '|' delimiters and aligned columns.

Do not convert when most rows require complex builders or mocks that cannot be represented as strings. Single-parameter @ValueSource tests should also stay as-is, and @NullSource should be kept when null cases are needed.

Use @TypeConverter for symbolic constants referenced by migrated table rows, such as Long.MAX_VALUE or DDSpanId.MAX. Prefer explicit one-case-one-return mappings and shared converter utilities when reuse across modules is likely.

Run the module test command and check the JUnit XML report at the module's build/test-results/test/TEST-*.xml path if the build fails. Common causes include unquoted strings starting with '[' or '{', missing scenario columns, or leftover unused imports.