[GRADLE-1009] Allow configuration option for seeing test output on the console. Created: 25/Jun/10 Updated: 04/Jan/13 Resolved: 07/Nov/11
|Comment by Hans Dockter [ 25/Jun/10 ]
One important use case is if you have dead locked tests, thus not xml result file is created.
|Comment by Peter Niederwieser [ 21/Feb/11 ]
I consider this very important - not just in the case of deadlocked tests, but in general. For example, if your integration tests take 10 minutes, you'll currently have to wait that long until you know what went wrong, even if the very first test failed. Aborting the build with CTRL+C doesn't work either because the test report is only written at the end.
Same problem exists for CheckStyle and Codenarc tasks, and probably also for others.
|Comment by Tomek Kaczanowski [ 02/Aug/11 ]
Any progress on this one? This is the most voted issue, please hear what people have to say.
|Comment by Neil Chaudhuri [ 19/Sep/11 ]
This is easily my most needed feature and the one that keeps me from moving completely to Gradle. This shouldn't be too hard either, so I am hoping to see it soon.
In the meantime, what is the "official" workaround?
|Comment by Tom Canova [ 24/Oct/11 ]
I've spent a couple weeks seeing if I can convert to gradle. In gradle the build never completes the tests - it just hangs(the builds including all of the tests, work fine in maven). Without real time logging, I have no way of getting information about where it is hanging when the tests run in gradle. Please fix this, as it looks like it could be a showstopper that prevents us from moving to gradle.
|Comment by Szczepan Faber [ 07/Nov/11 ]
|Comment by Tomek Kaczanowski [ 23/Jan/12 ]
I can't make it work, and because I can not reopen this issue, I created another one: http://issues.gradle.org/browse/GRADLE-2058