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.
I would recommend to prolong all WAIT timeouts to 60000. Sometimes it can happen that tested application is busy for a while (e.g. garbage collector or background parser work) and UI is not ready in time. Prolonging timeouts will not slow down a passing test. Only often failing test cases can take a little bigger amount of time but it is better than accidental failure because of small timeout value. At least values 1000 and 5000 should be enlarged to 10000 (maybe more), if there are objections against 60000. ComponentOperator: private final static long WAIT_COMPONENT_TIMEOUT = 10000; private final static long WAIT_COMPONENT_ENABLED_TIMEOUT = 1000; private final static long WAIT_FOCUS_TIMEOUT = 10000; private final static long WAIT_STATE_TIMEOUT = 5000; ContainerOperator: private final static long WAIT_SUBCOMPONENT_TIMEOUT = 10000; EventDispatcher: private final static long WAIT_COMPONENT_UNDER_MOUSE_TIMEOUT = 10000; JColorChooserOperator: private final static long WAIT_LIST_PAINTED_TIMEOUT = 10000; JComboBoxOperator: private final static long WAIT_LIST_TIMEOUT = 1000; JComponentOperator: private final static long WAIT_TOOL_TIP_TIMEOUT = 10000; JFileChooserOperator: private final static long WAIT_LIST_PAINTED_TIMEOUT = 10000; JMenuOperator: private final static long WAIT_POPUP_TIMEOUT = 10000; private final static long PUSH_MENU_TIMEOUT = 10000; JProgressBarOperator: private static long WAIT_VALUE_TIMEOUT = 10000; JTableOperator: private final static long WAIT_EDITING_TIMEOUT = 1000; JTextComponentOperator: private final static long CHANGE_CARET_POSITION_TIMEOUT = 10000; private final static long TYPE_TEXT_TIMEOUT = 30000; JTreeOperator: private final static long WAIT_NODE_EXPANDED_TIMEOUT = 10000; private final static long WAIT_NODE_COLLAPSED_TIMEOUT = 10000; private final static long WAIT_NEXT_NODE_TIMEOUT = 10000; private final static long WAIT_NODE_VISIBLE_TIMEOUT = 10000; private final static long BEFORE_EDIT_TIMEOUT = 1000; private final static long WAIT_EDITING_TIMEOUT = 10000; TextAreaOperator: private final static long CHANGE_CARET_POSITION_TIMEOUT = 10000; private final static long TYPE_TEXT_TIMEOUT = 30000; TextComponentOperator: private final static long CHANGE_CARET_POSITION_TIMEOUT = 10000; private final static long TYPE_TEXT_TIMEOUT = 30000; TextFieldOperator: private final static long CHANGE_CARET_POSITION_TIMEOUT = 10000; private final static long TYPE_TEXT_TIMEOUT = 30000;
I have no objection against increasing timeout values to 10000 or even to 60000 ms. As you said it won't make test slower. Except for one timeout: BEFORE_EDIT_TIMEOUT. This is not a waiting timeout - this is a time to sleep between node selecting and mouse click (which supposed to turn the node into editing mode). However, I do not think default values should be changed any time when they are too big or small. After all it's just _default_ values. Values could be changed as neccessary somewhere in test environment - Jemmy provides all neccessary API to change them. Talking about Jelly2, in particular, we have a place to do it - during Jemmy initialization in JellyTest clas. This time I'll increase them to 60000.
Timeouts increased to 60000
Thanks. Verified in 2.0.5.