[GRADLE-1252] output of TestNG listeners is not visible Created: 12/Dec/10  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: 0.9-rc-3
Fix Version/s: None

Type: Bug
Reporter: Tomek Kaczanowski Assignee: Unassigned
Resolution: Won't Fix Votes: 5

Issue Links:
Duplicate
Duplicated by GRADLE-2058 testNG listeners' system out/err is s... Resolved
Related
Related to GRADLE-2524 JAVA PLUGIN - test task - Setting of ... Resolved

 Description   

I have a TestNG listener (like http://testng.org/doc/documentation-main.html#logging-listeners) which prints some output to console (System.out). When I register them:

test {
useTestNG()
options

{ listeners << 'somePackage.MyListener' }

}

the output is not visible at all.

 Comments   
Comment by Joel Pearson [ 04/Jun/12 ]

We're seeing this problem with some of our tests, was there any resolution to this?

Comment by Joel Pearson [ 05/Jun/12 ]

Our problem was related to not logging to the stdout.

We needed: webAcceptanceTest.testLogging.showStandardStreams = true

see: http://forums.gradle.org/gradle/topics/some_of_our_gradle_tests_are_not_outputting_any_logs_with_testng

Comment by Benjamin Muschko [ 15/Nov/16 ]

As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.

We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.

Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:

  • Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
  • Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!

Comment by Benjamin Muschko [ 10/Feb/17 ]

Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved.

Generated at Wed Jun 30 11:50:49 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.