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.
I often need to run a single unit test method until it works correctly. In Eclipse you simply right click on the unit test method and select "Run Method". I would like the same functionality in NetBeans.
Please, use the context menu item "Run Again" against a desired method in the tree of the "Test Results" window.
Created attachment 88699 [details] Screenshot of contextual menu
This menu item you referred to doesn't seem to exist (see attached screenshot).
Hmm... Do you really use NB5.0? If so then try to update it up to latest version. Seems it was implemented in 6.7.1, I can't try it now. But, I see it in 6.8M1 Unfortunately, I can't see the picture. You need assign correct MIME type when a png file is attached, otherwise, by default, it will be interpreted as a plain/text file that we can see now.
Created attachment 88704 [details] JUnit - Run Again action for a FAILED method
I'll close this issue, because it is already implemented. And, I've used it every day at least the last week.
If I remember correctly, the presence/absence of the action depends on whether the action is actually implemented in the corresponding project (type). So the action may be present and work for J2SE projects and NetBeans module projects but may not work for other project types. I do not know which project types have the support (for the action) implemented and which project types do not.
Created attachment 88705 [details] Screenshot of contextual menu
I have attached the screenshot with the correct MIME-type. I also fixed the version number. From the screenshot, it is apparent that it is a development build of NetBeans 6.8 (build number 200908022240).
Your earlier comment about the menu being project dependent makes sense. I tested this on both Groovy and Grails projects and encountered the same problem. I'm shifting the component for this issue to "groovy".
*** This bug has been marked as a duplicate of bug 212829 ***