# Seeing test output at the console

**URL:** <https://discuss.gradle.org/t/seeing-test-output-at-the-console/7610>\
**Category:** Old Forum Archive\
**Created:** [November 7, 2011, 12:54pm UTC](https://discuss.gradle.org/t/seeing-test-output-at-the-console/7610 "2011-11-07T12:54:00Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Szczepan\_Faber](https://sea1.discourse-cdn.com/gradle/user_avatar/discuss.gradle.org/szczepan_faber/32/213_2.png) [@Szczepan\_Faber](https://discuss.gradle.org/u/Szczepan_Faber)\
**Post date:** [November 7, 2011, 12:54pm UTC](https://discuss.gradle.org/t/seeing-test-output-at-the-console/7610/1 "2011-11-07T12:54:00Z")

</div>

The fix for GRADLE-1009 has landed in the master branch. That is, you can now configure the test task to show the tests’ standard streams (out & err) directly on the console.

Obviously, most of you don’t need that, because your tests fail with meaningful assertion messages and you are never interested in system out. Not to mention that most of you don’t use system out but a proper logging tools 🙂 Regardless, the feature might come handy if the gradle process is killed before test reports have been generated (the reports have always included the standard streams output).

Enjoy, some docs/examples you can find [here](http://gradle.org/releases/latest/docs/dsl/org.gradle.api.tasks.testing.Test.html#org.gradle.api.tasks.testing.Test:testLogging) and [here](http://gradle.org/releases/latest/docs/dsl/org.gradle.api.tasks.testing.Test.html#org.gradle.api.tasks.testing.Test:onOutput(groovy.lang.Closure)%5D)

After the M6 release, the docs will be available at our usual location of the dsl reference for the Test task: [http://gradle.org/current/docs/dsl/org.gradle.api.tasks.testing.Test.html](http://gradle.org/current/docs/dsl/org.gradle.api.tasks.testing.Test.html)
