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.
Noted by sgtgarcia in issue #72080, but I had noticed this myself recently. The option is exposed but it does not nothing when invoked.
the latest code (after rewrite of maven junit integration to use the test runner apis) doesn't expose rerun single test anywhere. The rerun button button in the component toolbar is enabled and will either rerun all tests, or the tests in the given file only, depending how the window was populated. changing to enhancement, it's a missing feature,not a bug. I don't currently know how to implement run single method using maven alone. Unfortunately the ant based build script approach cannot be taken and the "compile on save" runner doesn't support it either.
CoS runner does support rerun single method, or at least it did last I checked; autoproject.java uses it.
Maven already gives you class path and NetBeans "compile on save". I am wondering what's missing and how it works in other IDEs (Eclipse)?
jglick: I see, the single method invokation constants are not exposed through he api though it seems, That's why I haven't found them. I guess adding that action for cases when CoS is on could be fairly easy. Still, if someone disables CoS (for good reasons oemtimes) it will disable the reruns, but I guess it's ok.
http://hg.netbeans.org/main/rev/be3686c05545
"the single method invocation constants are not exposed through the API" - please file a defect for JavaRunner so this gets fixed.
ok, see 160649
Integrated into 'main-golden', will be available in build *200903210201* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main/rev/be3686c05545 User: Milos Kleint <mkleint@netbeans.org> Log: #160194 add run single method through compile on save