Gradle-built Generic Java Application Test Logging: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 5: | Line 5: | ||
=Overview= | =Overview= | ||
When building with Gradle a generic Java application, stdout and stderr of the tests being executed will be shown at the console if the following are configured: | |||
* Set <tt>testLogging.showStandardStreams</tt> of the Java plugin Test task, as shown here: [[Testing_with_Gradle_Java_Plugin#Show_stdout_and_stderr_of_the_Test_JVM_on_the_Console|Show stdout and stderr of the Test JVM on the Console]]. | |||
* Make sure that a slf4j binding is in the test classpath. Spring uses Logback by default, so the following will work: [[Slf4j#Logback_Binding|Place Logback Binding on test classpath]]. | |||
* Place a [[Logback.xml#Example|logback.xml]] configuration in src/test/resources. At the time of the writing, I was not able to figure out why logging configuration from src/test/resources/application.yml did not work. | |||
Revision as of 05:56, 7 April 2019
Internal
Overview
When building with Gradle a generic Java application, stdout and stderr of the tests being executed will be shown at the console if the following are configured:
- Set testLogging.showStandardStreams of the Java plugin Test task, as shown here: Show stdout and stderr of the Test JVM on the Console.
- Make sure that a slf4j binding is in the test classpath. Spring uses Logback by default, so the following will work: Place Logback Binding on test classpath.
- Place a logback.xml configuration in src/test/resources. At the time of the writing, I was not able to figure out why logging configuration from src/test/resources/application.yml did not work.