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 58825 - TestAction should not be tools action
Summary: TestAction should not be tools action
Status: RESOLVED INVALID
Alias: None
Product: java
Classification: Unclassified
Component: JUnit (show other bugs)
Version: 5.x
Hardware: All All
: P3 blocker (vote)
Assignee: junit-issues@java
URL:
Keywords: PERFORMANCE
Depends on:
Blocks: 40260
  Show dependency tree
 
Reported: 2005-05-12 13:52 UTC by _ rkubacki
Modified: 2009-04-24 12:06 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description _ rkubacki 2005-05-12 13:52:33 UTC 
According to new UI spec for JUnit we should not define TestAction as a tools
action (http://ui.netbeans.org/docs/ui/junits/promo_f.html). It means we can
have simpler manifest parsing and one step towards eliminating of JInlineMenu in
Tools menu. Also it can aviod too deep nesting of this submenu in a context menu
of JavaDataObject.
Comment 1 _ rkubacki 2005-05-12 13:56:15 UTC 
related to issue #35827 and affects
Comment 2 Marian Petras 2005-05-13 12:49:26 UTC 
Accepted.
Comment 3 cms 2008-12-03 08:43:55 UTC 
Pretty old issue. Is it still intended to place corresponding menu in the Project Window between the Refactor and Tools 
sub-menus like mentioned in "JUnit Tests (release F)" document? Please confirm this or otherwise add the refreshed 
proposal on JUnit related context menu placements.
Comment 4 Alexei Mokeev 2009-04-16 06:22:02 UTC 
Should be re-evaluated with the proper UI spec.
Comment 5 Alexei Mokeev 2009-04-24 12:06:19 UTC 
It looks like JInlineMenu is not a problem for JUnit anymore. This bug is obsolete.