A Gradle plugin for printing beautiful logs on the console while running tests
Branch: develop
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.
.circleci Configure testlogger for each task Oct 28, 2018
docs Refresh screenshots Sep 8, 2018
gradle Configure testlogger for each task Oct 28, 2018
src Fix double escaping of brackets Feb 7, 2019
CHANGELOG.md Release v1.6.0 Nov 20, 2018
README.md Release v1.6.0 Nov 20, 2018
appveyor.yml Configure testlogger for each task Oct 28, 2018
build.gradle Add @CompileStatic to all classes Oct 30, 2018
gradle.properties Release v1.6.0 Nov 20, 2018
gradlew Change permissions for gradlew Jul 28, 2017
gradlew.bat Create plugin template Jul 26, 2017
settings.gradle Resolve Gradle deprecation warnings Aug 27, 2018
uploadTestResults.ps1 Add Configuration for AppVeyor Oct 2, 2017


Gradle Test Logger Plugin

CircleCI branch AppVeyor branch Coveralls branch Gradle plugin portal License

A Gradle plugin for printing beautiful logs on the console while running tests.


Standard theme

Standard theme

Mocha theme

Mocha theme

Scroll down for more themes and customisation options or visit the screenshots page for more demos.


Modern Gradle

plugins {
    id 'com.adarshr.test-logger' version '1.6.0'

Gradle < 2.1

buildscript {
    repositories {
        maven {
            url 'https://plugins.gradle.org/m2/'
    dependencies {
        classpath 'com.adarshr:gradle-test-logger-plugin:1.6.0'

apply plugin: 'com.adarshr.test-logger'


The plugin registers an extension called testlogger (all lowercase and one word) at project level as well as for each task of type Test.

The following shows the complete default configuration applied when you configure nothing.

testlogger {
    theme 'standard'
    showExceptions true
    slowThreshold 2000
    showSummary true
    showPassed true
    showSkipped true
    showFailed true
    showStandardStreams false
    showPassedStandardStreams true
    showSkippedStandardStreams true
    showFailedStandardStreams true

Project vs task level configuration

Settings configured at the project level can be overridden by redefining them at task level. Settings not defined at task level will inherit project level values. Consider the below configuration.

testlogger {
    theme 'mocha' // project level
    slowThreshold 5000

test {
    testlogger {
        theme 'standard-parallel' // task level

In the above example, the effective theme will be standard-parallel and slowThreshold will be 5000 whereas rest of the settings will retain their default values.

Overriding settings at runtime

All the above settings can either be specified in build.gradle or be set at runtime using system properties or both. For instance, we could have theme set to mocha in the build file but it can be overridden to be standard at runtime by using -Dtestlogger.theme=standard on the command line. Since they are system properties we have a number of ways of specifying them including JAVA_OPTS and gradle.properties.

  • The convention used for determining the name of the system property is testlogger.<configuration setting>.
  • System property overrides will be applied after combining task and project level settings.
  • Specifying a system property override will apply the same setting for all tasks, regardless of any configuration defined in the build file.

Switch themes

testlogger {
    theme 'mocha'

The following themes are currently supported:

  1. plain - displays no colours or Unicode symbols
  2. standard - displays colours but no Unicode symbols
  3. mocha - similar to what Mocha's spec reporter prints, with colours and Unicode symbols
  4. plain-parallel - similar to the plain theme but supports parallel test execution
  5. standard-parallel - similar to the standard theme but supports parallel test execution
  6. mocha-parallel - similar to the mocha theme but supports parallel test execution

Hide exceptions

By default, the showExceptions flag is turned on. This shows why the tests failed including the location of the failure. Of course, you can switch off this slightly more verbose logging by setting showExceptions to false.

testlogger {
    showExceptions false

Define slow threshold

Tests that are too slow will have their duration logged. However, "slow" is a relative terminology varying widely depending on the type of tests being executed, environment, kind of project and various other factors. Therefore you can define what you consider as slow to suit your needs.

testlogger {
    slowThreshold 5000

The default value of slowThreshold is 2 seconds. So all tests that take longer than a second to run will have their actual execution time logged.

If you want to turn off the logging of time taken completely, simply set the threshold to a very large value.

Please note that in themes that support colours, the duration is displayed using a warning style if it is greater than half the slow threshold. For instance, if slowThreshold is 5 seconds any tests that take longer than 2.5 seconds to run would have their durations logged using a warning style and those that take longer than 5 seconds to run using an error style.

Hide summary

By default, a useful summary containing a breakdown of passing, failing and skipped tests along with the total time taken to execute all the tests is shown. Of course, you can disable this if you prefer a more succinct output.

testlogger {
    showSummary false

Show standard streams

The display of standard output and error streams alongside the test logs can be controlled using the below configuration.

testlogger {
    showStandardStreams true

Filter standard streams

If the display standard output and error streams is enabled, it can often produce too much output to overwhelm anyone. Fortunately, we can filter this output based on the type of the test result.

testlogger {
    showStandardStreams true
    showPassedStandardStreams false
    showSkippedStandardStreams false
    showFailedStandardStreams true

All the three filter flags are enabled by default. In other words, the standard stream output is not filtered if showStandardStreams is enabled but none of the filter flags are configured.

If showStandardStreams is set to false, the filter flags don't have any effect.

Filter test results

Sometimes it is useful to hide test results of a certain type. For instance, if an application has hundreds of tests, the sheer volume of the output produced by passing tests could be enough to bury any valuable test failures. Similarly there might be a need to hide skipped tests or in rare instances even the failed ones.

We can perform test result filtering by using the below settings.

testlogger {
    showPassed false
    showSkipped false
    showFailed true

By default all the above three flags are turned on. If you have chosen to display standard streams by setting showStandardStreams flag to true, any output produced by filtered out tests will not be displayed.


Does it work on Windows?

Mostly. The standard and plain themes work out of the box but you might have to make a few modifications to your system settings to see Unicode symbols when using the mocha theme.

  1. Set or update JAVA_OPTS with the system property -Dfile.encoding=UTF-8
  2. Change the terminal code page to 65001 by executing chcp 65001

How to disable colours and Unicode symbols at runtime such as on Jenkins consoles?

You can switch off ANSI control characters and Unicode symbols by adding --console=plain to your Gradle command line.

Does it support parallel test execution?

Yes. You will need to switch to a suitable parallel theme though. This can be one of plain-parallel, standard-parallel or mocha-parallel. The parallel themes are specially designed to work with a setting of maxParallelForks greater than 1. They achieve this by sacrificing the ability to group tests and thus some readability is lost.

How are testlogger and Test.testLogging related?

Until recently, they were unrelated. While this plugin's testlogger has many properties named identical to the ones in Gradle's Test.testLogging, to a large extent, they are kept isolated by design.

However, as of this writing testlogger.showStandardStreams property has been made to react to testLogging.showStandardStreams property as long as one doesn't configure a value for testlogger.showStandardStreams. If a value is configured for testlogger.showStandardStreams (even if it is false), the plugin ignores testLogging.showStandardStreams altogether.

Can this plugin co-exist with junit-platform-gradle-plugin?

Due to certain unknown reasons, junit-platform-gradle-plugin is incompatible with gradle-test-logger-plugin. If you are still using junit-platform-gradle-plugin, it might be worth noting that this plugin was deprecated in JUnit Platform 1.2 and removed from JUnit Platform 1.3.

The test logger plugin however, is fully compatible with the Gradle native way of using JUnit 5.