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.
Summary: | [tests] Redundant thrown problem from move class tests | ||
---|---|---|---|
Product: | editor | Reporter: | ehucka <ehucka> |
Component: | Refactoring | Assignee: | Jan Becicka <jbecicka> |
Status: | CLOSED INVALID | ||
Severity: | blocker | Keywords: | RANDOM, T9Y |
Priority: | P3 | ||
Version: | 4.x | ||
Hardware: | PC | ||
OS: | Linux | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
ehucka
2004-10-06 09:36:30 UTC
Emane can you provide "manual" step by step instructions, please. I'm looking at the tests, and they move BeansD into "packagec". If I do it, no warning is shown. There is six tests which are changing the project before the testClass7. I'll try to find some better steps to reproduce it. See: refactoring/qa-functional|Undo/move class testUndoMoveClass3 and testUndoMoveClass4. They are failing with the same reason. Well, is this bug reproducible without automatic tests (manually?) I don't know, it is RANDOM. I have not reproduced it yet. Is this bug still valid? I'm not able to reproduce it without xtest. I'm setting target milestone to future. As soon as someone provides "manual" steps to reproduce, I'll look at it again. Checking in src/org/netbeans/modules/refactoring/api/Bundle.properties; /cvs/refactoring/src/org/netbeans/modules/refactoring/api/Bundle.properties,v <-- Bundle.properties new revision: 1.21; previous revision: 1.20 done Processing log script arguments... More commits to come... Checking in src/org/netbeans/modules/refactoring/plugins/MoveClassRefactoringPlugin.java; /cvs/refactoring/src/org/netbeans/modules/refactoring/plugins/MoveClassRefactoringPlugin.java,v <-- MoveClassRefactoringPlugin.java new revision: 1.15; previous revision: 1.14 done It is back in tests' results. I can fix it, If you provide steps to reproduce without xtest. QA-Functional refactoring tests are too complecated for debugging. Marking as INCOMPLETE. As soon as you provide reproducible scenario without xtest framework, please let me know. Emane, is this issue still valid? I do not know history of test results, probably it is not valid now. Closing as reporter suggested. verified |