Execution taking time

[Kirill BulatnikovParticipant]

Hey Hari, thanks for interest in ZAPTEST.

1.About your first observation. The delay that you have during script execution is more likely caused by “exist” method, as it having exactly 45 seconds default timeout. Usually this mean your test step is “failed” if this delay expired. Does it looks close to what you have in your script?
Though we have delay parameter for steps execution in ZAPTEST app. Navigate to TOOLS -> Options -> Runtime -> Global Delay (in ms).

2. Did you mean that code highlighting not working on some of your lab machines? Actually it is default parameter and can’t be changed (turned off), however it may be some graphical inconvenience on your environment. We will appreciate if you provide more details.

[Kirill BulatnikovParticipant]

3. I guess “click” method should work just fine. If you need some scrolling within submenu it may require “for” loop statement which is not allowed in free edition. But you still can use single scroll or Down (or PageDown) button.
4. Pressing keyboard buttons should not affect script execution unless it is affect screen objects displaying (like when you press “PageDown” button and page scrolls down – this way discovered object may be located out of visible area).
5. Screenshots appearing in test reports are exact imprint of the object that been recognized on the real application, not the one from repository. So it might be slightly different. This is valid for successfulll object recognition (successfully passed step), whereas in case of failed object recognition you will see repository snapshot.

[Author]

Posts