[GRADLE-652] Support GWT JUnit tests that write user prompts to the console Created: 25/Sep/09  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: None
Fix Version/s: None

Type: Improvement
Reporter: Andrew Pietsch Assignee: Unassigned
Resolution: Won't Fix Votes: 1


GWT test cases can be run in various modes one of which requires user action. In the case of "maunual" tests GWT test infrastructure will print a message to console which needs to be cut and pasted into a browser.

Gradle needs to be able to display this message to the user.

Information on GWT testing can be found at: http://code.google.com/docreader/#p=google-web-toolkit-doc-1-5&s=google-web-toolkit-doc-1-5&t=DevGuideJUnitCreation

Comment by Andrew Pietsch [ 24/Jun/10 ]

The GWT 2.0 documentation for manual mode can be found at: http://code.google.com/webtoolkit/doc/latest/DevGuideTesting.html#Manual_Mode

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:35:24 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.