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 2013


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

Re: [QF-Test] Going from quick to slow computer


  • Subject: Re: [QF-Test] Going from quick to slow computer
  • From: Gregor Schmid <Gregor.Schmid@?.de>
  • Date: Wed, 02 Oct 2013 15:03:22 +0200

Hello Mårten,

QF-Test does a lot of automatic synchronization to handle such cases
and in general it works well. This includes synchronizing with the
respective event queue, waiting for components to become available and
enabled, handling glass panes etc.

If your target machine's load is so high that the default timeouts are
not sufficient, the first thing you should try is to increase those
timeouts via >>Edit->Options<<. The settings are under
Replay->Timeouts, see

http://www.qfs.de/qftest/manual/en/opt_play.html#sec_opt_autodelay

for details.

If that's not sufficient you can add specific timeouts at critical
points, e.g. a 'Wait for component' node or a 'Check' node with a
timeout. For more specific help, please send a run-log showing typical
problems to our support, not to the mailing list.

Working with delays is a last resort. Recording with delays is not
supported, but you can either use the replace dialog to quickly set
delays on multiple nodes, or - preferably - experiment with the
default delay options under Replay->Delays.

Best regards,
    Greg


Mårten Carlzon <marten.carlzon@?.se> writes:

> Hello all,
>
> I have two questions I was wondering if I could get some help with.
>
> I have done recordings on a computer and a couple of tests that runs smoothly but when I try to
> move my tests over to my server that is rather slow I get some errors because of holdup and the
> like and I was wondering about the best practice to get past these errors?
>
> The errors seems to surface because either the window is behind a pause screen or QFTest tried to
> click to quickly on a button so that it haven’t really activated yet.
>
> I have tried with making a while loop where I try and try again until I succeeds doesn’t seem like
> the best option. Therefor I was wondering if there was a better method to somehow compensate for
> moving to a slower computer and notice the pause glass pane and not letting QFTest run away with
> clicking to fast?
>
> And this brings me to my second question. Since I do my recording on my own working computer and
> try to execute them on the test server, is there a way to make delays on the recording? I know I
> can go through every mouse click and add a delay for a few milliseconds but was wondering if there
> was a way to add these delays while recording?

--
Gregor Schmid

E: gregor.schmid@?.de
T: +49 (0)8171 38648-11
F: +49 (0)8171 38648-16

Quality First Software GmbH | www.qfs.de
Tulpenstr. 41 | 82538 Geretsried | Germany
GF Gregor Schmid, Karlheinz Kellerer
HRB München 140833