Bug 525650

Summary:	[JUnit 5] Display of TestReporter entries
Product:	[Eclipse Project] JDT	Reporter:	Florian Geyer <blueice_eclipse>
Component:	UI	Assignee:	JDT-UI-Inbox <jdt-ui-inbox>
Status:	NEW ---	QA Contact:
Severity:	normal
Priority:	P3	CC:	blueice_eclipse, noopur_gupta
Version:	4.7.1
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:	stalebug

Description Florian Geyer

2017-10-05 16:41:01 EDT

In JUnit 5 users can publish entries via a TestReporter during the test run. According to the user guide (http://junit.org/junit5/docs/5.0.1/user-guide/#writing-tests-dependency-injection):

> In JUnit Jupiter you should use TestReporter where you used to print information to stdout or stderr in JUnit 4.

Currently it is not possible to view these entries afterwards. Would be nice if this could be added.

Comment 1 Noopur Gupta

2017-10-06 05:23:06 EDT

Thanks for reporting this.

With the fix for bug 525662, the test identifier's display name and its published entries will be printed to the Console view.

I will keep this bug for discussing better UI options to display the TestReporter entries.

Suggestions are welcome!

Comment 2 Eclipse Genie

2020-06-26 15:27:22 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.

Comment 3 Eclipse Genie

2022-07-10 03:28:05 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.