You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are using TestNG as a framework for executing E2E tests as a service. Everything works great but I have noticed that the code has multiple places where instead of a Logger, System.out and System.err are used to print information to the screen.
For example: org.testng.internal.Version#displayBanner
It would be really cool if every console output came from a Logger like you are using in other places. This way, we can add extra information to the log line via configuration (requestId for example).
Otherwise, it's really hard for us to find important information in our logs. For example, some failure stack traces are printed this way and are imposible to find.
The text was updated successfully, but these errors were encountered:
Hello!
We are using TestNG as a framework for executing E2E tests as a service. Everything works great but I have noticed that the code has multiple places where instead of a Logger, System.out and System.err are used to print information to the screen.
For example:
org.testng.internal.Version#displayBanner
It would be really cool if every console output came from a Logger like you are using in other places. This way, we can add extra information to the log line via configuration (requestId for example).
Otherwise, it's really hard for us to find important information in our logs. For example, some failure stack traces are printed this way and are imposible to find.
The text was updated successfully, but these errors were encountered: