Resolver-supplied parameters follow the table-bound parameters

All 3 scenarios hold

Each invocation takes its file content from the table, writes it to a JUnit-supplied temporary directory, and verifies the size of the written file. TestInfo and TestReporter are resolved alongside.

expected outcome broken scenario
ScenarioFile contentFile size in bytes?
Single wordhello5
Two wordshello world11
Empty file“”0