When doing changes like this #204 we would basically decrease overall line coverage because such lines would be out of pitest visibility and eventually causing drop of line coverage % while still the coverage would be same.
This raise question whether we should expand pitest target classes not just only Strimzi* and KafkaContainer to avoid kinds of problem in the future.
This would also mean writing a few unit tests, and it's also related to other classes not just Utils (i.e., KafkaVersionService, KafkaNodeRole, Keytool and CertAssembly).
And if we decide this make sense I would create sub-issues to create tests and match mutation coverage for other classes (i.e., KafkaVersionService, KafkaNodeRole, Keytool and CertAssembly)
When doing changes like this #204 we would basically decrease overall line coverage because such lines would be out of pitest visibility and eventually causing drop of line coverage % while still the coverage would be same.
This raise question whether we should expand pitest target classes not just only Strimzi* and KafkaContainer to avoid kinds of problem in the future.
This would also mean writing a few unit tests, and it's also related to other classes not just Utils (i.e., KafkaVersionService, KafkaNodeRole, Keytool and CertAssembly).
And if we decide this make sense I would create sub-issues to create tests and match mutation coverage for other classes (i.e., KafkaVersionService, KafkaNodeRole, Keytool and CertAssembly)