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.

Bug 49986 - [tests] Redundant thrown problem from move class tests
Summary: [tests] Redundant thrown problem from move class tests
Status: CLOSED INVALID
Alias: None
Product: editor
Classification: Unclassified
Component: Refactoring (show other bugs)
Version: 4.x
Hardware: PC Linux
: P3 blocker (vote)
Assignee: Jan Becicka
URL:
Keywords: RANDOM, T9Y
Depends on:
Blocks:
 
Reported: 2004-10-06 09:36 UTC by ehucka
Modified: 2007-04-03 18:02 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description ehucka 2004-10-06 09:36:30 UTC 
From the test refactoring/qa-functional/Move
class/testClass7 is sometimes thrown a problem
about  accessing a protected field which should
not be thrown there.

The moved class is a subclass of class which
declares the field.

Problem: Class
"org.netbeans.tests.examples.packb.BeanDD"
accesses protected field "refID" declared in class
"org.netbeans.tests.examples.packb.Bean".

Class Bean was previously moved into the package
packb, class BeanDD is 'secondary' top-level class
of moved BeansD class.
Comment 1 Jan Becicka 2004-10-22 15:26:28 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.
Comment 2 ehucka 2004-10-25 09:45:22 UTC 
There is six tests which are changing the project before the
testClass7. I'll try to find some better steps to reproduce it.
Comment 3 ehucka 2004-10-26 13:35:52 UTC 
See: refactoring/qa-functional|Undo/move class
testUndoMoveClass3 and testUndoMoveClass4. They are failing with the
same reason.
Comment 4 Jan Becicka 2004-10-26 13:45:39 UTC 
Well, is this bug reproducible without automatic tests (manually?)
Comment 5 ehucka 2004-10-26 14:16:16 UTC 
I don't know, it is RANDOM. I have not reproduced it yet.
Comment 6 Jan Becicka 2005-01-14 14:06:11 UTC 
Is this bug still valid?
Comment 7 Jan Becicka 2005-01-17 14:00:11 UTC 
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.
Comment 8 Jan Becicka 2005-01-21 13:44:41 UTC 
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
Comment 9 ehucka 2005-01-31 12:19:02 UTC 
It is back in tests' results.
Comment 10 Jan Becicka 2005-01-31 13:33:51 UTC 
I can fix it, If you provide steps to reproduce without xtest.
Comment 11 Jan Becicka 2005-03-17 13:55:29 UTC 
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.
Comment 12 Milan Kubec 2005-11-15 13:56:48 UTC 
Emane, is this issue still valid?
Comment 13 ehucka 2005-11-15 14:48:42 UTC 
I do not know history of test results, probably it is not valid now.
Comment 14 Milan Kubec 2005-12-20 10:42:15 UTC 
Closing as reporter suggested.
Comment 15 ehucka 2006-03-22 09:48:36 UTC 
verified