Hello,
work with Capture&Replay.
testcase:
Capture several teststeps
The Replay end up with 'Waitings' after each teststep.
How can I avoid these 'Waitings'?
Thanks,
'Waitings' after each Teststep
Re: 'Waitings' after each Teststep
Hi,
Could you please specify what kind of “waiting” do you mean? Is it something you see in progress or report? Have you tried to enable Turbo mode in recording properties? It removes recorded delays or default delays added with some actions.
Could you please specify what kind of “waiting” do you mean? Is it something you see in progress or report? Have you tried to enable Turbo mode in recording properties? It removes recorded delays or default delays added with some actions.
Pavel Kudrys
Ranorex explorer at Descartes Systems
Please add these details to your questions:
Ranorex explorer at Descartes Systems
Please add these details to your questions:
- Ranorex Snapshot. Learn how to create one >here<
- Ranorex xPath of problematic element(s)
- Ranorex version
- OS version
- HW configuration
Re: 'Waitings' after each Teststep
Hello,
When I start the Replay I see "Waitings" between each teststeps in the progress.
In the code (for instance):
"Delay.Milisecondes(2370)"
When I start the Replay I see "Waitings" between each teststeps in the progress.
In the code (for instance):
"Delay.Milisecondes(2370)"
Re: 'Waitings' after each Teststep
Hi,
OK, two things. The delay values you are getting are caused by unchecked setting "Use timings also for recorded actions" (in Settings >> Recorder defaults). If unchecked, Ranorex records exact delays between individual actions. I would suggest to enable this option and use pre-defined timings for new actions. Any change you make in timing settings will not affect already recorded actions.
At second, if you don't want to see even these predefined delays, you can enable Turbo mode for each recording module. Turbo mode disables all recorded delays, except manually added Delay actions. Turbo mode is a nice helper, but you should use it with caution, because some apps may not be ready immediately after previous action, so small delay may be required
Hope this helps?
OK, two things. The delay values you are getting are caused by unchecked setting "Use timings also for recorded actions" (in Settings >> Recorder defaults). If unchecked, Ranorex records exact delays between individual actions. I would suggest to enable this option and use pre-defined timings for new actions. Any change you make in timing settings will not affect already recorded actions.
At second, if you don't want to see even these predefined delays, you can enable Turbo mode for each recording module. Turbo mode disables all recorded delays, except manually added Delay actions. Turbo mode is a nice helper, but you should use it with caution, because some apps may not be ready immediately after previous action, so small delay may be required
Hope this helps?
Pavel Kudrys
Ranorex explorer at Descartes Systems
Please add these details to your questions:
Ranorex explorer at Descartes Systems
Please add these details to your questions:
- Ranorex Snapshot. Learn how to create one >here<
- Ranorex xPath of problematic element(s)
- Ranorex version
- OS version
- HW configuration