I think it makes sense to keep logger private and separate. I can see one reason - we can change the logger in the framework without affecting the tests. We can also decide to not use the logger to print test suites messages - for example save per test artifacts.
On 15/01/2025 10:17, Luca Vizzarro wrote: > Sorry for the late reply Dean. This is a bit redundant in my opinion, > there is no reason not to give full access to the test suite's own > logger. I'd just change TestSuite._logger into TestSuite.logger to > indicate that it's a public member, and do what you initially did.
