Bug 525650 - [JUnit 5] Display of TestReporter entries
Summary: [JUnit 5] Display of TestReporter entries
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.7.1   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2017-10-05 16:41 EDT by Florian Geyer CLA
Modified: 2022-07-10 03:28 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Florian Geyer CLA 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 CLA 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 CLA 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 CLA 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.