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 30424 - Tests sometimes fails with message "Scrolling"
Summary: Tests sometimes fails with message "Scrolling"
Status: CLOSED WORKSFORME
Alias: None
Product: qa
Classification: Unclassified
Component: Jellytools (show other bugs)
Version: 3.x
Hardware: PC Linux
: P3 blocker (vote)
Assignee: issues@qa
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-01-28 13:46 UTC by Jan Becicka
Modified: 2003-07-02 12:06 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Stack trace (5.70 KB, text/plain)
2003-01-28 13:49 UTC, Jan Becicka
Details
Stack trace (5.14 KB, text/plain)
2003-02-04 10:38 UTC, Jan Becicka
Details
Stack trace (5.95 KB, text/plain)
2003-02-18 11:55 UTC, Jan Becicka
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jan Becicka 2003-01-28 13:46:13 UTC
200301270100, qa-fiji
org.netbeans.test.java.gui.customizers.FieldCustomizer.testCustomizeField()

Test is in CVS, module java/test
Comment 1 Jan Becicka 2003-01-28 13:47:47 UTC
Test works fine on Windows
Comment 2 Jan Becicka 2003-01-28 13:49:48 UTC
Created attachment 8696 [details]
Stack trace
Comment 3 Jiri Skrivanek 2003-01-29 13:04:45 UTC
I cannot reproduce it on any other environment than on fiji. Please,
try to add some waiting before combo selection:

line 63: new EventTool().waitNoEvent(1000);
Comment 4 Jan Becicka 2003-01-29 13:58:25 UTC
I cannot find in documentation, where should I insert those
waitNoEvents. This was just an example of "randomly failed" test. How
should we avoid those fails? We cannot insert waitNoEvents everywhere.

I think these issue should be solved on lower level than the test level.

Comment 5 Jan Becicka 2003-02-04 10:37:23 UTC
Hmm, sometimes I have the same problem, even if I wait for 3s.

JavaNode node = new JavaNode(optTree, ...);
new EventTool().waitNoEvent(3000);
node.delete();

see
org.netbeans.test.java.compilation.CompilerSettings.deleteTestCompiler(CompilerSettings.java:110)

this test is in CVS module java/test/qa-functional/src
Comment 6 Jan Becicka 2003-02-04 10:38:34 UTC
Created attachment 8790 [details]
Stack trace
Comment 7 Jiri Skrivanek 2003-02-05 11:14:46 UTC
It is probably some timing issue. We need to investigate it more.
In the meantime I would recommend to change mentioned test case the
following way:

        OptionsOperator optionsOperator = OptionsOperator.invoke();
        optionsOperator.selectOption(BUILDING + "|" + COMPILER_TYPES +
"|" + TEST_COMPILER);
        JTreeOperator optTree= optionsOperator.treeTable().tree();

        JavaNode node = new JavaNode(optTree, BUILDING + "|" +
COMPILER_TYPES + "|" + TEST_COMPILER);
        node.delete();

It is because tree in Options frame is not a regular JTree but
TreeTable and that is why must be handled a different way that an
ordinary tree.
Comment 8 Jiri Skrivanek 2003-02-06 18:27:39 UTC
Fixed thanks to Shura in version 2.0.48.
TreeTableOperator.scrollToPath() method was overriden.
Comment 9 Jan Becicka 2003-02-18 11:53:02 UTC
I'm sorry, but I still have problems with "scrolling". I do
RepositoryTabOperator.invoke();
JavaNode javaNode = new JavaNode(node);
javaNode.select();
new EventTool().waitNoEvent(1000);
javaNode.performMenuAction("Tools|" +
Bundle.getString("org.netbeans.modules.java.imptool.Bundle",
"LAB_ImpToolAction"));

Comment 10 Jan Becicka 2003-02-18 11:55:04 UTC
Created attachment 8997 [details]
Stack trace
Comment 11 Jiri Skrivanek 2003-02-20 08:51:23 UTC
Failure no more happens in a test case from which attached stack trace is.
Comment 12 Quality Engineering 2003-07-02 12:06:48 UTC
Resolved for 3.4.x or earlier, no new info since then -> closing.