2017 up to now  | 2016 | 2015 | 2014 | 2013 | 2012 | 2011 | 2010 | 2009 | 2008 | 2007

(older archive entries before 2007 are not shown here, but included in the onsite-search)

Mailing List - Entries of 2007


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [QF-Test] Closing an unknown modal dialog


  • Subject: Re: [QF-Test] Closing an unknown modal dialog
  • From: "Kelstrup, Louise" <louise.kelstrup@?.com>
  • Date: Fri, 13 Jul 2007 13:27:49 +0200

Hi Martin

That works!!

I didn't know the qfs.qft suite. There is a lot of helpfull stuff there. I have never thought of making generic components but that will be helpful in several situations.

Thanks for enlightening me :-)

/Louise

-----Original Message-----
From: Martin Moser [mailto:martin.moser@?.de]
Sent: 13. juli 2007 13:01
To: qftest-list@?.de
Cc: Kelstrup, Louise
Subject: Re: [QF-Test] Closing an unknown modal dialog

Hi Louise,

did you try the closeAllModalDialog procedure from qfs.qft?
This procedure can close any Modal dialog, because it makes use of the generic-component approach.
To make use of that, add qfs.qft to the "include" area of your test-suite and add the procedure "qfs.cleanup.closeAllModalDialogs"

I have to take a closer look at the CLOSING problem.

Regards,
Martin

--On Freitag, Juli 13, 2007 09:59:37 +0200 "Kelstrup, Louise"
<louise.kelstrup@?.com> wrote:

>
> Hi
>
> I am writing exception handling for my script and I have a challenge
> that I would like some comments on.
>
> Sometimes during testrun I get an unexpected modal dialog. It is not
> same dialog every time and it does not happen at the same script node,
> so that makes it difficult using a normal try-catch. I am therefore
> trying to implement catch nodes in my dependencies.
>
> When the dialog appears I want my script (in the dependency catch
> node) to close the dialog and after that close the mainwindow (not the
> whole
> application) and continue with the next testcase. The mainwindow
> cannot be closed until I get rid of the modal dialog.
>
> But how do I close the modal dialog when I don't know which component
> it is? Is it possible to make a Jython script that closes the active
> modal dialog? Or do I have to identify every possible modal dialog
> that could appear and try closing all of them with try-catch (not a
> very beautiful solution).
>
> Another problem I am facing is closing windows with Alt-F4 or pressing
> the X in the corner.
> When I record I get the steps:
> PRESSED Alt-Alt
> PTR Alt-F4
> CLOSING (windowname)
>
> Or (for the X)
> CLOSING (windowname)
>
> But nothing seems to happen when I replay?
>
> Regards Louise
>
>
>
> Capgemini Danmark A/S, Registered office: Gentofte, Reg.No. 25606965
>
>
>
>
> This message contains information that may be privileged or
> confidential and is the property of the Capgemini Group. It is
> intended only for the person to whom it is addressed. If you are not
> the intended recipient, you are not authorized to read, print, retain,
> copy, disseminate, distribute, or use this message or any part
> thereof. If you receive this message in error, please notify the
> sender immediately and delete all copies of this message.



--
Martin Moser                           martin.moser@?.de
Quality First Software GmbH            http://www.qfs.de
Tulpenstr. 41                          Tel: +49 8171 919874
DE-82538 Geretsried                    Fax: +49 8171 919876
GF: Gregor Schmid, Karlheinz Kellerer  HRB München 14083


This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient,  you are not authorized to read, print, retain, copy, disseminate,  distribute, or use this message or any part thereof. If you receive this  message in error, please notify the sender immediately and delete all  copies of this message.