This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 158018 - Ability to provide content for JUnit Test Results window
Summary: Ability to provide content for JUnit Test Results window
Status: NEW
Alias: None
Product: utilities
Classification: Unclassified
Component: Test Runner (show other bugs)
Version: 6.x
Hardware: All All
: P2 blocker with 1 vote (vote)
Assignee: Theofanis Oikonomou
Keywords: API
Depends on: 159570
Blocks: 158019 196890
  Show dependency tree
Reported: 2009-02-05 15:38 UTC by Jesse Glick
Modified: 2016-01-11 19:27 UTC (History)
4 users (show)

See Also:
Exception Reporter:


Note You need to log in before you can comment on or make changes to this bug.
Description Jesse Glick 2009-02-05 15:38:33 UTC
Currently it seems the JTR window is hardcoded to listen to Ant <junit> output.

It would be great for other module code to be able to open and populate this window with something else:

1. Maven test output is currently just shown in a text console.

2. Desirable for test results from a remote Hudson build to be displayed here.

I suppose what would be needed is something like org.netbeans.modules.junit.output.Manager in
org.netbeans.modules.junit.plugin, with s/AntSession/Object/g, and some default access things changed to public. I could
try to work on a proposed patch if you agree.
Comment 1 Andrey Yamkovoy 2009-02-05 15:51:23 UTC
Now I am investigating an ability to use Common Test Runner API module (gsf.testrunner) for all the modules which needs
to run tests and view results. This testrunner now used by php, python and ruby plugins. It would be great if we can
switch all other modules like java and maven to use it.
Comment 2 Jesse Glick 2009-02-05 17:17:56 UTC
Cool, I did not even know about this. When I get a chance I will check if Hudson support is able to use it.

The API is not very clean. Why are things like TestMethodNode public? Probably needs to be trimmed down in various ways.
But a good start.
Comment 3 Jesse Glick 2009-03-04 00:32:07 UTC
The Javadoc is pretty confused, e.g. issue #159570. Also there is no apparent way to hyperlink stack trace lines;
Trouble.setStackTrace just takes String[].
Comment 4 Alexei Mokeev 2009-03-05 13:49:58 UTC
Assigning issues from Michael to Andrey.