> Having a data-driven test can, in some circumstances, allow one > to more easily come up with additional interesting test cases. Let's try to break this request down: 1. You would like first-class support for parameterized tests, as they are commonly called, instead of the ad-hoc thing I did because this is all upstream KUnit has atm. Me too! 2. You would like a way to pass the data to the parameterized test other than hardcoding. Depending on how parameterizing is designed, the input part may or may not belong in KUnit. As an example we have a test which has custom code that does essentially "ls dir" and passes the list of input files as the list of parameters to the test framework and then each individual test has the code to read the file passed as the parameterized test's parameter. This is not the most elegant example but it's the quickest I could come up offhand the point being to demonstrate what can potentially belong in the core test framework what can be external to it.
