Issue 79207 - Testtool is unable to access ok-button on ScriptSelector
Summary: Testtool is unable to access ok-button on ScriptSelector
Alias: None
Product: General
Classification: Code
Component: ui (show other issues)
Version: 680m218
Hardware: All All
: P2 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Depends on:
Reported: 2007-07-04 12:52 UTC by joerg.skottke
Modified: 2017-05-20 10:47 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Note You need to log in before you can comment on or make changes to this issue.
Description joerg.skottke 2007-07-04 12:52:38 UTC
This appears to be one more of those weird testtool issues...

Automated test: framework\update\f_updt_customize.bas::tUpdtCustomize

From Tools/Customize the test assigns a macro by opening the Script Selector.
It is verified that the ScriptSelector is open using .exists( 2 ), a call to
dialogtest for the dialog works as well.

To close the dialog the sequence

kontext "ScriptSelector"

is executed but the ok-button is not available (though it is present and enabled)
Comment 1 joerg.skottke 2007-07-04 12:54:04 UTC
Seen on Linux and Solaris Sparc
Comment 2 joerg.skottke 2007-07-05 07:18:34 UTC
Found a rather import detail which was missing - the testtool is the one taken
from CWS GH13, a m193 based build. Now the problem is reproducible on other the
testmachine as well.
Comment 3 gregor.hartmann 2007-07-13 11:02:42 UTC
moved to 2.4 because of too little time left
Comment 4 gregor.hartmann 2007-07-20 16:09:28 UTC
inserting a small wait of 500 cured the problem for me

Will implement an internal retry mechanism for these buttons as existing already
for normal ui elements
Comment 5 gregor.hartmann 2007-12-21 11:00:10 UTC
Comment 6 gregor.hartmann 2007-12-21 11:07:20 UTC
3.0 I said ;-)
Comment 7 2008-03-11 15:48:24 UTC
set target devtools, suites better for this cws
Comment 8 Marcus 2017-05-20 10:47:38 UTC
Reset assigne to the default "".