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.
Sometimes can't delete a single test result because the item is disabled. Try the following: Set-up: Create a test and run it once so you have at least one result. Under the TestCase node: 1. right-click on Input 2. right-click on the test result or Under the TestCase node: 1. right-click on Input 2. right-click in any empty space near Input 3. right-click on the test result Workaround: 1. right-click on the TestCase node 2. right-click on the test result
I think I have found a way to always reproduce this problem: Under the same test case node, 1. left click the input node (a non-deletable node) 2. right click the output node (another non-deletable node) 3. right click a result node (a deletable node) => Delete action seems always disabled in this situation. I guess this is a problem in the IDE, but I need to write some code to verify this. For now, a simple workaround is to left click to select the result node first, then do right click to bring up the pop-up menu. Do you think this is a P4?
I think this is a NB platform issue. (I am using a NB build from source code on 7/18) To reproduce the problem: 1. get the full version of NB that includes NB SOA Pack. 2. open the attached projects 3. In the project tab, expand SynchronousSample5Application->Test->TestCase0 4. right click the Output node 5. right click a test result node (say, "July 19, 2007 7:03:07 - Failed"). => the delete action in the context menu is enabled. 6. right click the Output node again 7. right click the same test result node again => the delete action in the context menu is disabled. A little debugging [1] shows that after right-clicking the test case result node in step 7, the context menu is already shown *before* the canDestroy() method in the test case result node is checked. This is not the case for step 5, where the canDestroy() method in the test case result node is correctly checked before the context menu is shown. [1] Set a breakpoint in the canDestory() method of org.netbeans.modules.compapp.test.ui.TestCaseResultNode (enterprise/compapp)
Created attachment 45460 [details] projects
Reassigning to platform for evaluation. Umm... Why there is only a www subcomponent for platform? OK, reassigning to openide. Feel free to reassign to the correct component/subcomponent.
NB stops at TestCaseResultNode.canDestroy() 9 times after step 5 but only twice after step 7. A few stacktraces will be attached.
Created attachment 45462 [details] The first of the two stops after step 7
Created attachment 45463 [details] The second of the two stops after step 7
Created attachment 45464 [details] The first of the 9 stops after step 5
Created attachment 45465 [details] The second of the 9 stops after step 5
Created attachment 45466 [details] The nineth of the 9 stops after step 5
Reassigned back to "openide/nodes". The TestCaseResultNode class visible in the screenshots of the debugger is the following one: http://deadlock.netbeans.org/fisheye/browse/netbeans/enterprise/compapp/projectjbi/src/org/netbeans/modules/compapp/test/ui/TestCaseResultNode.java i.e. it has nothing common with the JUnit module from the basic installation of NetBeans. Reassigned back to "openide/nodes" for further evaluation or a better re-assignment.
Reassigning to new module owner Tomas Holy.
Belongs SOA, where is its category?