Hi Lihua, ahhh...got it :-) Meanwhile it seems my fix was successful. Will be integrated in next builds.
again, thanks and Best Regards Helge On 08/28/09 10:09, Zhu Lihua wrote: > Hi Helge, > > when you click the "Call out" button in the "drawing" toolbar, or a > "Call out" is selected, the toolbar "Drawing object properties" should > be opened. > > tFormatPositionAndSizeLegend will draw a "Call out" in the document. > After the "Call out" is drew, it's remain selected. So the toolbar > "Drawing object properties" should be opened. > > Running tFormatPositionAndSizeLegend alone, that toolbar can be opened > normally. But when running the testcase after tViewToolbars, that > toolbar can not be opened. > > Best regards, > Lihua > > 在 2009-08-28五的 08:59 +0200，Helge Delfs写道： >> Hi Lihua, >> >> hmmm, I can't see where toolbar "Drawing object properties" is expected >> to be opened in the mentioned testcase. >> >> >> >> Thank you and best regards >> Helge >> >> >> On 08/28/09 08:13, Zhu Lihua wrote: >>> Hi Helge, >>> >>> Maybe there is a misunderstanding, so you can't reproduce the problem. >>> I said: After tViewToolbars is run, "Drawing object properties" toolbar >>> will not show up in testcase tFormatPositionAndSizeLegend. >>> It's "Drawing object properties" toolbar, not "Drawing toolbar". >>> There should be a "Drawing object properties" toolbar when >>> tFormatPositionAndSizeLegend draws a legend object. But there is not. >>> This toolbar should appear in the area blow the menu with other >>> toolbars. >>> >>> And we are very glad we helped. >>> >>> cheers, >>> Lihua >>> >>> 在 2009-08-27四的 11:37 +0200，Helge Delfs写道： >>>> Hi Lihua, >>>> >>>> On 08/26/09 04:09, Zhu Lihua wrote: >>>>> Hi Oliver, >>>>> Thanks for explanation. >>>>> You said "For the new codeline (DEV300) the automation team has the main >>>>> goal to stabilize the autotests so that a rerun will not be necessary >>>>> anymore." >>>>> I wonder how you do that? Just insert delay instruction in script? or >>>>> use some new functions in scripts? or make some modification in the >>>>> Office side? Because we have to use scripts based on former OOo >>>>> milestone, we need modify the scripts we are using to avoid these >>>>> issues. >>>>> The 3rd problem I mentioned include 2 issues. One is a timing issue. >>>>> What do you think of the other one? That is: After tViewToolbars is run, >>>>> "Drawing object property" toolbar will not show up in testcase >>>>> tFormatPositionAndSizeLegend. IMHO, this is not a right behavior. >>>> tViewToolbars only is opening and closing all available toolbars >>>> depending on the defaults. Means default toolbars will remain opened. If >>>> later on the Drawing-Toolbar is not opended I would then interprete this >>>> as an issue in office application. But currently I can't reproduce this >>>> in DEV300m55 build. >>>> But...I've seen the warning in tFormatPositionAndSizeLegend some times >>>> like you and I wrote an issue for that to add a sleep as you mentioned >>>> in wZeichenObjektEinfuegen. Thank you for this valuable hint. With this >>>> fix I can't reproduce this warning when running tViewToolbars and >>>> tFormatPositionAndSizeLegend afterwards anymore. I will check >>>> hToolbarSelect() function if this can cause the toolbar not to be opened. >>>> See issue http://qa.openoffice.org/issues/show_bug.cgi?id=104542 >>>> for implementation details. >>>> >>>> >>>> Best Regards >>>> Helge >>>> >>>> >>>>> Thank you and best regards, >>>>> Lihua >>>>> >>>>> >>>>> >>>>> --------------------------------------------------------------------------- >>>>> Date: Mon, 24 Aug 2009 11:00:50 +0200 >>>>> From: Oliver Craemer - Sun Germany - ham02 - Hamburg >>>>> <[email protected]> >>>>> Content-Type: text/plain; charset=UTF-8; format=flowed >>>>> Subject: [qa-dev] [Automation]Problems in OOo3.1.1RC1 zh-CN build >>>>> >>>>> Hi Lihua, >>>>> >>>>> all three mentioned problems are known timing problems which occurs >>>>> sometimes (often with a bad network / IO performance) and are already >>>>> fixed in the current DEV300m55. >>>>> For the new codeline (DEV300) the automation team has the main goal to >>>>> stabilize the autotests so that a rerun will not be necessary anymore. >>>>> >>>>> Kind regards, Oliver >>>>> >>>>> Zhu Lihua wrote: >>>>>> Hi all, >>>>>> Sun Dequan(sdq) has finished the automation testing of OOo3.1.1RC1. Some >>>>>> problems arose. I wonder if they exist in other builds. >>>>>> >>>>>> Summarize all the problems, we can classify them into 3 types: >>>>>> >>>>>> >>>>>> 1. "Active: UNO URL "Slot:XXXXX" could not be run: Disabled. >>>>>> These warnings mainly arise in c_updat2.bas. And they arise randomly in >>>>>> testcases if we run the script again. >>>>>> Probing into the script showes the problems lie in the following code: >>>>>> >>>>>> Call hFileOpen(Convertpath(gTesttoolPath + "FileName")) >>>>>> Call sMakeReadOnlyDocumentEditable >>>>>> >>>>>> The first instruction opens a document named "FileName", and the 2nd >>>>>> instruction make it editable if it is not. But sometimes the file >>>>>> "FileName" is still ReadOnly after the 2 instruction. So, problems >>>>>> occur. >>>>>> If we insert a "sleep 1" instruction between the instructions, these >>>>>> problem will not arise again. >>>>>> So, is this a script problem or a performance issue in Chinese build? >>>>>> >>>>>> 2. "Timeout when waiting the server response" >>>>>> These problems often occur in function "hStartTheOffice" and >>>>>> "ExitRestartTheOffice" when testing under Windows. Because sometimes >>>>>> there is a existing "soffice.bin" process, So Fail to Start Office. >>>>>> These problems occurs randomly in many scripts. >>>>>> We use the scripts run_test.vbs to start testing. Do you use this >>>>>> scripts too? Have you seen these problems? >>>>>> >>>>>> 3. "Format / Position and Size does not work! Maybe object not >>>>>> selected!" >>>>>> This problem occurs in tFormatPositionAndSizeLegend in w_updt.bas. Run >>>>>> this testcase will not result in the problem. But run the whole script >>>>>> will result in the problem. after probing into the script, it turned out >>>>>> that the problem caused by another testcase, "tViewToolbars" in >>>>>> w_003_.inc. After this testcase, "Drawing object property" toolbar will >>>>>> not show when we click callout button in the drawing toolbar. And under >>>>>> this condition, the callout may not be selected by wObjektSelektieren. >>>>>> Following is the code snippet. >>>>>> Call hNewDocument >>>>>> Call wZeichenobjektEinfuegen ( "Legende", 45, 35, 50, 50 ) >>>>>> printlog " Insert a legend" >>>>>> sleep (1) >>>>>> Call wObjektSelektieren(43, 33, 75, 75) >>>>>> >>>>>> There is 2 problems here: >>>>>> A. tViewToolbars should not cause the disappearance of the "Drawing >>>>>> object property" toolbar. >>>>>> B. In function wZeichenobjektEinfuegen(), need a time delay between >>>>>> "click the button in toolbar" and "draw the object". Because the 1st >>>>>> action may cause the change of the toolbars, if the count of toolbars >>>>>> changed, the available area will change accordingly. We need wait until >>>>>> the new available area show, since it takes time to hide toolbar and >>>>>> resize availble area. To verify this, we add a time delay between the 2 >>>>>> actions, and the object can be selected, although the problem A still >>>>>> exist. I don't mean this is a solution of the problems, it's just a >>>>>> verification for problem B. Problem A disposes problem B. >>>>>> This issue also occurs in Japanese build and Russian build, I can see. >>>>>> >>>>>> Best regards, >>>>> >>>>> >> -- =============================================================== Sun Microsystems GmbH Helge Delfs Nagelsweg 55 Quality Assurance Engineer 20097 Hamburg OOo Team Lead Automation http://qa.openoffice.org mailto:[email protected] http://wiki.services.openoffice.org/wiki/User:Hde PGP Key-ID: 0x395940C4 --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
