Streamline Logging Across TestNG

[krmahadevan]

TestNG Version

Note: only the latest version is supported

7.4.0

Currently TestNG uses a mixture of sysouts and a custom logger that only logs to the console. We should enhance TestNG to use slf4j api integration so that our downstream consumers can basically work with their logging configurations and also help them streamline the test logs.

@juherr WDYT ?

[juherr]

Sure, I think slf4j is light enough to be added as a dependency.

From the architecture pov, I think we should keep the current logger facade and call slf4j from there.

[krmahadevan]

@juherr - Cool. I will work on raising a PR that addresses this ask shortly

[juherr]

TBD: how should be the verbose level managed?
From #2654 (comment)

[krmahadevan]

@juherr - I think we should think of deprecating the verbose attribute and just have it managed via the loggers verbosity. The other option would be to try and map a few of the initial values to the loggers verbosity (1 - error, 2 - warning) but I think that's going to be counter intuitive but will help us retain backward compatibility.

[juherr]

I don't know if we can remove the verbose level because it could be used by default listeners.
For sure, it should be possible to override the value of every listener.

But I agree that the internal logger should not be impacted by this value (but it could be by the runner configuration).

The level map will be necessary for the support of Reporter.log().