-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
print custom log message during an automated test #205
Comments
The showStandardStreams should do the trick. If that's not working for you, I'd start comparing with what you get with Gradle without this plug-in applied. |
Thank you, your guidance of checking gradle instead of the plugin helped me get closer. I was using
but actually needed to be using
Related question -- in version 3.0.0 is says "Implemented enhancements: Display start of the test #165"...was that feature added / how to use it? |
@jaymiller455 Unfortunately no. I should probably tweak the changelog generator I use to not mark issues that were closed without resolution as "Implemented enhancements". Anyway, see related comment: |
Thank you for your awesome plugin, but I am stuck and new at this. How can I see custom log messages I print during an automated test? Sometimes we need to know specific variable values at different moments of an automated test. I enabled as many settings in gradle-test-logger-plugin as I knew how (version 3.0.0). I even tried adding a log4j2.yaml file to the project as a last ditch effort for org.apache.logging.log4j.LogManager and org.apache.logging.log4j.Logger.
Currently, in our Kotlin/Java project within Intellij IDE, I can see log output in the console using something like:
But when I view the logs on Bamboo, those "logger.info" strings are never printed, only your PASS / FAIL lines. I'm okay with it printed after a test passes or fails, since your plugin formats/prints output after gradle finishes a test. Do you have any suggestions? Thank you in advance. The testlogger settings I am using are:
Gradle Version: 6.8.3
The text was updated successfully, but these errors were encountered: