(not related with this patch) This kind of parameter passing in ktest gets only worse with time.. ktest becomes more complex and we need to add more parameters(I know I'm responsible for this). I think widely-used solution to this problem is to use some kind of builder class with methods for settings object properties but that leads to more verbosity and more code to maintain... Or maybe we can share some settings using some kind of immutable ktest setting object. What do you guys think about that?