Mailingliste - Einträge 2006

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

Re: [qftestJUI] Re: qftestJUI-list Digest, Vol 19, Issue 1

  • Subject: Re: [qftestJUI] Re: qftestJUI-list Digest, Vol 19, Issue 1
  • From: Gregor Schmid <Gregor.Schmid@?.de>
  • Date: 01 Mar 2006 22:14:07 +0100

Hi Mark,

the "Wait for component" is sufficient to set a maximum time, except
that it will always throw an exception. You can catch that and turn it
into an error or warning, but your test may not be ready to continue.

More notably though, the sequence with time limit will always report
the actual time spent which is what Phil asked for.

Best regards,

Mark Willburger <Mark_Willburger@?.com> writes:

>    why wouldn't you just use the duration of the wait for component by
>    itself?
>    is there some processing overhead that the sequence with timelimit
>    cleans up?
>    Message: 1
>    Date: 01 Mar 2006 09:56:11 +0100
>    From: Gregor Schmid <Gregor.Schmid@?.de>
>    Subject: [qftestJUI] Re: Timing Operations
>    To: qftestJUI-list@?.de
>    Message-ID: <r18xrumtlg.fsf@?.de>
>    Content-Type: text/plain; charset=us-ascii
>    Another question of general interest:
>    Hi Phil,
>    > Greg,
>    >
>    > I have a some operaions with my application that I'm testing with
>    > gftestJUI that I need to time.  Is there a way to time how long it
>    takes
>    > in between events.
>    >
>    > To give you an idea of the opertion I'm trying to time... a popup
>    file
>    > selector appears, then after the user clicks a button in the window
>    it
>    > takes about 30 secs for an item to be added to a tree structure
>    (sort of
>    > like a file view in windows explorer).
>    >
>    > Anyway to record how long something like that takes?
>    Use a sequence with timelimit as follows:
>    + Sequence with timelimit
>     + MPRC to click the button
>     + Wait for component with the new tree item as the target id
>    Make the timeout in the "Wait for component" node very generous, like
>    two minutes or so.
>    Set the timeout of the "Sequence with timelimit" to the time that is
>    considered an acceptable response time. Set the error level to
>    "Error", "Warning" or even a plain message if you don't want to
>    consider exceeding the limit an error.
>    In any case, the actual time spent in the sequence will be logged as a
>    check.
>    Please see the manual for further info.
>    Best regards,
>       Greg

Gregor Schmid                                Gregor.Schmid@?.de
Quality First Software GmbH           
Tulpenstr. 41                                Tel: +49 8171 919870
DE-82538 Geretsried                          Fax: +49 8171 919876