Refactoring on rename/move class in sources should
offer rename/move of appropriate JUnit test class.
*** Issue 62724 has been marked as a duplicate of this issue. ***
*** Issue 62897 has been marked as a duplicate of this issue. ***
Issue #62897 was actually slightly different: dealing with renames of methods, not classes. Of course having both would
Oops, sorry, my bad. I see it now.
Should I, well, "unduplicate" it? :) Or can we take this as global 'refactoring-of-JUnit-tests' thing?
I think it's fine to take this to include refactoring of both the tested class and methods in it. Very related.
Rename/Move method should refactor appropriate Test method.
See 62897 closed a duplicate.
*** Bug 203788 has been marked as a duplicate of this bug. ***
The refactoring works when a class is renamed. Implemented in http://hg.netbeans.org/main-golden/rev/0a625e9c83a5. So closing this one and I will reopen bug 62897 which is about methods refactoring. Thank you