Resolver-supplied parameters follow the table-bound parameters

All 2 scenarios hold

A JUnit parameter resolver supplies parameters such as TestInfo, TestReporter, and @TempDir. Those parameters can follow the table-bound parameters.

Where a resolver parameter is present, a scenario column needs @Scenario. Without it TableTest does not recognise the column.

The rule is the parameter order. The byte count is how a row proves it.

Each invocation writes its File content to a temporary directory that JUnit supplies, and then measures the file. A count that matches the content is possible only where the table's value reached the parameter the table names. It cannot come from one of the three parameters the resolvers fill after it.

JUnit resolves TestInfo, TestReporter and the temporary directory alongside, and the body asserts that each one arrived.

Two rows, and not one. An empty file writes no bytes, and that is also the count of a parameter that never received the cell.